[要約] RFC 2674は、トラフィッククラス、マルチキャストフィルタリング、および仮想LAN拡張を持つブリッジの管理オブジェクトの定義に関するものです。このRFCの目的は、これらの機能を持つブリッジの管理を容易にするための標準化を提供することです。
Network Working Group E. Bell
Request for Comments: 2674 3Com Corp.
Category: Standards Track A. Smith
Extreme Networks
P. Langille
Newbridge Networks
A. Rijhsinghani
Cabletron Systems
K. McCloghrie
cisco Systems
August 1999
Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions
交通クラス、マルチキャストフィルタリング、仮想LAN拡張機能を備えた橋の管理されたオブジェクトの定義
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 (1999). All Rights Reserved.
Copyright（c）The Internet Society（1999）。無断転載を禁じます。
Abstract
概要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines two MIB modules for managing the new capabilities of MAC bridges defined by the IEEE 802.1D-1998 MAC Bridges and the IEEE 802.1Q-1998 Virtual LAN (VLAN) standards for bridging between Local Area Network (LAN) segments. One MIB module defines objects for managing the 'Traffic Classes' and 'Enhanced Multicast Filtering' components of IEEE 802.1D-1998. The other MIB module defines objects for managing IEEE 802.1Q VLANs.
このメモは、TCP/IPベースのインターネットのネットワーク管理プロトコルで使用するための管理情報ベース（MIB）の一部を定義します。特に、IEEE 802.1-1D-1998 Mac BridgesとIEEE 802.1Q-1998 Virtual LAN（VLAN）標準で定義されたMacブリッジの新しい機能を管理するための2つのMIBモジュールを定義して、ローカルエリアネットワーク（LAN）セグメント間のブリッジングの標準。1つのMIBモジュールは、IEEE 802.1D-1998の「トラフィッククラス」と「強化されたマルチキャストフィルタリング」コンポーネントを管理するためのオブジェクトを定義します。他のMIBモジュールは、IEEE 802.1Q VLANを管理するためのオブジェクトを定義します。
Provisions are made for support of transparent bridging. Provisions are also made so that these objects apply to bridges connected by subnetworks other than LAN segments. This memo also includes several MIB modules in a manner that is compliant to the SMIv2 [V2SMI].
透明なブリッジングの支援のための規定がなされています。また、これらのオブジェクトがLANセグメント以外のサブネットワークで接続されたブリッジに適用されるように、規定も作成されます。このメモには、SMIV2 [V2SMI]に準拠した方法で、いくつかのMIBモジュールも含まれています。
This memo supplements RFC 1493 [BRIDGEMIB] and (to a lesser extent) RFC 1525 [SBRIDGEMIB].
このメモは、RFC 1493 [Bridgemib]および（それほどではないが）RFC 1525 [Sbridgemib]をサプリメントします。
Table of Contents
目次
1 The SNMP Management Framework ................................... 3
2 Overview ........................................................ 4
2.1 Scope ......................................................... 4
3 Structure of MIBs ............................................... 5
3.1 Structure of Extended Bridge MIB module ....................... 5
3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ......... 6
3.1.2 Relationship to IEEE 802.1Q Manageable Objects .............. 8
3.1.3 The dot1dExtBase Group ...................................... 8
3.1.4 The dot1dPriority Group ..................................... 9
3.1.5 The dot1dGarp Group ......................................... 9
3.1.6 The dot1dGmrp Group ......................................... 9
3.1.7 The dot1dTpHCPortTable ...................................... 9
3.1.8 The dot1dTpPortOverflowTable ................................ 9
3.2 Structure of Virtual Bridge MIB module ........................ 9
3.2.1 Relationship to IEEE 802.1Q Manageable Objects .............. 9
3.2.2 The dot1qBase Group .........................................13
3.2.3 The dot1qTp Group ...........................................13
3.2.4 The dot1qStatic Group .......................................13
3.2.5 The dot1qVlan Group .........................................13
3.3 Textual Conventions ...........................................13
3.4 Relationship to Other MIBs ....................................14
3.4.1 Relationship to the 'system' group ..........................14
3.4.2 Relation to Interfaces MIB ..................................14
3.4.2.1 Layering Model ............................................15
3.4.2.2 ifStackTable ..............................................16
3.4.2.3 ifRcvAddressTable .........................................16
3.4.3 Relation to Original Bridge MIB .............................16
3.4.3.1 The dot1dBase Group .......................................16
3.4.3.2 The dot1dStp Group ........................................17
3.4.3.3 The dot1dTp Group .........................................17
3.4.3.4 The dot1dStatic Group .....................................17
3.4.3.5 Additions to the Original Bridge MIB ......................18
4 Definitions for Extended Bridge MIB .............................18
5 Definitions for Virtual Bridge MIB ..............................39
6 Acknowledgments .................................................80
7 Security Considerations .........................................80
8 References ......................................................81
9 Authors' Addresses ..............................................84
10 Intellectual Property ..........................................85
11 Full Copyright Statement .......................................86
The SNMP Management Framework presently consists of five major components:
SNMP管理フレームワークは現在、5つの主要なコンポーネントで構成されています。
o An overall architecture, described in an Architecture for Describing SNMP Management Frameworks [ARCH].
o SNMP管理フレームワークを説明するためのアーキテクチャで説明されている全体的なアーキテクチャ[Arch]。
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 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC 1215 [V1TRAPS]. The second version, called SMIv2, is described in STD 58, RFC 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58, RFC 2580 [V2CONFORM].
o 管理を目的としたオブジェクトとイベントを説明および名前を付けるためのメカニズム。この管理情報構造の最初のバージョン（SMI）はSMIV1と呼ばれ、STD 16、RFC 1155 [V1SMI]、STD 16、RFC 1212 [V1Concise]およびRFC 1215 [V1Traps]で説明されています。SMIV2と呼ばれる2番目のバージョンは、STD 58、RFC 2578 [V2SMI]、STD 58、RFC 2579 [V2TC]およびSTD 58、RFC 2580 [V2Conform]に記載されています。
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 [V1PROTO]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [V2TRANS], Message Processing and Dispatching [V3MPC] and User-based Security Model [V3USM].
o 管理情報を転送するためのメッセージプロトコル。SNMPメッセージプロトコルの最初のバージョンはSNMPV1と呼ばれ、STD 15、RFC 1157 [V1Proto]で説明されています。インターネット標準トラックプロトコルではないSNMPメッセージプロトコルの2番目のバージョンは、SNMPV2Cと呼ばれ、RFC 1901 [V2Community]およびRFC 1906 [V2Trans]で説明されています。メッセージプロトコルの3番目のバージョンはSNMPV3と呼ばれ、RFC 1906 [V2Trans]、メッセージ処理とディスパッチ[V3MPC]、およびユーザーベースのセキュリティモデル[V3USM]で説明されています。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [V1PROTO]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [V2PROTO].
o 管理情報にアクセスするためのプロトコル操作。プロトコル操作の最初のセットと関連するPDU形式は、STD 15、RFC 1157 [V1Proto]で説明されています。プロトコル操作の2番目のセットと関連するPDU形式は、RFC 1905 [V2Proto]で説明されています。
o A set of fundamental applications described in SNMPv3 Applications [V3APPS] and the view-based access control mechanism described in View-based Access Control Model [V3VACM].
o SNMPV3アプリケーション[V3APPS]で説明されている一連の基本的なアプリケーションと、ビューベースのアクセス制御モデル[V3VACM]で説明されているビューベースのアクセス制御メカニズム。
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.
このメモは、SMIV2に準拠したMIBモジュールを指定します。SMIV1に準拠するMIBは、適切な翻訳を通じて生成できます。結果として生じる翻訳されたMIBは、翻訳が不可能であるためオブジェクトまたはイベントが省略されている場合を除き、意味的に同等でなければなりません（Counter64の使用）。SMIV2の一部の機械読み取り可能な情報は、翻訳プロセス中にSMIV1のテキスト説明に変換されます。ただし、この機械の読み取り可能な情報の損失は、MIBのセマンティクスを変更するとは見なされません。
A common device present in many networks is the Bridge. This device is used to connect Local Area Network segments below the network layer. These devices are often known as 'layer 2 switches'.
多くのネットワークに存在する一般的なデバイスはブリッジです。このデバイスは、ネットワークレイヤーの下のローカルエリアネットワークセグメントを接続するために使用されます。これらのデバイスは、多くの場合、「レイヤー2スイッチ」として知られています。
There are two major modes defined for this bridging: Source-Route and transparent. Source-Route bridging is described by IEEE 802.5 [802.5]. and is not discussed further in this document.
このブリッジングには、ソースルートと透明な2つの主要なモードが定義されています。ソースルートブリッジングは、IEEE 802.5 [802.5]によって説明されています。このドキュメントではこれ以上議論されていません。
The transparent method of bridging is defined by IEEE 802.1D-1998 [802.1D] which is an update to the original IEEE 802.1D specification [802.1D-ORIG]. Managed objects for that original specification of transparent bridging were defined in RFC 1493 [BRIDGEMIB].
ブリッジングの透明な方法は、IEEE 802.1D-1998 [802.1d]によって定義されています。これは、元のIEEE 802.1D仕様[802.1D-Orig]の更新です。透明ブリッジングの元の仕様の管理オブジェクトは、RFC 1493 [Bridgemib]で定義されました。
The original IEEE 802.1D is augmented by IEEE 802.1Q-1998 [802.1Q] to provide support for 'virtual bridged LANs' where a single bridged physical LAN network may be used to support multiple logical bridged LANs, each of which offers a service approximately the same as that defined by IEEE 802.1D. Such virtual LANs (VLANs) are an integral feature of switched LAN networks. A VLAN can be viewed as a group of end-stations on multiple LAN segments and can communicate as if they were on a single LAN. IEEE 802.1Q defines port-based Virtual LANs where membership is determined by the bridge port on which data frames are received. This memo defines the objects needed for the management of port-based VLANs in bridge entities.
元のIEEE 802.1dはIEEE 802.1Q-1998 [802.1Q]によって増強され、「仮想ブリッジ付きLANS」をサポートすることができます。ここでは、単一のブリッジされた物理LANネットワークを使用して複数の論理ブリッジ付きLANをサポートすることができます。IEEE 802.1dによって定義されたものと同じです。このような仮想LAN（VLAN）は、スイッチ付きLANネットワークの不可欠な機能です。VLANは、複数のLANセグメント上のエンドステーションのグループと見なすことができ、単一のLANにいるかのように通信できます。IEEE 802.1Qは、データフレームが受信されるブリッジポートによってメンバーシップが決定されるポートベースの仮想LANを定義します。このメモは、ブリッジエンティティでのポートベースのVLANの管理に必要なオブジェクトを定義します。
This memo defines those objects needed for the management of a bridging entity operating in the transparent mode, as well as some objects applicable to all types of bridges. Managed objects for Source-Route bridging are defined in RFC 1525 [SRBRIDGEMIB].
このメモは、透明モードで動作するブリッジングエンティティの管理に必要なオブジェクトと、あらゆる種類のブリッジに適用されるいくつかのオブジェクトを定義します。ソースルートブリッジング用の管理されたオブジェクトは、RFC 1525 [srbridgemib]で定義されています。
This MIB includes a comprehensive set of managed objects which attempts to match the set defined in IEEE 802.1D and IEEE 802.1Q. However, to be consistent with the spirit of the SNMP Framework, a subjective judgement was made to omit the objects from those standards most 'costly' to implement in an agent and least 'essential' for fault and configuration management. The omissions are described in section 3 below.
このMIBには、IEEE 802.1dおよびIEEE 802.1qで定義されたセットを一致させようとする包括的な管理オブジェクトのセットが含まれています。ただし、SNMPフレームワークの精神と一致するためには、これらの標準からオブジェクトを最も「コスト」して、エージェントに実装し、障害と構成管理に最小限の「不可欠」にするという主観的な判断がなされました。省略については、以下のセクション3で説明します。
Historical note:
歴史的メモ：
The original bridge MIB [BRIDGEMIB] used the following principles for determining inclusion of an object in the BRIDGE-MIB module:
元のBridge Mib [Bridgemib]は、Bridge-Mibモジュールにオブジェクトを含めることを決定するために、次の原則を使用しました。
(1) Start with a small set of essential objects and add only as further objects are needed.
(1) 必須オブジェクトの小さなセットから始めて、さらなるオブジェクトが必要な場合にのみ追加します。
(2) Require objects be essential for either fault or configuration management.
(2) 障害または構成管理のいずれかにオブジェクトが不可欠であることを要求します。
(3) Consider evidence of current use and/or utility.
(3) 現在の使用および/またはユーティリティの証拠を検討してください。
(4) Limit the total of objects.
(4) オブジェクトの合計を制限します。
(5) Exclude objects which are simply derivable from others in this or other MIBs.
(5) このまたは他のMIBの他の人から単に派生可能なオブジェクトを除外します。
(6) Avoid causing critical sections to be heavily instrumented. The guideline that was followed is one counter per critical section per layer.
(6) 重要なセクションを重視しないようにしないでください。従ったガイドラインは、レイヤーごとにクリティカルセクションごとに1つのカウンターです。
This document defines additional objects, on top of those existing in the original BRIDGE-MIB module defined in [BRIDGEMIB]: that MIB module is to be maintained unchanged for backwards compatibility. Section 3.4.3 of the present document contains some recommendations regarding usage of objects in the original bridge MIB by devices implementing the enhancements defined here.
このドキュメントでは、[Bridgemib]で定義されている元のBridge-Mibモジュールに存在するものの上に、追加のオブジェクトを定義します。MIBモジュールは、逆方向の互換性のために変更されません。現在のドキュメントのセクション3.4.3には、ここで定義されている拡張機能を実装するデバイスによる元のブリッジMIBのオブジェクトの使用に関するいくつかの推奨事項が含まれています。
Two MIB modules are defined here:
2つのMIBモジュールがここで定義されています。
(1) Managed objects for an extended bridge MIB module P-BRIDGE-MIB for the traffic class and multicast filtering enhancements defined by IEEE 802.1D-1998 [802.1D].
(1) IEEE 802.1D-1998 [802.1d]で定義されたトラフィッククラスおよびマルチキャストフィルタリング強化のための拡張ブリッジMIBモジュールP-Bridge-MIBの管理オブジェクト。
(2) Managed objects for a virtual bridge MIB module Q-BRIDGE-MIB for the Virtual LAN bridging enhancements defined by IEEE 802.1Q-1998 [802.1Q].
(2) IEEE 802.1Q-1998 [802.1Q]によって定義された仮想LANブリッジングエンハンスメントの仮想ブリッジMIBモジュールQ-Bridge-MIBの管理オブジェクト。
Objects in this MIB are arranged into groups. Each group is organized as a set of related objects. The overall structure and assignment of objects to their groups is shown below.
このMIBのオブジェクトはグループに配置されます。各グループは、関連するオブジェクトのセットとして編成されています。グループへのオブジェクトの全体的な構造と割り当てを以下に示します。
This section contains a cross-reference to the objects defined in IEEE 802.1D-1998 [802.1D]. It also details those objects that are not considered necessary in this MIB module.
このセクションには、IEEE 802.1D-1998 [802.1d]で定義されているオブジェクトに対する相互参照が含まれています。また、このMIBモジュールでは必要ないと見なされないオブジェクトについても詳しく説明しています。
Some objects defined by IEEE 802.1D-1998 have been included in the virtual bridge MIB module rather than this one: entries in dot1qTpGroupTable, dot1qForwardAllTable and dot1qForwardUnregisteredTable are required for virtual bridged LANs with additional indexing (e.g. per-VLAN, per-FDB) and so are not defined here. Instead, devices which do not implement virtual bridged LANs but do implement the Extended Forwarding Services defined by IEEE 802.1D (i.e. dynamic learning of multicast group addresses and group service requirements in the filtering database) should implement these tables with a fixed value for dot1qFdbId (the value 1 is recommended) or dot1qVlanIndex (the value 1 is recommended). Devices which support Extended Filtering Services should support dot1qTpGroupTable, dot1qForwardAllTable and dot1qForwardUnregisteredTable.
IEEE 802.1D-1998で定義されたいくつかのオブジェクトは、これではなく仮想ブリッジMIBモジュールに含まれています。DOT1QTPGruptable、DOT1QForwardAlltable、DOT1QForwardunregisterEdtableのエントリは、追加のインデックスを備えた仮想ブリッジ付きLANに必要です（E.G. Per-vlan、Per-fdbb）およびPer-fdb）およびPer-FDB）したがって、ここでは定義されていません。代わりに、仮想ブリッジ型LANを実装していないが、IEEE 802.1Dによって定義された拡張転送サービスを実装するデバイス（つまり、マルチキャストグループアドレスの動的学習とフィルタリングデータベースのグループサービス要件）は、DOT1QFDBIDの固定値でこれらのテーブルを実装する必要があります（値1が推奨されます）またはdot1qvlanindex（値1が推奨されます）。拡張フィルタリングサービスをサポートするデバイスは、dot1qtpgroutable、dot1qforwardalltable、dot1qforwardunregisteredtableをサポートする必要があります。
Extended Bridge MIB Name IEEE 802.1D-1998 Name
拡張ブリッジMIB名IEEE 802.1D-1998名
dot1dExtBase Bridge dot1dDeviceCapabilities dot1dExtendedFilteringServices dot1dTrafficClasses dot1dTrafficClassesEnabled dot1dGmrpStatus .ApplicantAdministrativeControl dot1dPriority dot1dPortPriorityTable dot1dPortDefaultUserPriority .UserPriority dot1dPortNumTrafficClasses dot1dUserPriorityRegenTable .UserPriorityRegenerationTable dot1dUserPriority dot1dRegenUserPriority dot1dTrafficClassTable .TrafficClassTable dot1dTrafficClassPriority dot1dTrafficClass dot1dPortOutboundAccessPriorityTable .OutboundAccessPriorityTable dot1dPortOutboundAccessPriority dot1dGarp dot1dPortGarpTable dot1dPortGarpJoinTime .JoinTime dot1dPortGarpLeaveTime .LeaveTime dot1dPortGarpLeaveAllTime .LeaveAllTime dot1dGmrp dot1dPortGmrpTable dot1dPortGmrpStatus .ApplicantAdministrativeControl dot1dPortGmrpFailedRegistrations .FailedRegistrations dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU dot1dTp dot1dTpHCPortTable dot1dTpHCPortInFrames .BridgePort.FramesReceived dot1dTpHCPortOutFrames .ForwardOutBound dot1dTpHCPortInDiscards .DiscardInbound dot1dTpPortOverflowTable dot1dTpPortInOverflowFrames .BridgePort.FramesReceived dot1dTpPortOutOverflowFrames .ForwardOutBound dot1dTpPortInOverflowDiscards .DiscardInbound
dot1dextbaseブリッジdot1ddeviceCapabilities dot1dextedendedfilteringsersvices dot1dtrafficclasses dot1dtrafficclassesedabled dot1dgmrpstatus .applicantadministrativecontrol dot1dot1dot1partivetionteddedpartivedpartivedpartivedpartivecontrol dot1dot1partivedpartivedpartivedpartivedpartivedpartity DOT1DUSERPRIORITYREIGENTABLE .USERPRIORITYREGENERATIONTABLE DOT1DUSERPRIORITY DOT1DREGENUSERPRIORITY DOT1DTRAFFICCLASSTABLE .TRAFFICCLASSTABLE DOT1DTRAFFICCLASSPRICHICCLASSPRICORITY DOT1DTRAFFICCLASS DOT1DOTCSCESSPANTABURTの提供優先度dot1dgarp dot1dportgarptable dot1dportgarpjointime .jointime dot1dportgarpleavetime .leavetime dot1dportgarpleavealltime .leavealltime dot1dgmrp dot1dportgmrptatable dot1dtatus。 ISTRATIONS .FAILEDREGISTRATIONS DOT1DPORTGMRPLASTPDUORIGIN。Originatoroflastpdu dot1dtp dot1dtphcporttable dot1dtphcportinframes .bridgeport.framesreceived dot1dtphcportoutfframes .forwardoutbound dot1dtphcportindiscards .dot1dtpportinbound dot1dtpportinoverflames。 owframes .forwardoutbound dot1dtpportinoverflowdiscards .discardinbound
The following IEEE 802.1D-1998 management objects have not been included in the Bridge MIB for the indicated reasons.
以下のIEEE 802.1D-1998管理オブジェクトは、示された理由でBridge MIBに含まれていません。
IEEE 802.1D-1998 Object Disposition
IEEE 802.1D-1998オブジェクト処分
Bridge.StateValue not considered useful Bridge.ApplicantAdministrativeControl not provided per-attribute (e.g. per-VLAN, per-Group). Only per-{device,port,application} control is provided in this MIB.
Bridge.StateValueは有用であると見なされていないBridge.ApplicantadMinistrativeControlは、魅力ごとに提供されていません（例：N-VLAN、グループごと）。このMIBでは、per-{device、port、application}制御のみが提供されます。
This section contains section number cross-references to manageable objects defined in IEEE 802.1Q-1998 [802.1Q]. These objects have been included in this MIB as they provide a natural fit with the IEEE 802.1D objects with which they are co-located.
このセクションには、IEEE 802.1q-1998 [802.1q]で定義されている管理可能なオブジェクトへのセクション番号の相互参照が含まれています。これらのオブジェクトは、このMIBに含まれており、それらが共同で配置されているIEEE 802.1Dオブジェクトに自然に適合しています。
Extended Bridge MIB Name IEEE 802.1Q-1998 Section and Name
拡張ブリッジMIB名IEEE 802.1Q-1998セクションと名前
dot1dExtBase Bridge
dot1dDeviceCapabilities
dot1qStaticEntryIndividualPort 5.2 implementation options
dot1qIVLCapable
dot1qSVLCapable
dot1qHybridCapable
dot1qConfigurablePvidTagging 12.10.1.1 read bridge vlan
config
dot1dLocalVlanCapable
dot1dPortCapabilitiesTable
dot1dPortCapabilities
dot1qDot1qTagging 5.2 implementation options
dot1qConfigurableAcceptableFrameTypes
5.2 implementation options
dot1qIngressFiltering 5.2 implementation options
This group contains the objects which are applicable to all bridges implementing the traffic class and multicast filtering features of IEEE 802.1D-1998 [802.1D]. It includes per-device configuration of GARP and GMRP protocols. This group will be implemented by all devices which implement the extensions defined in 802.1D-1998.
このグループには、IEEE 802.1D-1998 [802.1d]のトラフィッククラスとマルチキャストフィルタリング機能を実装するすべてのブリッジに適用できるオブジェクトが含まれています。GARPおよびGMRPプロトコルのデバイスごとの構成が含まれています。このグループは、802.1D-1998で定義された拡張機能を実装するすべてのデバイスによって実装されます。
This group contains the objects for configuring and reporting status of priority-based queuing mechanisms in a bridge. This includes per-port user_priority treatment, mapping of user_priority in frames into internal traffic classes and outbound user_priority and access_priority.
このグループには、ブリッジ内の優先ベースのキューイングメカニズムのステータスを構成および報告するためのオブジェクトが含まれています。これには、ポートごとのuser_priorityトリートメント、内部トラフィッククラスへのフレーム内のuser_priorityのマッピング、およびuser_priorityとaccess_priorityが含まれます。
This group contains the objects for configuring and reporting on operation of the Generic Attribute Registration Protocol (GARP).
このグループには、汎用属性登録プロトコル（GARP）の操作に関する構成とレポートのオブジェクトが含まれています。
This group contains the objects for configuring and reporting on operation of the GARP Multicast Registration Protocol (GMRP).
このグループには、GARPマルチキャスト登録プロトコル（GMRP）の操作に関する構成とレポートのオブジェクトが含まれています。
This table extends the dot1dTp group from the original bridge MIB [BRIDGEMIB] and contains the objects for reporting port bridging statistics for high capacity network interfaces.
この表は、元のBridge MIB [Bridgemib]からDOT1DTPグループを拡張し、高容量ネットワークインターフェイスのポートブリッジング統計を報告するオブジェクトを含んでいます。
This table extends the dot1dTp group from the original bridge MIB [BRIDGEMIB] and contains the objects for reporting the upper bits of port bridging statistics for high capacity network interfaces for when 32-bit counters are inadequate.
この表は、元のブリッジMIB [Bridgemib]からDOT1DTPグループを拡張し、32ビットカウンターが不十分な場合の大容量ネットワークインターフェイスのポートブリッジング統計の上部ビットを報告するためのオブジェクトを含んでいます。
Objects in this MIB are arranged into groups. Each group is organized as a set of related objects. The overall structure and assignment of objects to their groups is shown below. Some manageable objects defined in the original bridge MIB [BRIDGEMIB] need to be indexed differently when they are used in a VLAN bridging environment: these objects are, therefore, effectively duplicated by new objects with different indexing which are defined in the Virtual Bridge MIB.
このMIBのオブジェクトはグループに配置されます。各グループは、関連するオブジェクトのセットとして編成されています。グループへのオブジェクトの全体的な構造と割り当てを以下に示します。元のBridge MIB [Bridgemib]で定義された管理可能なオブジェクトの一部は、VLANブリッジング環境で使用される場合、異なる索引付けをする必要があります。したがって、これらのオブジェクトは、仮想ブリッジMIBで定義される異なるインデックスを持つ新しいオブジェクトによって効果的に複製されます。
This section contains section-number cross-references to manageable objects defined in clause 12 of IEEE 802.1Q-1998 [802.1Q]. It also details those objects that are not considered necessary in this MIB module.
このセクションには、IEEE 802.1Q-1998 [802.1q]の条項12で定義されている管理可能なオブジェクトに対するセクション番号の相互参照が含まれています。また、このMIBモジュールでは必要ないと見なされないオブジェクトについても詳しく説明しています。
Note: unlike IEEE 802.1D-1998, IEEE 802.1Q-1998 [802.1Q] did not define exact syntax for a set of managed objects: the following cross-references indicate the section numbering of the descriptions of management operations from clause 12 in the latter document.
注：IEEE 802.1D-1998とは異なり、IEEE 802.1Q-1998 [802.1Q]は、管理されたオブジェクトのセットの正確な構文を定義しませんでした。後者のドキュメント。
Virtual Bridge MIB object IEEE 802.1Q-1998 Reference
仮想ブリッジMIBオブジェクトIEEE 802.1Q-1998リファレンス
dot1qBase
dot1qVlanVersionNumber 12.10.1.1 read bridge vlan config
dot1qMaxVlanId 12.10.1.1 read bridge vlan config
dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan config
dot1qNumVlans
dot1qGvrpStatus 12.9.2.1/2 read/set garp
applicant controls
dot1qTp
dot1qFdbTable
dot1qFdbId
dot1qFdbDynamicCount 12.7.1.1.3 read filtering d/base
dot1qTpFdbTable
dot1qTpFdbAddress
dot1qTpFdbPort
dot1qTpFdbStatus
dot1qTpGroupTable 12.7.7.1 read filtering entry
dot1qTpGroupAddress
dot1qTpGroupEgressPorts
dot1qTpGroupLearnt
dot1qForwardAllTable 12.7.7.1 read filtering entry
dot1qForwardAllPorts
dot1qForwardAllStaticPorts
dot1qForwardAllForbiddenPorts
dot1qForwardUnregisteredTable 12.7.7.1 read filtering entry
dot1qForwardUnregisteredPorts
dot1qForwardUnregisteredStaticPorts
dot1qForwardUnregisteredForbiddenPorts
dot1qStatic
dot1qStaticUnicastTable 12.7.7.1 create/delete/read
filtering entry
12.7.6.1 read permanent database
dot1qStaticUnicastAddress
dot1qStaticUnicastReceivePort
dot1qStaticUnicastAllowedToGoTo
dot1qStaticUnicastStatus
dot1qStaticMulticastTable 12.7.7.1 create/delete/read
filtering entry
12.7.6.1 read permanent database
dot1qStaticMulticastAddress
dot1qStaticMulticastReceivePort
dot1qStaticMulticastStaticEgressPorts
dot1qStaticMulticastForbiddenEgressPorts
dot1qStaticMulticastStatus
dot1qVlan
dot1qVlanNumDeletes
dot1qVlanCurrentTable 12.10.2.1 read vlan configuration
12.10.3.5 read VID to FID
allocations
12.10.3.6 read FID allocated to
VID
12.10.3.7 read VIDs allocated to
FID
dot1qVlanTimeMark
dot1qVlanIndex
dot1qVlanFdbId
dot1qVlanCurrentEgressPorts
dot1qVlanCurrentUntaggedPorts
dot1qVlanStatus
dot1qVlanCreationTime
dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read
filtering entry
12.7.6.1 read permanent database
12.10.2.2 create vlan config
12.10.2.3 delete vlan config
dot1qVlanStaticName 12.4.1.3 set bridge name
dot1qVlanStaticEgressPorts
dot1qVlanForbiddenEgressPorts
dot1qVlanStaticUntaggedPorts
dot1qVlanStaticRowStatus
dot1qNextFreeLocalVlanIndex
dot1qPortVlanTable 12.10.1.1 read bridge vlan
configuration
dot1qPvid 12.10.1.2 configure PVID values
dot1qPortAcceptableFrameTypes 12.10.1.3 configure acceptable
frame types parameter
dot1qPortIngressFiltering 12.10.1.4 configure ingress
filtering parameters
dot1qPortGvrpStatus 12.9.2.2 read/set garp applicant
controls
dot1qPortGvrpFailedRegistrations
dot1qPortGvrpLastPduOrigin
dot1qPortVlanStatisticsTable 12.6.1.1 read forwarding port
counters
dot1qTpVlanPortInFrames
dot1qTpVlanPortOutFrames
dot1qTpVlanPortInDiscards
dot1qTpVlanPortInOverflowFrames
dot1qTpVlanPortOutOverflowFrames
dot1qTpVlanPortInOverflowDiscards
dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port counters dot1qTpVlanPortHCInFrames dot1qTpVlanPortHCOutFrames dot1qTpVlanPortHCInDiscards dot1qLearningConstraintsTable 12.10.3.1/3/4 read/set/delete vlan learning constraints 12.10.3.2 read vlan learning constraints for VID dot1qConstraintVlan dot1qConstraintSet dot1qConstraintType dot1qConstraintStatus dot1qConstraintSetDefault dot1qConstraintTypeDefault
DOT1QPORTVLANHCSTATISTISTABLE 12.6.1.1転送ポートカウンターの読み取りDOT1QTPVLANPORTHCINFRAMES DOT1QTPVLANPORTHCOUTFRAMES DOT1QTPVLANPORTHCINDISCARDS DOT1QLEARNINGCONSTSTABLE 12.10.10.3.1/4 read read daint/deate/deet/delete/delete/delet ot1qconstraintvlan dot1qconstraintset dot1qconstrainttype dot1qconstraintstatus dot1qconstraintsetdefault dot1qconstrainttypedefault
The following IEEE 802.1Q management objects have not been included in the Bridge MIB for the indicated reasons.
次のIEEE 802.1Q管理オブジェクトは、示された理由でBridge MIBに含まれていません。
IEEE 802.1Q-1998 Operation Disposition
IEEE 802.1Q-1998運用処分
reset bridge (12.4.1.4) not considered useful
リセットブリッジ（12.4.1.4）は有用であるとは見なされません
reset vlan bridge (12.10.1.5) not considered useful
リセットVLANブリッジ（12.10.1.5）は役に立たないと見なされます
read forwarding port counters (12.6.1.1) discard on error details not considered useful
転送ポートカウンター（12.6.1.1）を読むエラーの詳細を破棄してください
read permanent database (12.7.6.1)
permanent database size not considered useful
number of static filtering count rows in
entries dot1qStaticUnicastTable +
dot1qStaticMulticastTable
number of static VLAN count rows in
registration entries dot1qVlanStaticTable
read filtering entry range use GetNext operation. (12.7.7.4)
フィルタリングエントリ範囲を読み取りますgetNext操作を使用します。（12.7.7.4）
read filtering database (12.7.1.1) filtering database size not considered useful number of dynamic group address count rows applicable to each entries (12.7.1.3) FDB in dot1dTpGroupTable
フィルタリングデータベース（12.7.1.1）のフィルタリングデータベースサイズは、dot1dtpgruptableの各エントリに適用される動的グループアドレスカウント行の有用な数のダイナミックグループアドレスカウント行と見なされていません。
read garp state (12.9.3.1) not considered useful
Garp State（12.9.3.1）を読んでください
notify vlan registration failure not considered useful (12.10.1.6)
VLAN登録の失敗に有用と見なされない通知（12.10.1.6）
notify learning constraint violation (12.10.3.10) not considered useful
学習制約違反（12.10.3.10）に役立つとはみなされない
This mandatory group contains the objects which are applicable to all bridges implementing IEEE 802.1Q virtual LANs.
この必須グループには、IEEE 802.1Q仮想LANを実装するすべてのブリッジに適用できるオブジェクトが含まれています。
This group contains objects that control the operation and report the status of transparent bridging. This includes management of the dynamic Filtering Databases for both unicast and multicast forwarding. This group will be implemented by all bridges that perform destination-address filtering.
このグループには、操作を制御し、透明なブリッジングのステータスを報告するオブジェクトが含まれています。これには、ユニキャストとマルチキャストの両方の転送の両方の動的フィルタリングデータベースの管理が含まれます。このグループは、宛先アドレスフィルタリングを実行するすべてのブリッジによって実装されます。
This group contains objects that control static configuration information for transparent bridging. This includes management of the static entries in the Filtering Databases for both unicast and multicast forwarding.
このグループには、透明なブリッジングの静的構成情報を制御するオブジェクトが含まれています。これには、ユニキャストとマルチキャストの両方の転送の両方のフィルタリングデータベースの静的エントリの管理が含まれます。
This group contains objects that control configuration and report status of the Virtual LANs known to a bridge. This includes management of the statically configured VLANs as well as reporting VLANs discovered by other means e.g. GVRP. It also controls configuration and reports status of per-port objects relating to VLANs and reports traffic statistics. It also provides for management of the VLAN Learning Constraints.
このグループには、ブリッジに知られている仮想LANの構成と報告ステータスを制御するオブジェクトが含まれています。これには、静的に構成されたVLANの管理と、他の手段によって発見されたVLANの報告が含まれます。GVRP。また、VLANに関連するポートごとのオブジェクトの構成とレポートのステータスを制御し、トラフィック統計を報告します。また、VLAN学習制約の管理も提供します。
The datatypes MacAddress, BridgeId, Timeout, EnabledStatus, PortList, VlanIndex and VlanId are used as textual conventions in this document. These textual conventions have NO effect on either the syntax nor the semantics of any managed object. Objects defined using these conventions are always encoded by means of the rules that define their primitive type. Hence, no changes to the SMI or the SNMP are necessary to accommodate these textual conventions which are adopted merely for the convenience of readers.
MacAddress、BridgeID、TimeOut、EnabledStatus、ポートリスト、Vlanindex、Vlanidのデータ型は、このドキュメントのテキストの規則として使用されます。これらのテキストの規則は、構文や管理されたオブジェクトのセマンティクスのいずれにも影響しません。これらの規則を使用して定義されたオブジェクトは、原始タイプを定義するルールによって常にエンコードされます。したがって、SMIまたはSNMPの変更は、読者の利便性のためだけに採用されるこれらのテキストの慣習に対応するために必要はありません。
As described above, some IEEE 802.1D management objects have not been included in this MIB because they overlap with objects in other MIBs applicable to a bridge implementing this MIB. In particular, it is assumed that a bridge implementing this MIB will also implement (at least) the 'system' group defined in MIB-II [MIB2], the 'interfaces' group defined in [INTERFACEMIB] and the original bridge MIB [BRIDGEMIB].
上記のように、一部のIEEE 802.1D管理オブジェクトは、このMIBを実装するブリッジに適用される他のMIBのオブジェクトと重複するため、このMIBに含まれていません。特に、このMIBを実装するブリッジは、[少なくとも）MIB-II [MIB2]で定義された「システム」グループ、[Interfacemib]で定義された「インターフェイス」グループ、および元のブリッジMIB [Bridgemibも実装すると想定されています。]。
In MIB-II, the 'system' group is defined as being mandatory for all systems such that each managed entity contains one instance of each object in the 'system' group. Thus, those objects apply to the entity as a whole irrespective of whether the entity's sole functionality is bridging, or whether bridging is only a subset of the entity's functionality.
MIB-IIでは、「システム」グループは、各マネージドエンティティに「システム」グループの各オブジェクトの1つのインスタンスが含まれるように、すべてのシステムに必須であると定義されています。したがって、これらのオブジェクトは、エンティティの唯一の機能がブリッジングであるかどうか、またはブリッジングがエンティティの機能のサブセットのみであるかどうかに関係なく、全体として全体に適用されます。
The Interfaces Group MIB [INTERFACEMIB], requires that any MIB which is an adjunct of the Interfaces Group MIB, clarify specific areas within the Interfaces Group MIB. These areas were intentionally left vague in the Interfaces Group MIB to avoid over-constraining the MIB, thereby precluding management of certain media-types.
インターフェイスグループMIB [Interfacemib]では、インターフェースグループMIBの付属物であるMIBがインターフェースグループMIB内の特定の領域を明確にする必要があります。これらの領域は、MIBの制約を避けるために、インターフェイスグループMIBで意図的に曖昧なままにされ、それにより特定のメディア型の管理を排除しました。
The Interfaces Group MIB enumerates several areas which a media-specific MIB must clarify. Each of these areas is addressed in a following subsection. The implementor is referred to the Interfaces Group MIB in order to understand the general intent of these areas.
インターフェイスグループMIBは、メディア固有のMIBが明確にしなければならないいくつかの領域を列挙しています。これらの各領域は、次のサブセクションで対処されています。実装者は、これらの領域の一般的な意図を理解するために、インターフェイスグループMIBに紹介されます。
In the Interfaces Group MIB, the 'interfaces' group is defined as being mandatory for all systems and contains information on an entity's interfaces, where each interface is thought of as being attached to a `subnetwork'. (Note that this term is not to be confused with `subnet' which refers to an addressing partitioning scheme used in the Internet suite of protocols.) The term 'segment' is used in this memo to refer to such a subnetwork, whether it be an Ethernet segment, a 'ring', a WAN link, or even an X.25 virtual circuit.
インターフェイスグループMIBでは、「インターフェイス」グループはすべてのシステムに必須であると定義され、各インターフェイスが「サブネットワーク」に接続されていると考えられているエンティティのインターフェイスに情報が含まれています。（この用語は、プロトコルのインターネットスイートで使用されるアドレス指定パーティションスキームを指す「サブネット」と混同しないことに注意してください。）「セグメント」という用語は、このメモで使用され、そのようなサブネットワークを参照するために使用されます。イーサネットセグメント、「リング」、WANリンク、またはX.25仮想回路。
Implicit in this Extended Bridge MIB is the notion of ports on a bridge. Each of these ports is associated with one interface of the 'interfaces' group (one row in ifTable) and, in most situations, each port is associated with a different interface. However, there are situations in which multiple ports are associated with the same interface. An example of such a situation would be several ports each corresponding one-to-one with several X.25 virtual circuits but all on the same interface.
この拡張ブリッジMIBで暗黙的には、橋の港の概念です。これらの各ポートは、「インターフェイス」グループ（IFTableの1つの行）の1つのインターフェイスに関連付けられており、ほとんどの場合、各ポートは異なるインターフェイスに関連付けられています。ただし、複数のポートが同じインターフェイスに関連付けられている状況があります。このような状況の例は、いくつかのx.25仮想回路を備えた1対1に対応するいくつかのポートですが、すべて同じインターフェイスにあります。
Each port is uniquely identified by a port number. A port number has no mandatory relationship to an interface number, but in the simple case a port number will have the same value as the corresponding interface's interface number. Port numbers are in the range (1..dot1dBaseNumPorts).
各ポートは、ポート番号で一意に識別されます。ポート番号には、インターフェイス番号との必須関係はありませんが、単純な場合、ポート番号は対応するインターフェイスのインターフェイス番号と同じ値を持ちます。ポート番号は範囲内にあります（1..dot1dbasenumports）。
Some entities perform other functionality as well as bridging through the sending and receiving of data on their interfaces. In such situations, only a subset of the data sent/received on an interface is within the domain of the entity's bridging functionality. This subset is considered to be delineated according to a set of protocols, with some protocols being bridged, and other protocols not being bridged. For example, in an entity which exclusively performed bridging, all protocols would be considered as being bridged, whereas in an entity which performed IP routing on IP datagrams and only bridged other protocols, only the non-IP data would be considered as being bridged. Thus, this Extended Bridge MIB (and in particular, its counters) is applicable only to that subset of the data on an entity's interfaces which is sent/received for a protocol being bridged. All such data is sent/received via the ports of the bridge.
一部のエンティティは、他の機能を実行し、インターフェイス上のデータの送信と受信をブリッジングします。このような状況では、インターフェイスで送信/受信したデータのサブセットのみが、エンティティのブリッジング機能のドメイン内にあります。このサブセットは、一連のプロトコルに従って描写されていると考えられており、一部のプロトコルは橋渡しされており、他のプロトコルはブリッジされていません。たとえば、ブリッジングのみを実行したエンティティでは、すべてのプロトコルがブリッジされていると見なされますが、IPデータグラムでIPルーティングを実行し、他のプロトコルのみをブリッジしたエンティティでは、非IPデータのみがブリッジされていると見なされます。したがって、この拡張されたブリッジMIB（特に、そのカウンター）は、ブリッジされているプロトコルのために送信/受信されるエンティティのインターフェイス上のデータのサブセットにのみ適用できます。そのようなデータはすべて、ブリッジのポートを介して送信/受信されます。
This memo assumes the interpretation of the Interfaces Group to be in accordance with the Interfaces Group MIB [INTERFACEMIB] which states that the interfaces table (ifTable) contains information on the managed resource's interfaces and that each sub-layer below the internetwork layer of a network interface is considered an interface.
このメモは、インターフェイスグループMIB [Interfacemib]に従って、インターフェイスグループの解釈が、インターフェイステーブル（IFTable）にはマネージドリソースのインターフェイスに関する情報が含まれており、ネットワークのインターネットワークレイヤーの下に各サブレイヤーが含まれていることを想定しています。インターフェイスはインターフェイスと見なされます。
This document recommends that, within an entity, VLANs which are instantiated as an entry in dot1qVlanCurrentTable by either management configuration through dot1qVlanStaticTable or by dynamic means (e.g. through GVRP), are NOT also represented by an entry in ifTable.
このドキュメントでは、エンティティ内で、dot1qvlancurrenttableのエントリとしてdot1qvlancurrenttableのエントリとしてインスタンス化されるVLANは、dot1qvlanstatitableまたは動的手段（たとえばGVRPを介して）によって、iftableのエントリによっても表されないことを推奨しています。
Where an entity contains higher-layer protocol entities e.g. IP-layer interfaces that transmit and receive traffic to/from a VLAN, these should be represented in the ifTable as interfaces of type propVirtual(53). Protocol-specific types such as l3ipxvlan(137) should not be used here since there is no implication that the bridge will perform any protocol filtering before delivering up to these virtual interfaces.
エンティティに高層プロトコルエンティティが含まれている場合VLANに出入りするトラフィックを送信および受信するIP層インターフェイスは、これらを型prompvirtualのインターフェイスとしてiftableで表す必要があります（53）。L3IPXVLAN（137）などのプロトコル固有のタイプは、ブリッジがこれらの仮想インターフェイスに配信する前にプロトコルフィルタリングを実行するという意味がないため、ここでは使用しないでください。
In addition, the Interfaces Group MIB [INTERFACEMIB] defines a table 'ifStackTable' for describing the relationship between logical interfaces within an entity. It is anticipated that implementors will use this table to describe the binding of e.g. IP interfaces to physical ports, although the presence of VLANs makes the representation less than perfect for showing connectivity: the ifStackTable cannot represent the full capability of the IEEE 802.1Q VLAN bridging standard since that makes a distinction between VLAN bindings on 'ingress' to and 'egress' from a port: these relationships may or may not be symmetrical whereas Interface MIB Evolution assumes a symmetrical binding for transmit and receive. This makes it necessary to define other manageable objects for configuring which ports are members of which VLANs.
さらに、インターフェイスグループMIB [Interfacemib]は、エンティティ内の論理インターフェイス間の関係を記述するためのテーブル「IfStackTable」を定義します。実装者は、このテーブルを使用して、例えば。物理ポートへのIPインターフェイス。VLANの存在により、接続性を示すのに最適ではありませんが、IFStackTableはIEEE 802.1Q VLANブリッジング標準の完全な能力を表現できません。ポートからの「出口」：これらの関係は対称的である場合とそうでない場合がありますが、インターフェイスMIBの進化は送信および受信の対称的な結合を想定しています。これにより、どのポートがどのVLANメンバーであるかを構成するために、他の管理可能なオブジェクトを定義する必要があります。
This table contains all MAC addresses, unicast, multicast, and broadcast, for which an interface will receive packets and forward them up to a higher layer entity for local consumption. Note that this does not include addresses for data-link layer control protocols such as Spanning-Tree, GMRP or GVRP. The format of the address, contained in ifRcvAddressAddress, is the same as for ifPhysAddress.
このテーブルには、すべてのMACアドレス、ユニキャスト、マルチキャスト、ブロードキャストが含まれています。インターフェイスは、パケットを受信し、ローカル消費のために高層エンティティに転送します。これには、スパニングツリー、GMRP、GVRPなどのデータリンクレイヤー制御プロトコルのアドレスが含まれていないことに注意してください。ifrcvaddressAddressに含まれるアドレスの形式は、ifphysAddressの場合と同じです。
This table does not include unicast or multicast addresses which are accepted for possible forwarding out some other port. This table is explicitly not intended to provide a bridge address filtering mechanism.
このテーブルには、他のポートを転送する可能性があるために受け入れられるユニキャストまたはマルチキャストアドレスは含まれていません。このテーブルは、明示的にブリッジアドレスフィルタリングメカニズムを提供することを意図していません。
This section defines how objects in the original bridge MIB module [BRIDGEMIB] should be represented for devices which implement the extensions: some of the old objects are less useful in such devices but must still be implemented for reasons of backwards compatibility. Note that formal conformance statements for that MIB module do not exist since it is defined in SMIv1.
このセクションでは、元のBridge MIBモジュール[Bridgemib]のオブジェクトを拡張機能を実装するデバイスに表現する方法を定義します。古いオブジェクトの一部は、そのようなデバイスではあまり役に立ちませんが、後方互換性の理由で実装する必要があります。そのMIBモジュールの正式な適合ステートメントは、SMIV1で定義されているため、存在しないことに注意してください。
This mandatory group contains the objects which are applicable to all types of bridges. Interpretation of this group is unchanged.
この必須グループには、あらゆる種類のブリッジに適用可能なオブジェクトが含まれています。このグループの解釈は変更されていません。
This group contains the objects that denote the bridge's state with respect to the Spanning Tree Protocol. Interpretation of this group is unchanged.
このグループには、スパニングツリープロトコルに関してブリッジの状態を示すオブジェクトが含まれています。このグループの解釈は変更されていません。
This group contains objects that describe the entity's state with respect to transparent bridging.
このグループには、透明なブリッジングに関してエンティティの状態を記述するオブジェクトが含まれています。
In a device operating with a single Filtering Database, interpretation of this group is unchanged.
単一のフィルタリングデータベースで動作するデバイスでは、このグループの解釈は変更されていません。
In a device supporting multiple Filtering Databases, this group is interpreted as follows:
複数のフィルタリングデータベースをサポートするデバイスでは、このグループは次のように解釈されます。
dot1dTpLearnedEntryDiscards The number of times that *any* of the FDBs became full.
dot1dtplearnedentrydrydiscards FDBの任意の * *がいっぱいになった回数。
dot1dTpAgingTime This applies to all Filtering Databases.
dot1dtpagingTimeこれは、すべてのフィルタリングデータベースに適用されます。
dot1dTpFdbTable Report MAC addresses learned on each port, regardless of which Filtering Database they have been learnt in. If an address has been learnt in multiple databases on a single port, report it only once. If an address has been learnt in multiple databases on more than one port, report the entry on any one of the valid ports.
DOT1DTPFDBTABLEレポート各ポートで学習したMACアドレスは、どのフィルタリングデータベースで学習されているかに関係なく、単一のポートの複数のデータベースでアドレスが学習されている場合は、1回だけ報告します。複数のポートの複数のデータベースでアドレスが学習されている場合は、有効なポートのいずれかに関するエントリを報告します。
dot1dTpPortTable This table is port-based and is not affected by multiple Filtering Databases or multiple VLANs. The counters should include frames received or transmitted for all VLANs. Note that equivalent 64-bit port statistics counters, as well as other objects to represent the upper 32 bits of these counters, are defined in this document for high capacity network interfaces. These have confromance statements to indicate for which speeds of interface they are required.
DOT1DTPPORTTABLEこのテーブルはポートベースであり、複数のフィルタリングデータベースまたは複数のVLANの影響を受けません。カウンターには、すべてのVLANに対して受信または送信されたフレームを含める必要があります。これらのカウンターの上部32ビットを表すための他のオブジェクトと同様に、同等の64ビットポート統計カウンターと、このドキュメントでは、大容量ネットワークインターフェイスのために定義されていることに注意してください。これらには、どのインターフェースの速度が必要かを示すための声明があります。
This optional group contains objects that describe the configuration of destination-address filtering.
このオプションのグループには、宛先アドレスフィルタリングの構成を記述するオブジェクトが含まれています。
In a device operating with a single Filtering Database, interpretation of this group is unchanged.
単一のフィルタリングデータベースで動作するデバイスでは、このグループの解釈は変更されていません。
In a device supporting multiple Filtering Databases, this group is interpreted as follows:
複数のフィルタリングデータベースをサポートするデバイスでは、このグループは次のように解釈されます。
dot1dStaticTable Entries read from this table include all static entries from all of the Filtering Databases. Entries for the same MAC address and receive port in more than one Filtering Database must appear only once since these are the indices of this table. This table should be implemented as read-only in devices that support multiple Forwarding Databases - instead, write access should be provided through dot1qStaticUnicastTable and dot1qStaticMulticastTable, as defined in this document.
このテーブルから読むdot1dstaticableエントリには、すべてのフィルタリングデータベースからのすべての静的エントリが含まれています。同じMACアドレスのエントリと複数のフィルタリングデータベースのポートを受信するポートを受信すると、これらはこのテーブルのインデックスであるため、1回だけ表示する必要があります。このテーブルは、複数の転送データベースをサポートするデバイスで読み取り専用として実装する必要があります。代わりに、このドキュメントで定義されているように、dot1qstaticunicasttableおよびdot1qstaticmulticastableを介して書き込みアクセスを提供する必要があります。
In addition to the objects in the original bridge MIB [BRIDGEMIB], this document contains:
元のBridge Mib [Bridgemib]のオブジェクトに加えて、このドキュメントには以下が含まれています。
(1) support for multiple traffic classes and dynamic multicast filtering as per IEEE 802.1D-1998 [802.1D].
(1) IEEE 802.1D-1998 [802.1d]に従って、複数のトラフィッククラスと動的マルチキャストフィルタリングのサポート。
(2) support for bridged Virtual LANs as per IEEE 802.1Q-1998 [802.1Q].
(2) IEEE 802.1Q-1998 [802.1Q]に従って、ブリッジ付き仮想LANのサポート。
(3) support for 64-bit versions of original bridge MIB [BRIDGEMIB] port counters.
(3) 元のBridge MIB [Bridgemib]ポートカウンターの64ビットバージョンのサポート。
P-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- -------------------------------------------------------------
-- MIB for IEEE 802.1p devices
-- -------------------------------------------------------------
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64 FROM SNMPv2-SMI TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF dot1dTp, dot1dTpPort, dot1dBridge, dot1dBasePortEntry, dot1dBasePort FROM BRIDGE-MIB;
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64 FROM SNMPv2-SMI TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF dot1dTp, dot1dTpPort, dot1dBridge, dot1dBasePortEntry, dot1dBasePort FROMブリッジミブ;
pBridgeMIB MODULE-IDENTITY LAST-UPDATED "9908250000Z" ORGANIZATION "IETF Bridge MIB Working Group" CONTACT-INFO " Les Bell Postal: 3Com Europe Ltd. 3Com Centre, Boundary Way Hemel Hempstead, Herts. HP2 7YU UK Phone: +44 1442 438025 Email: Les_Bell@3Com.com
PBRIDGEMIBモジュールのアイデンティティ最後の「99082500Z」組織 "IETFブリッジMIBワーキンググループ「コンタクトINFO」レスベル郵便：3com Europe Ltd. 3comセンター、境界ウェイヘメルヘンプステッド、HP2 7YU UK電話：44 1442 438025メール：les_bell@3com.com
Andrew Smith Postal: Extreme Networks 3585 Monroe St. Santa Clara CA 95051 USA Phone: +1 408 579 2821 Email: andrew@extremenetworks.com
Andrew Smith Postal：Extreme Networks 3585 Monroe St. Santa Clara CA 95051 USA電話：1 408 579 2821メール：andrew@extremenetworks.com
Paul Langille Postal: Newbridge Networks 5 Corporate Drive Andover, MA 01810 USA Phone: +1 978 691 4665 Email: langille@newbridge.com
Paul Langille Postal：NewBridge Networks 5 Corporate Drive Andover、MA 01810 USA電話：1 978 691 4665メール：langille@newbridge.com
Anil Rijhsinghani Postal: Cabletron Systems 50 Minuteman Road Andover, MA 01810 USA Phone: +1 978 684 1295 Email: anil@cabletron.com
Anil Rijhsinghani Postal：Cabletron Systems 50 Minuteman Road Andover、MA 01810 USA電話：1 978 684 1295メール：anil@cabletron.com
Keith McCloghrie Postal: cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Phone: +1 408 526 5260 Email: kzm@cisco.com"
Keith McCloghrie Postal：Cisco Systems、Inc。170 West Tasman Drive San Jose、CA 95134-1706 USA電話：1 408 526 5260メール：kzm@cisco.com "
DESCRIPTION "The Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D-1998."
説明「IEEE 802.1D-1998で定義された優先度とマルチキャストフィルタリングを管理するためのブリッジMIB拡張モジュール。」
-- revision history
- 改訂履歴
REVISION "9908250000Z" DESCRIPTION "Initial version, published as RFC 2674."
リビジョン「99082500Z」説明「RFC 2674として公開された初期バージョン」。
::= { dot1dBridge 6 }
pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 }
-- -------------------------------------------------------------
-- Textual Conventions
-- -------------------------------------------------------------
EnabledStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A simple status value for the object."
SYNTAX INTEGER { enabled(1), disabled(2) }
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- groups in the P-BRIDGE MIB
-- -------------------------------------------------------------
dot1dExtBase OBJECT IDENTIFIER ::= { pBridgeMIBObjects 1 }
dot1dPriority OBJECT IDENTIFIER ::= { pBridgeMIBObjects 2 }
dot1dGarp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 3 }
dot1dGmrp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 4 }
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- the dot1dExtBase group
-- -------------------------------------------------------------
dot1dDeviceCapabilities OBJECT-TYPE
SYNTAX BITS {
dot1dExtendedFilteringServices(0),
-- can perform filtering of
-- individual multicast addresses
-- controlled by GMRP.
dot1dTrafficClasses(1),
-- can map user priority to
-- multiple traffic classes.
dot1qStaticEntryIndividualPort(2),
-- dot1qStaticUnicastReceivePort &
-- dot1qStaticMulticastReceivePort
-- can represent non-zero entries.
dot1qIVLCapable(3), -- Independent VLAN Learning.
dot1qSVLCapable(4), -- Shared VLAN Learning.
dot1qHybridCapable(5),
-- both IVL & SVL simultaneously.
dot1qConfigurablePvidTagging(6),
-- whether the implementation
-- supports the ability to
-- override the default PVID
-- setting and its egress status
-- (VLAN-Tagged or Untagged) on
-- each port.
dot1dLocalVlanCapable(7)
-- can support multiple local
-- bridges, outside of the scope
-- of 802.1Q defined VLANs.
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the optional parts of IEEE 802.1D and 802.1Q
that are implemented by this device and are manageable
through this MIB. Capabilities that are allowed on a
per-port basis are indicated in dot1dPortCapabilities."
REFERENCE
"ISO/IEC 15802-3 Section 5.2,
IEEE 802.1Q/D11 Section 5.2, 12.10.1.1.3/b/2"
::= { dot1dExtBase 1 }
dot1dTrafficClassesEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value true(1) indicates that Traffic Classes are
enabled on this bridge. When false(2), the bridge
operates with a single priority level for all traffic."
DEFVAL { true }
::= { dot1dExtBase 2 }
dot1dGmrpStatus OBJECT-TYPE SYNTAX EnabledStatus MAX-ACCESS read-write STATUS current DESCRIPTION
dot1dgmrpstatus object-type syntax enabledstatus max-access read-writeステータス現在の説明
"The administrative status requested by management for
GMRP. The value enabled(1) indicates that GMRP should
be enabled on this device, in all VLANs, on all ports
for which it has not been specifically disabled. When
disabled(2), GMRP is disabled, in all VLANs, on all
ports and all GMRP packets will be forwarded
transparently. This object affects both Applicant and
Registrar state machines. A transition from disabled(2)
to enabled(1) will cause a reset of all GMRP state
machines on all ports."
DEFVAL { enabled }
::= { dot1dExtBase 3 }
-- -------------------------------------------------------------
-- Port Capabilities Table
-- -------------------------------------------------------------
dot1dPortCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains capabilities information about
every port that is associated with this bridge."
::= { dot1dExtBase 4 }
dot1dPortCapabilitiesEntry OBJECT-TYPE
SYNTAX Dot1dPortCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of capabilities information about this port
indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry }
::= { dot1dPortCapabilitiesTable 1 }
Dot1dPortCapabilitiesEntry ::=
SEQUENCE {
dot1dPortCapabilities
BITS
}
dot1dPortCapabilities OBJECT-TYPE
SYNTAX BITS {
dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of
-- frames and GVRP.
dot1qConfigurableAcceptableFrameTypes(1),
-- allows modified values of
-- dot1qPortAcceptableFrameTypes.
dot1qIngressFiltering(2)
-- supports the discarding of any
-- frame received on a Port whose
-- VLAN classification does not
-- include that Port in its Member
-- set.
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the parts of IEEE 802.1D and 802.1Q that are
optional on a per-port basis that are implemented by
this device and are manageable through this MIB."
REFERENCE
"ISO/IEC 15802-3 Section 5.2,
IEEE 802.1Q/D11 Section 5.2"
::= { dot1dPortCapabilitiesEntry 1 }
-- -------------------------------------------------------------
-- the dot1dPriority group
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- Port Priority Table
-- -------------------------------------------------------------
dot1dPortPriorityTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortPriorityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains information about every port that
is associated with this transparent bridge."
::= { dot1dPriority 1 }
dot1dPortPriorityEntry OBJECT-TYPE
SYNTAX Dot1dPortPriorityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Default User Priorities for each port of a
transparent bridge. This is indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry }
::= { dot1dPortPriorityTable 1 }
Dot1dPortPriorityEntry ::=
SEQUENCE {
dot1dPortDefaultUserPriority INTEGER, dot1dPortNumTrafficClasses INTEGER }
dot1dportdefaultususerpriority integer、dot1dportnumtrafficclasses integer}
dot1dPortDefaultUserPriority OBJECT-TYPE
SYNTAX INTEGER (0..7)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The default ingress User Priority for this port. This
only has effect on media, such as Ethernet, that do not
support native User Priority."
::= { dot1dPortPriorityEntry 1 }
dot1dPortNumTrafficClasses OBJECT-TYPE
SYNTAX INTEGER (1..8)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of egress traffic classes supported on this
port. This object may optionally be read-only."
::= { dot1dPortPriorityEntry 2 }
-- -------------------------------------------------------------
-- User Priority Regeneration Table
-- -------------------------------------------------------------
dot1dUserPriorityRegenTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dUserPriorityRegenEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Regenerated User Priorities for each received
User Priority on each port of a bridge. The Regenerated
User Priority value may be used to index the Traffic
Class Table for each input port. This only has effect
on media that support native User Priority. The default
values for Regenerated User Priorities are the same as
the User Priorities."
REFERENCE
"ISO/IEC 15802-3 Section 6.4"
::= { dot1dPriority 2 }
dot1dUserPriorityRegenEntry OBJECT-TYPE
SYNTAX Dot1dUserPriorityRegenEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A mapping of incoming User Priority to a Regenerated
User Priority."
INDEX { dot1dBasePort, dot1dUserPriority }
::= { dot1dUserPriorityRegenTable 1 }
Dot1dUserPriorityRegenEntry ::=
SEQUENCE {
dot1dUserPriority
INTEGER,
dot1dRegenUserPriority
INTEGER
}
dot1dUserPriority OBJECT-TYPE
SYNTAX INTEGER (0..7)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The User Priority for a frame received on this port."
::= { dot1dUserPriorityRegenEntry 1 }
dot1dRegenUserPriority OBJECT-TYPE
SYNTAX INTEGER (0..7)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The Regenerated User Priority the incoming User
Priority is mapped to for this port."
::= { dot1dUserPriorityRegenEntry 2 }
-- -------------------------------------------------------------
-- Traffic Class Table
-- -------------------------------------------------------------
dot1dTrafficClassTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1dTrafficClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table mapping evaluated User Priority to Traffic Class, for forwarding by the bridge. Traffic class is a number in the range (0..(dot1dPortNumTrafficClasses-1))." REFERENCE
DOT1DTRAFFICCLASSTABLEオブジェクトタイプ型dot1dtrafficclassentry max-access not-accessable accessable current現在の説明 "テーブルマッピング評価されたテーブルマッピング評価されたユーザーの優先順位、交通クラス、ブリッジによる転送のために。トラフィッククラスは範囲の数です（0 ..）。」参照
"ISO/IEC 15802-3 Table 7-2"
::= { dot1dPriority 3 }
dot1dTrafficClassEntry OBJECT-TYPE
SYNTAX Dot1dTrafficClassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"User Priority to Traffic Class mapping."
INDEX { dot1dBasePort, dot1dTrafficClassPriority }
::= { dot1dTrafficClassTable 1 }
Dot1dTrafficClassEntry ::=
SEQUENCE {
dot1dTrafficClassPriority
INTEGER,
dot1dTrafficClass
INTEGER
}
dot1dTrafficClassPriority OBJECT-TYPE SYNTAX INTEGER (0..7) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Priority value determined for the received frame. This value is equivalent to the priority indicated in the tagged frame received, or one of the evaluated priorities, determined according to the media-type.
dot1dtrafficclasspriorityオブジェクトタイプの構文整数（0..7）最大アクセスはアクセス不可能なステータス現在の説明 "受信フレームに対して決定される優先値。メディアタイプに従って決定された優先順位。
For untagged frames received from Ethernet media, this value is equal to the dot1dPortDefaultUserPriority value for the ingress port.
イーサネットメディアから受け取った未積層のフレームの場合、この値は、イングレスポートのDOT1DPORTDEFAULTUSUSERPRIORITY値に等しくなります。
For untagged frames received from non-Ethernet media,
this value is equal to the dot1dRegenUserPriority value
for the ingress port and media-specific user priority."
::= { dot1dTrafficClassEntry 1 }
dot1dTrafficClass OBJECT-TYPE
SYNTAX INTEGER (0..7)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The Traffic Class the received frame is mapped to."
::= { dot1dTrafficClassEntry 2 }
-- -------------------------------------------------------------
-- Outbound Access Priority Table
-- -------------------------------------------------------------
dot1dPortOutboundAccessPriorityTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortOutboundAccessPriorityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table mapping Regenerated User Priority to Outbound
Access Priority. This is a fixed mapping for all port
types, with two options for 802.5 Token Ring."
REFERENCE
"ISO/IEC 15802-3 Table 7-3"
::= { dot1dPriority 4 }
dot1dPortOutboundAccessPriorityEntry OBJECT-TYPE
SYNTAX Dot1dPortOutboundAccessPriorityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Regenerated User Priority to Outbound Access Priority
mapping."
INDEX { dot1dBasePort, dot1dRegenUserPriority }
::= { dot1dPortOutboundAccessPriorityTable 1 }
Dot1dPortOutboundAccessPriorityEntry ::=
SEQUENCE {
dot1dPortOutboundAccessPriority
INTEGER
}
dot1dPortOutboundAccessPriority OBJECT-TYPE
SYNTAX INTEGER (0..7)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Outbound Access Priority the received frame is
mapped to."
::= { dot1dPortOutboundAccessPriorityEntry 1 }
-- -------------------------------------------------------------
-- the dot1dGarp group
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- The GARP Port Table
-- -------------------------------------------------------------
dot1dPortGarpTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortGarpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of GARP control information about every bridge
port. This is indexed by dot1dBasePort."
::= { dot1dGarp 1 }
dot1dPortGarpEntry OBJECT-TYPE
SYNTAX Dot1dPortGarpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"GARP control information for a bridge port."
AUGMENTS { dot1dBasePortEntry }
::= { dot1dPortGarpTable 1 }
Dot1dPortGarpEntry ::=
SEQUENCE {
dot1dPortGarpJoinTime
TimeInterval,
dot1dPortGarpLeaveTime
TimeInterval,
dot1dPortGarpLeaveAllTime
TimeInterval
}
dot1dPortGarpJoinTime OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The GARP Join time, in centiseconds."
DEFVAL { 20 }
::= { dot1dPortGarpEntry 1 }
dot1dPortGarpLeaveTime OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The GARP Leave time, in centiseconds."
DEFVAL { 60 }
::= { dot1dPortGarpEntry 2 }
dot1dPortGarpLeaveAllTime OBJECT-TYPE
SYNTAX TimeInterval
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The GARP LeaveAll time, in centiseconds."
DEFVAL { 1000 }
::= { dot1dPortGarpEntry 3 }
-- -------------------------------------------------------------
-- The GMRP Port Configuration and Status Table
-- -------------------------------------------------------------
dot1dPortGmrpTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortGmrpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of GMRP control and status information about
every bridge port. Augments the dot1dBasePortTable."
::= { dot1dGmrp 1 }
dot1dPortGmrpEntry OBJECT-TYPE
SYNTAX Dot1dPortGmrpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"GMRP control and status information for a bridge port."
AUGMENTS { dot1dBasePortEntry }
::= { dot1dPortGmrpTable 1 }
Dot1dPortGmrpEntry ::=
SEQUENCE {
dot1dPortGmrpStatus
EnabledStatus,
dot1dPortGmrpFailedRegistrations
Counter32,
dot1dPortGmrpLastPduOrigin
MacAddress
}
dot1dPortGmrpStatus OBJECT-TYPE
SYNTAX EnabledStatus
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The administrative state of GMRP operation on this port. The
value enabled(1) indicates that GMRP is enabled on this port
in all VLANs as long as dot1dGmrpStatus is also enabled(1).
A value of disabled(2) indicates that GMRP is disabled on
this port in all VLANs: any GMRP packets received will
be silently discarded and no GMRP registrations will be
propagated from other ports. Setting this to a value of
enabled(1) will be stored by the agent but will only take
effect on the GMRP protocol operation if dot1dGmrpStatus
also indicates the value enabled(1). This object affects
all GMRP Applicant and Registrar state machines on this
port. A transition from disabled(2) to enabled(1) will
cause a reset of all GMRP state machines on this port."
DEFVAL { enabled }
::= { dot1dPortGmrpEntry 1 }
dot1dPortGmrpFailedRegistrations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of failed GMRP registrations, for any
reason, in all VLANs, on this port."
::= { dot1dPortGmrpEntry 2 }
dot1dPortGmrpLastPduOrigin OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Source MAC Address of the last GMRP message
received on this port."
::= { dot1dPortGmrpEntry 3 }
-- -------------------------------------------------------------
-- High Capacity Port Table for Transparent Bridges
-- -------------------------------------------------------------
dot1dTpHCPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dTpHCPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains information about every high
capacity port that is associated with this transparent
bridge."
::= { dot1dTp 5 }
dot1dTpHCPortEntry OBJECT-TYPE
SYNTAX Dot1dTpHCPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Statistics information for each high capacity port of a
transparent bridge."
INDEX { dot1dTpPort }
::= { dot1dTpHCPortTable 1 }
Dot1dTpHCPortEntry ::=
SEQUENCE {
dot1dTpHCPortInFrames
Counter64,
dot1dTpHCPortOutFrames
Counter64,
dot1dTpHCPortInDiscards
Counter64
}
dot1dTpHCPortInFrames OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames that have been received by this
port from its segment. Note that a frame received on
the interface corresponding to this port is only counted
by this object if and only if it is for a protocol being
processed by the local bridging function, including
bridge management frames."
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 1 }
dot1dTpHCPortOutFrames OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames."
dot1dtphcportoutframes object-type syntax counter64 max-access読み取り専用ステータス現在そして、それがブリッジ管理フレームを含むローカルブリッジング機能によってプロトコルが処理される場合のみです。」
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 2 }
dot1dTpHCPortInDiscards OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of valid frames that have been received by this
port from its segment which were discarded (i.e.,
filtered) by the Forwarding Process."
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 3 }
-- ----------------------------------------------------
-- Upper part of High Capacity Port Table for Transparent Bridges
-- ----------------------------------------------------
dot1dTpPortOverflowTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1dTpPortOverflowEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table that contains the most-significant bits of statistics counters for ports that are associated with this transparent bridge that are on high capacity interfaces, as defined in the conformance clauses for this table. This table is provided as a way to read 64-bit counters for agents which support only SNMPv1.
dot1dtpportoverflowtableオブジェクトタイプ型dot1dtpportoverflowentry max-access of dot1dtpportoverflowentryはアクセス不可能なステータス現在の説明 "A Table" A Tableの最も重要なビットのテーブルを含むテーブルを含むテーブルを含むテーブルを含むテーブル、この透明なブリッジに関連するポートに関連するポートの統計カウンターを含むテーブル。このテーブルの適合条項。この表は、SNMPV1のみをサポートするエージェントの64ビットカウンターを読み取る方法として提供されます。
Note that the reporting of most-significant and
least-significant counter bits separately runs the risk of
missing an overflow of the lower bits in the interval between
sampling. The manager must be aware of this possibility, even
within the same varbindlist, when interpreting the results of
a request or asynchronous notification."
::= { dot1dTp 6 }
dot1dTpPortOverflowEntry OBJECT-TYPE
SYNTAX Dot1dTpPortOverflowEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The most significant bits of statistics counters for a high
capacity interface of a transparent bridge. Each object is
associated with a corresponding object in dot1dTpPortTable
which indicates the least significant bits of the counter."
INDEX { dot1dTpPort }
::= { dot1dTpPortOverflowTable 1 }
Dot1dTpPortOverflowEntry ::=
SEQUENCE {
dot1dTpPortInOverflowFrames
Counter32,
dot1dTpPortOutOverflowFrames
Counter32,
dot1dTpPortInOverflowDiscards
Counter32
}
dot1dTpPortInOverflowFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated dot1dTpPortInFrames
counter has overflowed."
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpPortOverflowEntry 1 }
dot1dTpPortOutOverflowFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated dot1dTpPortOutFrames
counter has overflowed."
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpPortOverflowEntry 2 }
dot1dTpPortInOverflowDiscards OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated
dot1dTpPortInDiscards counter has overflowed."
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpPortOverflowEntry 3 }
-- -------------------------------------------------------------
-- IEEE 802.1p MIB - Conformance Information
-- -------------------------------------------------------------
pBridgeConformance OBJECT IDENTIFIER ::= { pBridgeMIB 2 }
pBridgeGroups OBJECT IDENTIFIER ::= { pBridgeConformance 1 }
pBridgeCompliances OBJECT IDENTIFIER
::= { pBridgeConformance 2 }
-- -------------------------------------------------------------
-- units of conformance
-- -------------------------------------------------------------
pBridgeExtCapGroup OBJECT-GROUP
OBJECTS {
dot1dDeviceCapabilities,
dot1dPortCapabilities
}
STATUS current
DESCRIPTION
"A collection of objects indicating the optional
capabilites of the device."
::= { pBridgeGroups 1 }
pBridgeDeviceGmrpGroup OBJECT-GROUP
OBJECTS {
dot1dGmrpStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing device-level control
for the Multicast Filtering extended bridge services."
::= { pBridgeGroups 2 }
pBridgeDevicePriorityGroup OBJECT-GROUP
OBJECTS {
dot1dTrafficClassesEnabled
}
STATUS current
DESCRIPTION
"A collection of objects providing device-level control
for the Priority services."
::= { pBridgeGroups 3 }
pBridgeDefaultPriorityGroup OBJECT-GROUP
OBJECTS {
dot1dPortDefaultUserPriority
}
STATUS current
DESCRIPTION
"A collection of objects defining the User Priority
applicable to each port for media which do not support
native User Priority."
::= { pBridgeGroups 4 }
pBridgeRegenPriorityGroup OBJECT-GROUP
OBJECTS {
dot1dRegenUserPriority
}
STATUS current
DESCRIPTION
"A collection of objects defining the User Priorities
applicable to each port for media which support native
User Priority."
::= { pBridgeGroups 5 }
pBridgePriorityGroup OBJECT-GROUP
OBJECTS {
dot1dPortNumTrafficClasses,
dot1dTrafficClass
}
STATUS current
DESCRIPTION
"A collection of objects defining the traffic classes
within a bridge for each evaluated User Priority."
::= { pBridgeGroups 6 }
pBridgeAccessPriorityGroup OBJECT-GROUP
OBJECTS {
dot1dPortOutboundAccessPriority
}
STATUS current
DESCRIPTION
"A collection of objects defining the media dependent
outbound access level for each priority."
::= { pBridgeGroups 7 }
pBridgePortGarpGroup OBJECT-GROUP
OBJECTS {
dot1dPortGarpJoinTime,
dot1dPortGarpLeaveTime,
dot1dPortGarpLeaveAllTime
}
STATUS current
DESCRIPTION
"A collection of objects providing port level control
and status information for GARP operation."
::= { pBridgeGroups 8 }
pBridgePortGmrpGroup OBJECT-GROUP
OBJECTS {
dot1dPortGmrpStatus,
dot1dPortGmrpFailedRegistrations,
dot1dPortGmrpLastPduOrigin
}
STATUS current
DESCRIPTION
"A collection of objects providing port level control
and status information for GMRP operation."
::= { pBridgeGroups 9 }
pBridgeHCPortGroup OBJECT-GROUP
OBJECTS {
dot1dTpHCPortInFrames,
dot1dTpHCPortOutFrames,
dot1dTpHCPortInDiscards
}
STATUS current
DESCRIPTION
"A collection of objects providing 64-bit statistics
counters for high capacity bridge ports."
::= { pBridgeGroups 10 }
pBridgePortOverflowGroup OBJECT-GROUP
OBJECTS {
dot1dTpPortInOverflowFrames,
dot1dTpPortOutOverflowFrames,
dot1dTpPortInOverflowDiscards
}
STATUS current
DESCRIPTION
"A collection of objects providing overflow statistics
counters for high capacity bridge ports."
::= { pBridgeGroups 11 }
-- -------------------------------------------------------------
-- compliance statements
-- -------------------------------------------------------------
pBridgeCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for device support of Priority and Multicast Filtering extended bridging services."
PBRIDGEComplianceモジュールコンプライアンスステータス現在の説明「優先度およびマルチキャストフィルタリングのデバイスサポートのコンプライアンスステートメント拡張ブリッジングサービス。」
MODULE MANDATORY-GROUPS { pBridgeExtCapGroup }
モジュール必須グループ{pbridgeextcapgroup}
GROUP pBridgeDeviceGmrpGroup DESCRIPTION "This group is mandatory for devices supporting the GMRP application, defined by IEEE 802.1D Extended Filtering Services."
グループPBRIDGEDEVICEGMRPGROUP説明「このグループは、IEEE 802.1d拡張フィルタリングサービスによって定義されたGMRPアプリケーションをサポートするデバイスに必須です。」
GROUP pBridgeDevicePriorityGroup DESCRIPTION "This group is mandatory only for devices supporting the priority forwarding operations defined by IEEE 802.1D."
グループPBRIDGEDEVICEPRIORITYGROUP説明「このグループは、IEEE 802.1dによって定義された優先転送操作をサポートするデバイスにのみ必須です。」
GROUP pBridgeDefaultPriorityGroup DESCRIPTION "This group is mandatory only for devices supporting the priority forwarding operations defined by the extended bridge services with media types, such as Ethernet, that do not support native User Priority."
グループPBRIDGEDEFAULTPRIORITYGROUP説明「このグループは、イーサネットなどのメディアタイプを使用して、ネイティブユーザーの優先度をサポートしないメディアタイプを使用して定義された優先転送操作をサポートするデバイスにのみ必須です。」
GROUP pBridgeRegenPriorityGroup DESCRIPTION "This group is mandatory only for devices supporting the priority forwarding operations defined by IEEE 802.1D and which have interface media types that support native User Priority e.g. IEEE 802.5."
グループPBRIDGEREGENPRIORITYGROUP説明「このグループは、IEEE 802.1Dによって定義された優先転送操作をサポートし、ネイティブユーザーの優先度をサポートするインターフェイスメディアタイプなどを備えたデバイスにのみ必須です。
GROUP pBridgePriorityGroup DESCRIPTION "This group is mandatory only for devices supporting the priority forwarding operations defined by IEEE 802.1D."
グループPBRIDGEPRIORITYGROUP説明「このグループは、IEEE 802.1dによって定義された優先転送操作をサポートするデバイスにのみ必須です。」
GROUP pBridgeAccessPriorityGroup DESCRIPTION "This group is optional and is relevant only for devices supporting the priority forwarding operations defined by IEEE 802.1D and which have interface media types that support native Access Priority e.g. IEEE 802.5."
グループPBRIDGEACESCESSPRIORITYGROUP説明「このグループはオプションであり、IEEE 802.1Dによって定義された優先転送操作をサポートするデバイスにのみ関連し、ネイティブアクセスの優先度などのインターフェイスメディアタイプを備えています。
GROUP pBridgePortGarpGroup DESCRIPTION "This group is mandatory for devices supporting any of the GARP applications: e.g. GMRP, defined by the extended filtering services of 802.1D; or GVRP, defined by 802.1Q (refer to the Q-BRIDGE-MIB for conformance statements for GVRP)."
グループPBRIDGEPORTGARPGROUP説明「このグループは、GARPアプリケーションのいずれかをサポートするデバイスに必須です。たとえば、802.1Dの拡張フィルタリングサービスで定義されています。GVRP）。」
GROUP pBridgePortGmrpGroup DESCRIPTION "This group is mandatory for devices supporting the GMRP application, as defined by IEEE 802.1D Extended Filtering Services."
グループPBRIDGEPORTGMRPGROUP説明「このグループは、IEEE 802.1D拡張フィルタリングサービスで定義されているように、GMRPアプリケーションをサポートするデバイスに必須です。」
GROUP pBridgeHCPortGroup DESCRIPTION "Support for this group in a device is mandatory for those bridge ports which map to network interfaces that have the value of the corresponding instance of ifSpeed greater than 650,000,000 bits/second."
グループPBRIDGEHCPORTGROUPの説明「デバイス内のこのグループのサポートは、650,000,000ビット/秒を超えるIFSPEDの対応するインスタンスの値を持つネットワークインターフェイスにマッピングするブリッジポートには必須です。」
GROUP pBridgePortOverflowGroup DESCRIPTION "Support for this group in a device is mandatory for those bridge ports which map to network interfaces that have the value of the corresponding instance of ifSpeed greater than 650,000,000 bits/second."
グループPBRIDGEPORTOVERFLOWGROUP説明「デバイス内のこのグループのサポートは、650,000,000ビット/秒を超えるIFSPEDの対応するインスタンスの値を持つネットワークインターフェイスにマッピングされるブリッジポートに必須です。」
OBJECT dot1dPortNumTrafficClasses MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトdot1dportnumtrafficclasses min-access読み取り専用説明「書き込みアクセスは必要ありません」。
OBJECT dot1dTrafficClass MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトdot1dtrafficclass min-access読み取り専用説明「書き込みアクセスは不要です。」
OBJECT dot1dRegenUserPriority MIN-ACCESS read-only DESCRIPTION "Write access is not required."
オブジェクトdot1dregenuserpriority min-access読み取り専用説明「書き込みアクセスは不要です。」
::= { pBridgeCompliances 1 }
END
終わり
Q-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- -------------------------------------------------------------
-- MIB for IEEE 802.1Q Devices
-- -------------------------------------------------------------
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64, Unsigned32, TimeTicks FROM SNMPv2-SMI RowStatus, TruthValue, TEXTUAL-CONVENTION, MacAddress FROM SNMPv2-TC SnmpAdminString FROM SNMP-FRAMEWORK-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF dot1dBridge, dot1dBasePortEntry, dot1dBasePort FROM BRIDGE-MIB EnabledStatus FROM P-BRIDGE-MIB TimeFilter FROM RMON2-MIB;
インポートモジュールアイデンティティ、オブジェクトタイプ、カウンター32、カウンター64、unsigned32、snmpv2-smi rowstatus、truthvalue、textual convention、snmpv2-tc snmpadminstringからのMacAddress from snmp-framework-mib module-compliang、SNMPV2-2-2-2-2-2-2-GROUPからのMacAddressconf dot1dbridge、dot1dbaseportentry、dot1dbaseport bridge-mib enabledStatusのrmon2-mibのp-bridge-mib timefilter;
qBridgeMIB MODULE-IDENTITY LAST-UPDATED "9908250000Z" ORGANIZATION "IETF Bridge MIB Working Group" CONTACT-INFO " Les Bell Postal: 3Com Europe Ltd. 3Com Centre, Boundary Way Hemel Hempstead, Herts. HP2 7YU UK Phone: +44 1442 438025 Email: Les_Bell@3Com.com
QBRIDGEMIBモジュール同一性最後の「99082500Z」組織 "IETFブリッジMIBワーキンググループ「コンタクトINFO" LES BELL POSAL：3COM Europe Ltd. 3com Center、Boundary Way Hemel Hempstead、HP2 7YU UK電話：44 1442 438025メール：les_bell@3com.com
Andrew Smith Postal: Extreme Networks 3585 Monroe St. Santa Clara CA 95051 USA Phone: +1 408 579 2821 Email: andrew@extremenetworks.com
Andrew Smith Postal：Extreme Networks 3585 Monroe St. Santa Clara CA 95051 USA電話：1 408 579 2821メール：andrew@extremenetworks.com
Paul Langille Postal: Newbridge Networks 5 Corporate Drive Andover, MA 01810 USA Phone: +1 978 691 4665 Email: langille@newbridge.com
Paul Langille Postal：NewBridge Networks 5 Corporate Drive Andover、MA 01810 USA電話：1 978 691 4665メール：langille@newbridge.com
Anil Rijhsinghani Postal: Cabletron Systems 50 Minuteman Road Andover, MA 01810 USA Phone: +1 978 684 1295 Email: anil@cabletron.com
Anil Rijhsinghani Postal：Cabletron Systems 50 Minuteman Road Andover、MA 01810 USA電話：1 978 684 1295メール：anil@cabletron.com
Keith McCloghrie Postal: cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Phone: +1 408 526 5260 Email: kzm@cisco.com" DESCRIPTION "The VLAN Bridge MIB module for managing Virtual Bridged Local Area Networks, as defined by IEEE 802.1Q-1998."
Keith McCloghrie Postal：Cisco Systems、Inc。170 West Tasman Drive San Jose、CA 95134-1706 USA電話：1 408 52655260メール：kzm@cisco.com "説明"仮想ブリッジ型のローカルエリアネットコークを管理するためのVLAN Bridge MIBモジュール、IEEE 802.1Q-1998で定義されています。」
-- revision history
- 改訂履歴
REVISION "9908250000Z" DESCRIPTION "Initial version, published as RFC 2674."
リビジョン「99082500Z」説明「RFC 2674として公開された初期バージョン」。
::= { dot1dBridge 7 }
qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 }
-- -------------------------------------------------------------
-- Textual Conventions
-- -------------------------------------------------------------
PortList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Each octet within this value specifies a set of eight
ports, with the first octet specifying ports 1 through
8, the second octet specifying ports 9 through 16, etc.
Within each octet, the most significant bit represents
the lowest numbered port, and the least significant bit
represents the highest numbered port. Thus, each port
of the bridge is represented by a single bit within the
value of this object. If that bit has a value of '1'
then that port is included in the set of ports; the port
is not included if its bit has a value of '0'."
SYNTAX OCTET STRING
VlanIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value used to index per-VLAN tables: values of 0 and
4095 are not permitted; if the value is between 1 and
4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with
global scope within a given bridged domain (see VlanId
textual convention). If the value is greater than 4095
then it represents a VLAN with scope local to the
particular agent, i.e. one without a global VLAN-ID
assigned to it. Such VLANs are outside the scope of
IEEE 802.1Q but it is convenient to be able to manage them
in the same way using this MIB."
SYNTAX Unsigned32
VlanId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A 12-bit VLAN ID used in the VLAN Tag header."
SYNTAX INTEGER (1..4094)
-- -------------------------------------------------------------
-- groups in the Q-BRIDGE MIB
-- -------------------------------------------------------------
dot1qBase OBJECT IDENTIFIER ::= { qBridgeMIBObjects 1 }
dot1qTp OBJECT IDENTIFIER ::= { qBridgeMIBObjects 2 }
dot1qStatic OBJECT IDENTIFIER ::= { qBridgeMIBObjects 3 }
dot1qVlan OBJECT IDENTIFIER ::= { qBridgeMIBObjects 4 }
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- dot1qBase group
-- -------------------------------------------------------------
dot1qVlanVersionNumber OBJECT-TYPE
SYNTAX INTEGER {
version1(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The version number of IEEE 802.1Q that this device
supports."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.1"
::= { dot1qBase 1 }
dot1qMaxVlanId OBJECT-TYPE
SYNTAX VlanId
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum IEEE 802.1Q VLAN ID that this device
supports."
REFERENCE
"IEEE 802.1Q/D11 Section 9.3.2.3"
::= { dot1qBase 2 }
dot1qMaxSupportedVlans OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of IEEE 802.1Q VLANs that this
device supports."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.1"
::= { dot1qBase 3 }
dot1qNumVlans OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of IEEE 802.1Q VLANs that are
configured in this device."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.1.1"
::= { dot1qBase 4 }
dot1qGvrpStatus OBJECT-TYPE
SYNTAX EnabledStatus
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The administrative status requested by management for
GVRP. The value enabled(1) indicates that GVRP should
be enabled on this device, on all ports for which it has
not been specifically disabled. When disabled(2), GVRP
is disabled on all ports and all GVRP packets will be
forwarded transparently. This object affects all GVRP
Applicant and Registrar state machines. A transition
from disabled(2) to enabled(1) will cause a reset of all
GVRP state machines on all ports."
DEFVAL { enabled }
::= { dot1qBase 5 }
-- -------------------------------------------------------------
-- the dot1qTp group
-- -------------------------------------------------------------
-- -------------------------------------------------------------
-- the current Filtering Database Table
-- -------------------------------------------------------------
dot1qFdbTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qFdbEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains configuration and control
information for each Filtering Database currently
operating on this device. Entries in this table appear
automatically when VLANs are assigned FDB IDs in the
dot1qVlanCurrentTable."
::= { dot1qTp 1 }
dot1qFdbEntry OBJECT-TYPE
SYNTAX Dot1qFdbEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a specific Filtering Database."
INDEX { dot1qFdbId }
::= { dot1qFdbTable 1 }
Dot1qFdbEntry ::=
SEQUENCE {
dot1qFdbId
Unsigned32,
dot1qFdbDynamicCount
Counter32
}
dot1qFdbId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The identity of this Filtering Database."
::= { dot1qFdbEntry 1 }
dot1qFdbDynamicCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of dynamic entries in this
Filtering Database."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.1.1.3"
::= { dot1qFdbEntry 2 }
-- -------------------------------------------------------------
-- Multiple Forwarding Databases for 802.1Q Transparent devices
-- This table is an alternative to the dot1dTpFdbTable,
-- previously defined for 802.1D devices which only support a
-- single Forwarding Database.
-- -------------------------------------------------------------
dot1qTpFdbTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qTpFdbEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains information about unicast entries
for which the device has forwarding and/or filtering
information. This information is used by the
transparent bridging function in determining how to
propagate a received frame."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7"
::= { dot1qTp 2 }
dot1qTpFdbEntry OBJECT-TYPE
SYNTAX Dot1qTpFdbEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a specific unicast MAC address for
which the device has some forwarding and/or filtering
information."
INDEX { dot1qFdbId, dot1qTpFdbAddress }
::= { dot1qTpFdbTable 1 }
Dot1qTpFdbEntry ::=
SEQUENCE {
dot1qTpFdbAddress
MacAddress,
dot1qTpFdbPort
INTEGER,
dot1qTpFdbStatus
INTEGER
}
dot1qTpFdbAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unicast MAC address for which the device has
forwarding and/or filtering information."
::= { dot1qTpFdbEntry 1 }
dot1qTpFdbPort OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Either the value '0', or the port number of the port on
which a frame having a source address equal to the value
of the corresponding instance of dot1qTpFdbAddress has
been seen. A value of '0' indicates that the port
number has not been learned but that the device does
have some forwarding/filtering information about this
address (e.g. in the dot1qStaticUnicastTable).
Implementors are encouraged to assign the port value to
this object whenever it is learned even for addresses
for which the corresponding value of dot1qTpFdbStatus is
not learned(3)."
::= { dot1qTpFdbEntry 2 }
dot1qTpFdbStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
invalid(2),
learned(3),
self(4),
mgmt(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The status of this entry. The meanings of the values
are:
other(1) - none of the following. This may include
the case where some other MIB object (not the
corresponding instance of dot1qTpFdbPort, nor an
entry in the dot1qStaticUnicastTable) is being
used to determine if and how frames addressed to
the value of the corresponding instance of
dot1qTpFdbAddress are being forwarded.
invalid(2) - this entry is no longer valid (e.g., it
was learned but has since aged out), but has not
yet been flushed from the table.
learned(3) - the value of the corresponding instance
of dot1qTpFdbPort was learned and is being used.
self(4) - the value of the corresponding instance of
dot1qTpFdbAddress represents one of the device's
addresses. The corresponding instance of
dot1qTpFdbPort indicates which of the device's
ports has this address.
mgmt(5) - the value of the corresponding instance of
dot1qTpFdbAddress is also the value of an
existing instance of dot1qStaticAddress."
::= { dot1qTpFdbEntry 3 }
-- -------------------------------------------------------------
-- Dynamic Group Registration Table
-- -------------------------------------------------------------
dot1qTpGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qTpGroupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing filtering information for VLANs
configured into the bridge by (local or network)
management, or learnt dynamically, specifying the set of
ports to which frames received on a VLAN for this FDB
and containing a specific Group destination address are
allowed to be forwarded."
::= { dot1qTp 3 }
dot1qTpGroupEntry OBJECT-TYPE
SYNTAX Dot1qTpGroupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Filtering information configured into the bridge by
management, or learnt dynamically, specifying the set of
ports to which frames received on a VLAN and containing
a specific Group destination address, are allowed to be
forwarded. The subset of these ports learnt dynamically
is also provided."
INDEX { dot1qVlanIndex, dot1qTpGroupAddress }
::= { dot1qTpGroupTable 1 }
Dot1qTpGroupEntry ::=
SEQUENCE {
dot1qTpGroupAddress
MacAddress,
dot1qTpGroupEgressPorts
PortList,
dot1qTpGroupLearnt
PortList }
ポートリスト}
dot1qTpGroupAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The destination Group MAC address in a frame to which
this entry's filtering information applies."
::= { dot1qTpGroupEntry 1 }
dot1qTpGroupEgressPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The complete set of ports, in this VLAN, to which
frames destined for this Group MAC address are currently
being explicitly forwarded. This does not include ports
for which this address is only implicitly forwarded, in
the dot1qForwardAllPorts list."
::= { dot1qTpGroupEntry 2 }
dot1qTpGroupLearnt OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The subset of ports in dot1qTpGroupEgressPorts which
were learnt by GMRP or some other dynamic mechanism, in
this Filtering database."
::= { dot1qTpGroupEntry 3 }
-- -------------------------------------------------------------
-- Service Requirements Group
-- -------------------------------------------------------------
dot1qForwardAllTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qForwardAllEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing forwarding information for each
VLAN, specifying the set of ports to which forwarding of
all multicasts applies, configured statically by
management or dynamically by GMRP. An entry appears in
this table for all VLANs that are currently
instantiated."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.2, 12.7.7"
::= { dot1qTp 4 }
dot1qForwardAllEntry OBJECT-TYPE
SYNTAX Dot1qForwardAllEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Forwarding information for a VLAN, specifying the set
of ports to which all multicasts should be forwarded,
configured statically by management or dynamically by
GMRP."
INDEX { dot1qVlanIndex }
::= { dot1qForwardAllTable 1 }
Dot1qForwardAllEntry ::=
SEQUENCE {
dot1qForwardAllPorts
PortList,
dot1qForwardAllStaticPorts
PortList,
dot1qForwardAllForbiddenPorts
PortList
}
dot1qForwardAllPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The complete set of ports in this VLAN to which all
multicast group-addressed frames are to be forwarded.
This includes ports for which this need has been
determined dynamically by GMRP, or configured statically
by management."
::= { dot1qForwardAllEntry 1 }
dot1qForwardAllStaticPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports configured by management in this VLAN
to which all multicast group-addressed frames are to be
forwarded. Ports entered in this list will also appear
in the complete set shown by dot1qForwardAllPorts. This
value will be restored after the device is reset. This
only applies to ports that are members of the VLAN,
defined by dot1qVlanCurrentEgressPorts. A port may not
be added in this set if it is already a member of the
set of ports in dot1qForwardAllForbiddenPorts. The
default value is a string of ones of appropriate length,
to indicate standard non-EFS behaviour, i.e. forward
all multicasts to all ports."
::= { dot1qForwardAllEntry 2 }
dot1qForwardAllForbiddenPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports configured by management in this VLAN
for which the Service Requirement attribute Forward All
Multicast Groups may not be dynamically registered by
GMRP. This value will be restored after the device is
reset. A port may not be added in this set if it is
already a member of the set of ports in
dot1qForwardAllStaticPorts. The default value is a
string of zeros of appropriate length."
::= { dot1qForwardAllEntry 3 }
dot1qForwardUnregisteredTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qForwardUnregisteredEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing forwarding information for each
VLAN, specifying the set of ports to which forwarding of
multicast group-addressed frames for which there is no
more specific forwarding information applies. This is
configured statically by management and determined
dynamically by GMRP. An entry appears in this table for
all VLANs that are currently instantiated."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.2, 12.7.7"
::= { dot1qTp 5 }
dot1qForwardUnregisteredEntry OBJECT-TYPE
SYNTAX Dot1qForwardUnregisteredEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Forwarding information for a VLAN, specifying the set
of ports to which all multicasts for which there is no
more specific forwarding information shall be forwarded.
This is configured statically by management or
dynamically by GMRP."
INDEX { dot1qVlanIndex }
::= { dot1qForwardUnregisteredTable 1 }
Dot1qForwardUnregisteredEntry ::=
SEQUENCE {
dot1qForwardUnregisteredPorts
PortList,
dot1qForwardUnregisteredStaticPorts
PortList,
dot1qForwardUnregisteredForbiddenPorts
PortList
}
dot1qForwardUnregisteredPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The complete set of ports in this VLAN to which
multicast group-addressed frames for which there is no
more specific forwarding information will be forwarded.
This includes ports for which this need has been
determined dynamically by GMRP, or configured statically
by management."
::= { dot1qForwardUnregisteredEntry 1 }
dot1qForwardUnregisteredStaticPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports configured by management, in this
VLAN, to which multicast group-addressed frames for
which there is no more specific forwarding information
are to be forwarded. Ports entered in this list will
also appear in the complete set shown by
dot1qForwardUnregisteredPorts. This value will be
restored after the device is reset. A port may not be
added in this set if it is already a member of the set
of ports in dot1qForwardUnregisteredForbiddenPorts. The
default value is a string of zeros of appropriate
length, although this has no effect with the default
value of dot1qForwardAllStaticPorts."
::= { dot1qForwardUnregisteredEntry 2 }
dot1qForwardUnregisteredForbiddenPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports configured by management in this VLAN
for which the Service Requirement attribute Forward
Unregistered Multicast Groups may not be dynamically
registered by GMRP. This value will be restored after
the device is reset. A port may not be added in this
set if it is already a member of the set of ports in
dot1qForwardUnregisteredStaticPorts. The default value
is a string of zeros of appropriate length."
::= { dot1qForwardUnregisteredEntry 3 }
-- -------------------------------------------------------------
-- The Static (Destination-Address Filtering) Database
-- -------------------------------------------------------------
dot1qStaticUnicastTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qStaticUnicastEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing filtering information for Unicast
MAC addresses for each Filtering Database, configured
into the device by (local or network) management
specifying the set of ports to which frames received
from specific ports and containing specific unicast
destination addresses are allowed to be forwarded. A
value of zero in this table as the port number from
which frames with a specific destination address are
received, is used to specify all ports for which there
is no specific entry in this table for that particular
destination address. Entries are valid for unicast
addresses only."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7,
ISO/IEC 15802-3 Section 7.9.1"
::= { dot1qStatic 1 }
dot1qStaticUnicastEntry OBJECT-TYPE
SYNTAX Dot1qStaticUnicastEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Filtering information configured into the device by
(local or network) management specifying the set of
ports to which frames received from a specific port and
containing a specific unicast destination address are
allowed to be forwarded."
INDEX {
dot1qFdbId,
dot1qStaticUnicastAddress,
dot1qStaticUnicastReceivePort
}
::= { dot1qStaticUnicastTable 1 }
Dot1qStaticUnicastEntry ::=
SEQUENCE {
dot1qStaticUnicastAddress
MacAddress,
dot1qStaticUnicastReceivePort
INTEGER,
dot1qStaticUnicastAllowedToGoTo
PortList,
dot1qStaticUnicastStatus
INTEGER
}
dot1qStaticUnicastAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The destination MAC address in a frame to which this
entry's filtering information applies. This object must
take the value of a unicast address."
::= { dot1qStaticUnicastEntry 1 }
dot1qStaticUnicastReceivePort OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Either the value '0', or the port number of the port
from which a frame must be received in order for this
entry's filtering information to apply. A value of zero
indicates that this entry applies on all ports of the
device for which there is no other applicable entry."
::= { dot1qStaticUnicastEntry 2 }
dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports for which a frame with a specific
unicast address will be flooded in the event that it
has not been learned. It also specifies the set of
ports a specific unicast address may be dynamically
learnt on. The dot1qTpFdbTable will have an equivalent
entry with a dot1qTpFdbPort value of '0' until this
address has been learnt, when it will be updated with
the port the address has been seen on. This only
applies to ports that are members of the VLAN, defined
by dot1qVlanCurrentEgressPorts. The default value of
this object is a string of ones of appropriate length."
REFERENCE
"IEEE 802.1Q/D11 Table 8-5, ISO/IEC 15802-3 Table 7-5"
::= { dot1qStaticUnicastEntry 3 }
dot1qStaticUnicastStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
invalid(2),
permanent(3),
deleteOnReset(4),
deleteOnTimeout(5)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the status of this entry.
other(1) - this entry is currently in use but
the conditions under which it will remain
so differ from the following values.
invalid(2) - writing this value to the object
removes the corresponding entry.
permanent(3) - this entry is currently in use
and will remain so after the next reset of
the bridge.
deleteOnReset(4) - this entry is currently in
use and will remain so until the next
reset of the bridge.
deleteOnTimeout(5) - this entry is currently in
use and will remain so until it is aged out."
DEFVAL { permanent }
::= { dot1qStaticUnicastEntry 4 }
dot1qStaticMulticastTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qStaticMulticastEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing filtering information for Multicast
and Broadcast MAC addresses for each VLAN, configured
into the device by (local or network) management
specifying the set of ports to which frames received
from specific ports and containing specific Multicast
and Broadcast destination addresses are allowed to be
forwarded. A value of zero in this table as the port
number from which frames with a specific destination
address are received, is used to specify all ports for
which there is no specific entry in this table for that
particular destination address. Entries are valid for
Multicast and Broadcast addresses only."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7,
ISO/IEC 15802-3 Section 7.9.1"
::= { dot1qStatic 2 }
dot1qStaticMulticastEntry OBJECT-TYPE
SYNTAX Dot1qStaticMulticastEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Filtering information configured into the device by
(local or network) management specifying the set of
ports to which frames received from this specific port
for this VLAN and containing this Multicast or Broadcast
destination address are allowed to be forwarded."
INDEX {
dot1qVlanIndex,
dot1qStaticMulticastAddress,
dot1qStaticMulticastReceivePort
}
::= { dot1qStaticMulticastTable 1 }
Dot1qStaticMulticastEntry ::=
SEQUENCE {
dot1qStaticMulticastAddress
MacAddress,
dot1qStaticMulticastReceivePort
INTEGER,
dot1qStaticMulticastStaticEgressPorts
PortList,
dot1qStaticMulticastForbiddenEgressPorts
PortList,
dot1qStaticMulticastStatus
INTEGER
}
dot1qStaticMulticastAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The destination MAC address in a frame to which this
entry's filtering information applies. This object must
take the value of a Multicast or Broadcast address."
::= { dot1qStaticMulticastEntry 1 }
dot1qStaticMulticastReceivePort OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Either the value '0', or the port number of the port
from which a frame must be received in order for this
entry's filtering information to apply. A value of zero
indicates that this entry applies on all ports of the
device for which there is no other applicable entry."
::= { dot1qStaticMulticastEntry 2 }
dot1qStaticMulticastStaticEgressPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports to which frames received from a
specific port and destined for a specific Multicast or
Broadcast MAC address must be forwarded, regardless of
any dynamic information e.g. from GMRP. A port may not
be added in this set if it is already a member of the
set of ports in dot1qStaticMulticastForbiddenEgressPorts.
The default value of this object is a string of ones of
appropriate length."
::= { dot1qStaticMulticastEntry 3 }
dot1qStaticMulticastForbiddenEgressPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports to which frames received from a
specific port and destined for a specific Multicast or
Broadcast MAC address must not be forwarded, regardless
of any dynamic information e.g. from GMRP. A port may
not be added in this set if it is already a member of the
set of ports in dot1qStaticMulticastStaticEgressPorts.
The default value of this object is a string of zeros of
appropriate length."
::= { dot1qStaticMulticastEntry 4 }
dot1qStaticMulticastStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
invalid(2),
permanent(3),
deleteOnReset(4),
deleteOnTimeout(5)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the status of this entry.
other(1) - this entry is currently in use but
the conditions under which it will remain
so differ from the following values.
invalid(2) - writing this value to the object
removes the corresponding entry.
permanent(3) - this entry is currently in use
and will remain so after the next reset of
the bridge.
deleteOnReset(4) - this entry is currently in
use and will remain so until the next
reset of the bridge.
deleteOnTimeout(5) - this entry is currently in
use and will remain so until it is aged out."
DEFVAL { permanent }
::= { dot1qStaticMulticastEntry 5 }
-- -------------------------------------------------------------
-- The Current VLAN Database
-- -------------------------------------------------------------
dot1qVlanNumDeletes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times a VLAN entry has been deleted from
the dot1qVlanCurrentTable (for any reason). If an entry
is deleted, then inserted, and then deleted, this
counter will be incremented by 2."
::= { dot1qVlan 1 }
dot1qVlanCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qVlanCurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing current configuration information
for each VLAN currently configured into the device by
(local or network) management, or dynamically created
as a result of GVRP requests received."
::= { dot1qVlan 2 }
dot1qVlanCurrentEntry OBJECT-TYPE
SYNTAX Dot1qVlanCurrentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information for a VLAN configured into the device by
(local or network) management, or dynamically created
as a result of GVRP requests received."
INDEX { dot1qVlanTimeMark, dot1qVlanIndex }
::= { dot1qVlanCurrentTable 1 }
Dot1qVlanCurrentEntry ::=
SEQUENCE {
dot1qVlanTimeMark
TimeFilter,
dot1qVlanIndex
VlanIndex,
dot1qVlanFdbId
Unsigned32,
dot1qVlanCurrentEgressPorts
PortList,
dot1qVlanCurrentUntaggedPorts
PortList,
dot1qVlanStatus
INTEGER,
dot1qVlanCreationTime
TimeTicks
}
dot1qVlanTimeMark OBJECT-TYPE
SYNTAX TimeFilter
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A TimeFilter for this entry. See the TimeFilter
textual convention to see how this works."
::= { dot1qVlanCurrentEntry 1 }
dot1qVlanIndex OBJECT-TYPE
SYNTAX VlanIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VLAN-ID or other identifier refering to this VLAN."
::= { dot1qVlanCurrentEntry 2 }
dot1qVlanFdbId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Filtering Database used by this VLAN. This is one
of the dot1qFdbId values in the dot1qFdbTable. This
value is allocated automatically by the device whenever
the VLAN is created: either dynamically by GVRP, or by
management, in dot1qVlanStaticTable. Allocation of this
value follows the learning constraints defined for this
VLAN in dot1qLearningConstraintsTable."
::= { dot1qVlanCurrentEntry 3 }
dot1qVlanCurrentEgressPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of ports which are transmitting traffic for
this VLAN as either tagged or untagged frames."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanCurrentEntry 4 }
dot1qVlanCurrentUntaggedPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The set of ports which are transmitting traffic for
this VLAN as untagged frames."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanCurrentEntry 5 }
dot1qVlanStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
permanent(2),
dynamicGvrp(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the status of this entry.
other(1) - this entry is currently in use but the
conditions under which it will remain so differ
from the following values.
permanent(2) - this entry, corresponding to an entry
in dot1qVlanStaticTable, is currently in use and
will remain so after the next reset of the
device. The port lists for this entry include
ports from the equivalent dot1qVlanStaticTable
entry and ports learnt dynamically.
dynamicGvrp(3) - this entry is currently in use
and will remain so until removed by GVRP. There
is no static entry for this VLAN and it will be
removed when the last port leaves the VLAN."
::= { dot1qVlanCurrentEntry 6 }
dot1qVlanCreationTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this VLAN was created."
::= { dot1qVlanCurrentEntry 7 }
-- -------------------------------------------------------------
-- The Static VLAN Database
-- -------------------------------------------------------------
dot1qVlanStaticTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qVlanStaticEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing static configuration information for
each VLAN configured into the device by (local or
network) management. All entries are permanent and will
be restored after the device is reset."
::= { dot1qVlan 3 }
dot1qVlanStaticEntry OBJECT-TYPE
SYNTAX Dot1qVlanStaticEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Static information for a VLAN configured into the
device by (local or network) management."
INDEX { dot1qVlanIndex }
::= { dot1qVlanStaticTable 1 }
Dot1qVlanStaticEntry ::=
SEQUENCE {
dot1qVlanStaticName
SnmpAdminString,
dot1qVlanStaticEgressPorts
PortList,
dot1qVlanForbiddenEgressPorts
PortList,
dot1qVlanStaticUntaggedPorts PortList, dot1qVlanStaticRowStatus RowStatus }
dot1qvlanstaticuntaggedportsポートリスト、dot1qvlanstaticrowstatus rowstatus}}
dot1qVlanStaticName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An administratively assigned string, which may be used
to identify the VLAN."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 1 }
dot1qVlanStaticEgressPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The set of ports which are permanently assigned to the
egress list for this VLAN by management. Changes to a
bit in this object affect the per-port per-VLAN
Registrar control for Registration Fixed for the
relevant GVRP state machine on each port. A port may
not be added in this set if it is already a member of
the set of ports in dot1qVlanForbiddenEgressPorts. The
default value of this object is a string of zeros of
appropriate length, indicating not fixed."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 2 }
dot1qVlanForbiddenEgressPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The set of ports which are prohibited by management
from being included in the egress list for this VLAN.
Changes to this object that cause a port to be included
or excluded affect the per-port per-VLAN Registrar
control for Registration Forbidden for the relevant GVRP
state machine on each port. A port may not be added in
this set if it is already a member of the set of ports
in dot1qVlanStaticEgressPorts. The default value of
this object is a string of zeros of appropriate length,
excluding all ports from the forbidden set."
REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 3 }
dot1qVlanStaticUntaggedPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The set of ports which should transmit egress packets
for this VLAN as untagged. The default value of this
object for the default VLAN (dot1qVlanIndex = 1) is a string
of appropriate length including all ports. There is no
specified default for other VLANs. If a device agent cannot
support the set of ports being set then it will reject the
set operation with an error. An example might be if a
manager attempts to set more than one VLAN to be untagged
on egress where the device does not support this IEEE 802.1Q
option."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 4 }
dot1qVlanStaticRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the status of this entry."
::= { dot1qVlanStaticEntry 5 }
dot1qNextFreeLocalVlanIndex OBJECT-TYPE SYNTAX INTEGER (0|4096..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The next available value for dot1qVlanIndex of a local VLAN entry in dot1qVlanStaticTable. This will report values >=4096 if a new Local VLAN may be created or else the value 0 if this is not possible.
dot1qnextfreelocalvlanindex object-type integer（0 | 4096..2147483647）max-access読み取り専用ステータス現在の説明 "dot1qvlanstativableのローカルVLANエントリのDOT1QVLANINDEXの次の利用可能な値。これが不可能な場合は、作成される場合があります。
A row creation operation in this table for an entry with a local VlanIndex value may fail if the current value of this object is not used as the index. Even if the value read is used, there is no guarantee that it will still be the valid index when the create operation is attempted - another manager may have already got in during the intervening time interval. In this case, dot1qNextFreeLocalVlanIndex should be re-read and the creation re-tried with the new value.
このテーブルの行の作成操作は、このオブジェクトの現在の値がインデックスとして使用されていない場合、ローカルVlanIndex値を持つエントリのエントリの操作が故障する場合があります。値が使用されていても、作成操作が試みられた場合、それがまだ有効なインデックスであるという保証はありません。別のマネージャーは、介入時間間隔中にすでに入っています。この場合、DOT1QNEXTFREELOCOLVLANINDEXを再読し、作成を新しい値で再試行する必要があります。
This value will automatically change when the current value is
used to create a new row."
::= { dot1qVlan 4 }
-- -------------------------------------------------------------
-- The VLAN Port Configuration Table
-- -------------------------------------------------------------
dot1qPortVlanTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing per port control and status
information for VLAN configuration in the device."
::= { dot1qVlan 5 }
dot1qPortVlanEntry OBJECT-TYPE
SYNTAX Dot1qPortVlanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information controlling VLAN configuration for a port
on the device. This is indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry }
::= { dot1qPortVlanTable 1 }
Dot1qPortVlanEntry ::=
SEQUENCE {
dot1qPvid
VlanIndex,
dot1qPortAcceptableFrameTypes
INTEGER,
dot1qPortIngressFiltering
TruthValue,
dot1qPortGvrpStatus
EnabledStatus,
dot1qPortGvrpFailedRegistrations Counter32, dot1qPortGvrpLastPduOrigin MacAddress }
dot1qportgvrpfailedregistrations counter32、dot1qportgvrplastpduorigin macaddress}}
dot1qPvid OBJECT-TYPE
SYNTAX VlanIndex
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The PVID, the VLAN ID assigned to untagged frames or
Priority-Tagged frames received on this port."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.1"
DEFVAL { 1 }
::= { dot1qPortVlanEntry 1 }
dot1qPortAcceptableFrameTypes OBJECT-TYPE
SYNTAX INTEGER {
admitAll(1),
admitOnlyVlanTagged(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When this is admitOnlyVlanTagged(2) the device will
discard untagged frames or Priority-Tagged frames
received on this port. When admitAll(1), untagged
frames or Priority-Tagged frames received on this port
will be accepted and assigned to the PVID for this port.
This control does not affect VLAN independent BPDU
frames, such as GVRP and STP. It does affect VLAN
dependent BPDU frames, such as GMRP."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.3"
DEFVAL { admitAll }
::= { dot1qPortVlanEntry 2 }
dot1qPortIngressFiltering OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "When this is true(1) the device will discard incoming frames for VLANs which do not include this Port in its Member set. When false(2), the port will accept all incoming frames.
dot1qportingressfiltering object-type struthvalue max-access read-writeステータス現在の説明 "これが真の場合（1）デバイスは、メンバーセットにこのポートを含めないVLANの着信フレームを破棄します。すべての着信フレームを受け入れます。
This control does not affect VLAN independent BPDU
frames, such as GVRP and STP. It does affect VLAN
dependent BPDU frames, such as GMRP."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.4"
DEFVAL { false }
::= { dot1qPortVlanEntry 3 }
dot1qPortGvrpStatus OBJECT-TYPE
SYNTAX EnabledStatus
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The state of GVRP operation on this port. The value
enabled(1) indicates that GVRP is enabled on this port,
as long as dot1qGvrpStatus is also enabled for this
device. When disabled(2) but dot1qGvrpStatus is still
enabled for the device, GVRP is disabled on this port:
any GVRP packets received will be silently discarded and
no GVRP registrations will be propagated from other
ports. This object affects all GVRP Applicant and
Registrar state machines on this port. A transition
from disabled(2) to enabled(1) will cause a reset of all
GVRP state machines on this port."
DEFVAL { enabled }
::= { dot1qPortVlanEntry 4 }
dot1qPortGvrpFailedRegistrations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of failed GVRP registrations, for any
reason, on this port."
::= { dot1qPortVlanEntry 5 }
dot1qPortGvrpLastPduOrigin OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Source MAC Address of the last GVRP message
received on this port."
::= { dot1qPortVlanEntry 6 }
-- -------------------------------------------------------------
-- Per port VLAN Statistics Table
-- -------------------------------------------------------------
dot1qPortVlanStatisticsTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents which support only SNMPv1.
DOT1QPORTVLANSTATISTABLEオブジェクトタイプタイプのdot1qportvlanstatisticsentry max-access not-accessable accessable current current current current current "Table Per-port、vlan統計を含むテーブルが受け取ったテーブル。この透明なブリッジに関連付けられているポートのカウンター。これらのオブジェクトの適合性条項で定義されているように、最も重要なビットオブジェクトは大容量インターフェイスでのみ必要です。このメカニズムは、エージェントの64ビットカウンターを読み取る方法として提供されます。SNMPV1のみをサポートしています。
Note that the reporting of most-significant and least-
significant counter bits separately runs the risk of missing
an overflow of the lower bits in the interval between sampling.
The manager must be aware of this possibility, even within the
same varbindlist, when interpreting the results of a request or
asynchronous notification."
::= { dot1qVlan 6 }
dot1qPortVlanStatisticsEntry OBJECT-TYPE
SYNTAX Dot1qPortVlanStatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Traffic statistics for a VLAN on an interface."
INDEX { dot1dBasePort, dot1qVlanIndex }
::= { dot1qPortVlanStatisticsTable 1 }
Dot1qPortVlanStatisticsEntry ::=
SEQUENCE {
dot1qTpVlanPortInFrames Counter32, dot1qTpVlanPortOutFrames Counter32, dot1qTpVlanPortInDiscards Counter32, dot1qTpVlanPortInOverflowFrames Counter32, dot1qTpVlanPortOutOverflowFrames Counter32, dot1qTpVlanPortInOverflowDiscards Counter32 }
dot1qtpvlanportinframes counter32、dot1qtpvlanportoutframes counter32、dot1qtpvlanportindiscards counter32、dot1qtpvlanportoutobleflowframes counter32、dot1qtpvlanportinoverflowdisplowdisprowdispdispdisprams
dot1qTpVlanPortInFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of valid frames received by this port from
its segment which were classified as belonging to this
VLAN. Note that a frame received on this port is
counted by this object if and only if it is for a
protocol being processed by the local forwarding process
for this VLAN. This object includes received bridge
management frames classified as belonging to this VLAN
(e.g. GMRP, but not GVRP or STP)."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(a)"
::= { dot1qPortVlanStatisticsEntry 1 }
dot1qTpVlanPortOutFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of valid frames transmitted by this port to
its segment from the local forwarding process for this
VLAN. This includes bridge management frames originated
by this device which are classified as belonging to this
VLAN (e.g. GMRP, but not GVRP or STP)."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanStatisticsEntry 2 }
dot1qTpVlanPortInDiscards OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of valid frames received by this port from
its segment which were classified as belonging to this
VLAN which were discarded due to VLAN related reasons.
Specifically, the IEEE 802.1Q counters for Discard
Inbound and Discard on Ingress Filtering."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3"
::= { dot1qPortVlanStatisticsEntry 3 }
dot1qTpVlanPortInOverflowFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated
dot1qTpVlanPortInFrames counter has overflowed."
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1qPortVlanStatisticsEntry 4 }
dot1qTpVlanPortOutOverflowFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated
dot1qTpVlanPortOutFrames counter has overflowed."
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1qPortVlanStatisticsEntry 5 }
dot1qTpVlanPortInOverflowDiscards OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated
dot1qTpVlanPortInDiscards counter has overflowed."
REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1qPortVlanStatisticsEntry 6 }
dot1qPortVlanHCStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing per port, per VLAN statistics for
traffic on high capacity interfaces."
::= { dot1qVlan 7 }
dot1qPortVlanHCStatisticsEntry OBJECT-TYPE
SYNTAX Dot1qPortVlanHCStatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Traffic statistics for a VLAN on a high capacity
interface."
INDEX { dot1dBasePort, dot1qVlanIndex }
::= { dot1qPortVlanHCStatisticsTable 1 }
Dot1qPortVlanHCStatisticsEntry ::=
SEQUENCE {
dot1qTpVlanPortHCInFrames
Counter64,
dot1qTpVlanPortHCOutFrames
Counter64,
dot1qTpVlanPortHCInDiscards
Counter64
}
dot1qTpVlanPortHCInFrames OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of valid frames received by this port from
its segment which were classified as belonging to this
VLAN. Note that a frame received on this port is
counted by this object if and only if it is for a
protocol being processed by the local forwarding process
for this VLAN. This object includes received bridge
management frames classified as belonging to this VLAN
(e.g. GMRP, but not GVRP or STP)."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(a)"
::= { dot1qPortVlanHCStatisticsEntry 1 }
dot1qTpVlanPortHCOutFrames OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of valid frames transmitted by this port to
its segment from the local forwarding process for this
VLAN. This includes bridge management frames originated
by this device which are classified as belonging to this
VLAN (e.g. GMRP, but not GVRP or STP)."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanHCStatisticsEntry 2 }
dot1qTpVlanPortHCInDiscards OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of valid frames received by this port from
its segment which were classified as belonging to this
VLAN which were discarded due to VLAN related reasons.
Specifically, the IEEE 802.1Q counters for Discard
Inbound and Discard on Ingress Filtering."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3"
::= { dot1qPortVlanHCStatisticsEntry 3 }
-- -------------------------------------------------------------
-- The VLAN Learning Constraints Table
-- -------------------------------------------------------------
dot1qLearningConstraintsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qLearningConstraintsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing learning constraints for sets of
Shared and Independendent VLANs."
REFERENCE
"IEEE 802.1Q/D11 Section 12.10.3.1"
::= { dot1qVlan 8 }
dot1qLearningConstraintsEntry OBJECT-TYPE
SYNTAX Dot1qLearningConstraintsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A learning constraint defined for a VLAN."
INDEX { dot1qConstraintVlan, dot1qConstraintSet }
::= { dot1qLearningConstraintsTable 1 }
Dot1qLearningConstraintsEntry ::=
SEQUENCE {
dot1qConstraintVlan
VlanIndex,
dot1qConstraintSet
INTEGER,
dot1qConstraintType
INTEGER,
dot1qConstraintStatus
RowStatus
}
dot1qConstraintVlan OBJECT-TYPE
SYNTAX VlanIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index of the row in dot1qVlanCurrentTable for the
VLAN constrained by this entry."
::= { dot1qLearningConstraintsEntry 1 }
dot1qConstraintSet OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The identity of the constraint set to which
dot1qConstraintVlan belongs. These values may be chosen
by the management station."
::= { dot1qLearningConstraintsEntry 2 }
dot1qConstraintType OBJECT-TYPE
SYNTAX INTEGER {
independent(1),
shared(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of constraint this entry defines.
independent(1) - the VLAN, dot1qConstraintVlan,
uses an independent filtering database from all
other VLANs in the same set, defined by
dot1qConstraintSet.
shared(2) - the VLAN, dot1qConstraintVlan, shares
the same filtering database as all other VLANs
in the same set, defined by dot1qConstraintSet."
::= { dot1qLearningConstraintsEntry 3 }
dot1qConstraintStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this entry."
::= { dot1qLearningConstraintsEntry 4 }
dot1qConstraintSetDefault OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The identity of the constraint set to which a VLAN
belongs, if there is not an explicit entry for that VLAN
in dot1qLearningConstraintsTable."
::= { dot1qVlan 9 }
dot1qConstraintTypeDefault OBJECT-TYPE
SYNTAX INTEGER {
independent(1),
shared(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The type of constraint set to which a VLAN belongs, if
there is not an explicit entry for that VLAN in
dot1qLearningConstraintsTable. The types are as defined
for dot1qConstraintType."
::= { dot1qVlan 10 }
-- -------------------------------------------------------------
-- IEEE 802.1Q MIB - Conformance Information
-- -------------------------------------------------------------
qBridgeConformance OBJECT IDENTIFIER ::= { qBridgeMIB 2 }
qBridgeGroups OBJECT IDENTIFIER ::= { qBridgeConformance 1 }
qBridgeCompliances OBJECT IDENTIFIER
::= { qBridgeConformance 2 }
-- -------------------------------------------------------------
-- units of conformance
-- -------------------------------------------------------------
qBridgeBaseGroup OBJECT-GROUP
OBJECTS {
dot1qVlanVersionNumber,
dot1qMaxVlanId,
dot1qMaxSupportedVlans,
dot1qNumVlans,
dot1qGvrpStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing device level control
and status information for the Virtual LAN bridge
services."
::= { qBridgeGroups 1 }
qBridgeFdbUnicastGroup OBJECT-GROUP
OBJECTS {
dot1qFdbDynamicCount,
dot1qTpFdbPort,
dot1qTpFdbStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing information about all
unicast addresses, learnt dynamically or statically
configured by management, in each Filtering Database."
::= { qBridgeGroups 2 }
qBridgeFdbMulticastGroup OBJECT-GROUP
OBJECTS {
dot1qTpGroupEgressPorts,
dot1qTpGroupLearnt
}
STATUS current
DESCRIPTION
"A collection of objects providing information about all
multicast addresses, learnt dynamically or statically
configured by management, in each Filtering Database."
::= { qBridgeGroups 3 }
qBridgeServiceRequirementsGroup OBJECT-GROUP
OBJECTS {
dot1qForwardAllPorts,
dot1qForwardAllStaticPorts,
dot1qForwardAllForbiddenPorts,
dot1qForwardUnregisteredPorts,
dot1qForwardUnregisteredStaticPorts,
dot1qForwardUnregisteredForbiddenPorts
}
STATUS current
DESCRIPTION
"A collection of objects providing information about
service requirements, learnt dynamically or statically
configured by management, in each Filtering Database."
::= { qBridgeGroups 4 }
qBridgeFdbStaticGroup OBJECT-GROUP
OBJECTS {
dot1qStaticUnicastAllowedToGoTo,
dot1qStaticUnicastStatus,
dot1qStaticMulticastStaticEgressPorts,
dot1qStaticMulticastForbiddenEgressPorts,
dot1qStaticMulticastStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing information about
unicast and multicast addresses statically configured by
management, in each Filtering Database or VLAN."
::= { qBridgeGroups 5 }
qBridgeVlanGroup OBJECT-GROUP
OBJECTS {
dot1qVlanNumDeletes,
dot1qVlanFdbId,
dot1qVlanCurrentEgressPorts,
dot1qVlanCurrentUntaggedPorts,
dot1qVlanStatus,
dot1qVlanCreationTime
}
STATUS current
DESCRIPTION
"A collection of objects providing information about
all VLANs currently configured on this device."
::= { qBridgeGroups 6 }
qBridgeVlanStaticGroup OBJECT-GROUP
OBJECTS {
dot1qVlanStaticName,
dot1qVlanStaticEgressPorts,
dot1qVlanForbiddenEgressPorts,
dot1qVlanStaticUntaggedPorts,
dot1qVlanStaticRowStatus,
dot1qNextFreeLocalVlanIndex
}
STATUS current
DESCRIPTION
"A collection of objects providing information about
VLANs statically configured by management."
::= { qBridgeGroups 7 }
qBridgePortGroup OBJECT-GROUP
OBJECTS {
dot1qPvid,
dot1qPortAcceptableFrameTypes,
dot1qPortIngressFiltering,
dot1qPortGvrpStatus,
dot1qPortGvrpFailedRegistrations,
dot1qPortGvrpLastPduOrigin
}
STATUS current
DESCRIPTION
"A collection of objects providing port level VLAN
control and status information for all ports."
::= { qBridgeGroups 8 }
qBridgeVlanStatisticsGroup OBJECT-GROUP
OBJECTS {
dot1qTpVlanPortInFrames,
dot1qTpVlanPortOutFrames,
dot1qTpVlanPortInDiscards
}
STATUS current
DESCRIPTION
"A collection of objects providing per-port packet
statistics for all VLANs currently configured on this
device."
::= { qBridgeGroups 9 }
qBridgeVlanStatisticsOverflowGroup OBJECT-GROUP
OBJECTS {
dot1qTpVlanPortInOverflowFrames,
dot1qTpVlanPortOutOverflowFrames,
dot1qTpVlanPortInOverflowDiscards
}
STATUS current
DESCRIPTION
"A collection of objects providing overflow counters for
per-port packet statistics for all VLANs currently configured
on this device for high capacity interfaces, defined as those
that have the value of the corresponding instance of
ifSpeed greater than 650,000,000 bits/second."
::= { qBridgeGroups 10 }
qBridgeVlanHCStatisticsGroup OBJECT-GROUP
OBJECTS {
dot1qTpVlanPortHCInFrames,
dot1qTpVlanPortHCOutFrames,
dot1qTpVlanPortHCInDiscards
}
STATUS current
DESCRIPTION
"A collection of objects providing per-port packet
statistics for all VLANs currently configured on this
device for high capacity interfaces, defined as those
that have the value of the corresponding instance of
ifSpeed greater than 650,000,000 bits/second."
::= { qBridgeGroups 11 }
qBridgeLearningConstraintsGroup OBJECT-GROUP
OBJECTS {
dot1qConstraintType,
dot1qConstraintStatus
}
STATUS current
DESCRIPTION
"A collection of objects defining the Filtering Database
constraints all VLANs have with each other."
::= { qBridgeGroups 12 }
qBridgeLearningConstraintDefaultGroup OBJECT-GROUP
OBJECTS {
dot1qConstraintSetDefault,
dot1qConstraintTypeDefault
}
STATUS current
DESCRIPTION
"A collection of objects defining the default Filtering
Database constraints for VLANs which have no specific
constraints defined."
::= { qBridgeGroups 13 }
-- -------------------------------------------------------------
-- compliance statements
-- -------------------------------------------------------------
qBridgeCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for device support of Virtual LAN Bridge services."
QBRIDGEComplianceモジュールコンプライアンスステータス現在の説明「仮想LANブリッジサービスのデバイスサポートのコンプライアンスステートメント。」
MODULE
MANDATORY-GROUPS {
qBridgeBaseGroup,
qBridgeVlanGroup,
qBridgeVlanStaticGroup,
qBridgePortGroup
}
GROUP qBridgeFdbUnicastGroup DESCRIPTION "This group is mandatory for bridges that implement 802.1Q transparent bridging."
グループQBridgeFDBunicastGroup説明「このグループは、802.1Qの透明ブリッジングを実装するブリッジに必須です。」
GROUP qBridgeFdbMulticastGroup DESCRIPTION "This group is mandatory for bridges that implement 802.1Q transparent bridging."
グループQBRIDGEFDBMULTICASTGROUP説明「このグループは、802.1Qの透明ブリッジングを実装するブリッジに必須です。」
GROUP qBridgeServiceRequirementsGroup DESCRIPTION "This group is mandatory for bridges that implement extended filtering services. All objects must be read-write if extended-filtering services are enabled."
グループQBRIDGESERVICEREQUIREMENTSGROUP説明「このグループは、拡張フィルタリングサービスを実装するブリッジに義務付けられています。拡張フィルタリングサービスが有効になっている場合、すべてのオブジェクトは読み取りされている必要があります。」
GROUP qBridgeFdbStaticGroup DESCRIPTION "This group is optional."
グループQBRIDGEFDBSTATICGROUP説明「このグループはオプションです。」
GROUP qBridgeVlanStatisticsGroup DESCRIPTION "This group is optional as there may be significant implementation cost associated with its support."
グループqbridgevlanstatisticsgroup説明「このグループは、そのサポートに関連する重要な実装コストがある可能性があるため、オプションです。」
GROUP qBridgeVlanStatisticsOverflowGroup DESCRIPTION "This group is optional as there may be significant implementation cost associated with its support. It is most relevant for high capacity interfaces where the SNMP agent supports only SNMPv1."
グループQBRIDGEVLANSTATISTICSOVERFLOWGROUP説明「このグループは、そのサポートに関連する重要な実装コストがある可能性があるため、オプションです。SNMPエージェントがSNMPV1のみをサポートする大容量インターフェイスに最も関連しています。」
GROUP qBridgeVlanHCStatisticsGroup DESCRIPTION "This group is optional as there may be significant implementation cost associated with its support. It is most relevant for high capacity interfaces."
グループQBRIDGEVLANHCSTATISTICSGROUP説明「このグループは、そのサポートに関連する重要な実装コストがある可能性があるため、オプションです。大容量インターフェイスに最も関連しています。」
GROUP qBridgeLearningConstraintsGroup DESCRIPTION "This group is mandatory for devices implementing both Independent VLAN Learning (IVL) and Shared VLAN Learning (SVL) modes of operation of the filtering database, as defined by IEEE 802.1Q."
グループQBRIDGELEARNINGConstraintsGroupの説明「このグループは、IEEE 802.1Qで定義されているように、独立したVLAN学習（IVL）と共有VLAN学習（SVL）動作モードの両方のフィルタリングデータベースの動作モードを実装するデバイスに必須です。」
GROUP qBridgeLearningConstraintDefaultGroup DESCRIPTION "This group is mandatory for devices implementing both Independent VLAN Learning (IVL) and Shared VLAN Learning (SVL) modes of operation of the filtering database, as defined by IEEE 802.1Q."
グループQBRIDGELEARNINGConstraintDefaultGroupの説明「このグループは、IEEE 802.1Q。
OBJECT dot1qPortAcceptableFrameTypes MIN-ACCESS read-only DESCRIPTION "Write access is not required as this is an optional capability in IEEE 802.1Q."
オブジェクトdot1qportacceptableframetypes min-access読み取り専用説明
OBJECT dot1qPortIngressFiltering MIN-ACCESS read-only DESCRIPTION "Write access is not required as this is an optional capability in IEEE 802.1Q."
オブジェクトdot1qportingressfiltering min-access読み取り専用説明「書き込みアクセスは必要ありません。これはIEEE 802.1q。のオプションの機能であるため」
OBJECT dot1qConstraintSetDefault MIN-ACCESS read-only DESCRIPTION "Write access is not required as this is an optional capability in IEEE 802.1Q."
オブジェクトdot1qcconstraintsetdefault min-access read-only description "これはIEEE 802.1q。のオプションの機能であるため、書き込みアクセスは不要です。」
OBJECT dot1qConstraintTypeDefault MIN-ACCESS read-only DESCRIPTION "Write access is not required as this is an optional capability in IEEE 802.1Q."
オブジェクトdot1qconstrainttypedefault min-access read-only description "これはIEEE 802.1qのオプションの機能であるため、書き込みアクセスは不要です。」
::= { qBridgeCompliances 1 }
END
終わり
This document expands upon previous work which resulted in the original bridge MIB [BRIDGEMIB].
このドキュメントは、以前の作業を拡張し、元のブリッジMIB [Bridgemib]をもたらしました。
Much of the groundwork for this document was performed by the IEEE 802.1 working group during the definition of the IEEE 802.1D updates [802.1D] and IEEE 802.1Q [802.1Q].
このドキュメントの基礎の多くは、IEEE 802.1dアップデート[802.1d]およびIEEE 802.1q [802.1q]の定義中にIEEE 802.1ワーキンググループによって実行されました。
The authors wish to thank the members of the Bridge Working Group and David Harrington in particular for their many comments and suggestions which improved this effort.
著者は、この努力を改善した多くのコメントや提案について、特にブリッジワーキンググループのメンバーとデビッドハリントンに感謝したいと考えています。
There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
このMIBには、読み取りワイトおよび/またはread-Createの最大アクセス句がある管理オブジェクトがいくつかあります。このようなオブジェクトは、一部のネットワーク環境で敏感または脆弱と見なされる場合があります。適切な保護なしの非セキュア環境でのセット操作のサポートは、ネットワーク操作に悪影響を与える可能性があります。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB.
SNMPV1自体は安全な環境ではありません。ネットワーク自体が（たとえばIPSECを使用して）安全である場合でも、それでもセキュアネットワーク上の誰がアクセス/セット/セット（読み取り/変更/作成/削除/削除）を制御することはできません。ミブ。
It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model [USM] and the View-based Access Control Model [VACM] is recommended.
実装者は、SNMPV3フレームワークで提供されるセキュリティ機能を考慮することをお勧めします。具体的には、ユーザーベースのセキュリティモデル[USM]とビューベースのアクセス制御モデル[VACM]の使用が推奨されます。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
その場合、このMIBのインスタンスへのアクセスを提供するSNMPエンティティが、実際に取得または設定する正当な権利を持つプリンシパル（ユーザー）にのみオブジェクトにアクセスできるように適切に構成されていることを保証するのは、顧客/ユーザーの責任です（変更を変更するプリンシパル（ユーザー）（変更）/作成/削除）それら。
[ARCH] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[Arch] Harrington、D.、Presuhn、R。およびB. Wijnen、「SNMP管理フレームワークを説明するためのアーキテクチャ」、RFC 2571、1999年4月。
[V1PROTO] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[V1Proto] Case、J.、Fedor、M.、Schoffstall、M.およびJ. Davin、「Simple Network Management Protocol」、STD 15、RFC 1157、1990年5月。
[V1SMI] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[V1SMI] Rose、M。およびK. McCloghrie、「TCP/IPベースのインターネットの管理情報の構造と識別」、STD 16、RFC 1155、1990年5月。
[V1CONCISE] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[V1Concise] Rose、M。and K. McCloghrie、「Concise MIB Definitions」、STD 16、RFC 1212、1991年3月。
[V1TRAPS] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[V1Traps] Rose、M。、「SNMPで使用するためのトラップを定義するための条約」、RFC 1215、1991年3月。
[V2SMI] 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.
[V2SMI] McCloghrie、K.、Perkins、D.、Schoenwaelder、J.、Case、J.、Rose、M。and S. Waldbusser、「管理情報の構造バージョン2（SMIV2）、STD 58、RFC 2578、1999年4月。
[V2TC] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[V2TC] McCloghrie、K.、Perkins、D.、Schoenwaelder、J.、Case、J.、Rose、M。、およびS. Waldbusser、「SMIV2のテキストコンベンション」、STD 58、RFC 2579、1999年4月。
[V2CONFORM] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[V2Conform] McCloghrie、K.、Perkins、D.、Schoenwaelder、J.、Case、J.、Rose、M。、およびS. Waldbusser、「SMIV2の適合ステートメント」、STD 58、RFC 2580、1999年4月。
[V2COMMUNITY] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[V2Community] Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「コミュニティベースのSNMPV2の紹介」、RFC 1901、1996年1月。
[V2TRANS] 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.
[V2Trans] Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「シンプルネットワーク管理プロトコル（SNMPV2）のバージョン2の輸送マッピング」、RFC 1906、1996年1月。
[V2PROTO] 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.
[V2Proto] Case、J.、McCloghrie、K.、Rose、M。、およびS. Waldbusser、「単純なネットワーク管理プロトコル（SNMPV2）のバージョン2のプロトコル操作」、RFC 1905、1996年1月。
[V3INTRO] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[V3Intro] Case、J.、Mundy、R.、Partain、D。、およびB. Stewart、「インターネット標準ネットワーク管理フレームワークのバージョン3の紹介」、RFC 2570、1999年4月。
[V3MPC] Case, J., Harrington D., Presuhn, R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[V3MPC] Case、J.、J.、Harrington D.、Presuhn、R。、およびB. Wijnen、「Simple Network Management Protocol（SNMP）のメッセージ処理とディスパッチ」、RFC 2572、1999年4月。
[V3USM] Blumenthal, U. and B. Wijnen, "The User-Based Security Model (USM) for Version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[V3USM] Blumenthal、U.およびB. Wijnen、「シンプルネットワーク管理プロトコル（SNMPV3）のバージョン3のユーザーベースのセキュリティモデル（USM）」、RFC 2574、1999年4月。
[V3APPS] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, April 1999.
[V3Apps] Levi、D.、Meyer、P。and B. Stewart、「SNMP Applications」、RFC 2573、1999年4月。
[V3VACM] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[V3VACM] Wijnen、B.、Presuhn、R。、およびK. McCloghrie、「Simple Network Management Protocol（SNMP）のビューベースのアクセス制御モデル」、RFC 2575、1999年4月。
[ASN1] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International Standard 8824, December 1987.
[ASN1]情報処理システム - オープンシステムの相互接続 - 抽象的な構文表記の仕様（ASN.1）、国際標準化機関、国際標準8824、1987年12月。
[ASN1BER] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization, International Standard 8825, December 1987.
[ASN1ber]情報処理システム - オープンシステムの相互接続 - 抽象表記1（ASN.1）、国際標準化機関、国際標準8825、1987年12月の基本エンコードルールの指定。
[802.1D-ORIG] ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges".
[802.1D-Orig] ISO/IEC 10038、ANSI/IEEE STD 802.1D-1993「Mac Bridges」。
[802.1D] "Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 3: Media Access Control (MAC) Bridges: Revision. This is a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k-1992. It incorporates P802.11c, P802.1p and P802.12e." ISO/IEC 15802-3: 1998.
[802.1d]「情報技術 - システム間の通信と情報交換 - ローカルおよびメトロポリタンエリアネットワーク - 共通仕様 - パート3：メディアアクセス制御（MAC）ブリッジ：改訂。これはISO/IEC 10038：1993、802.11の改訂です。J-1992および802.6k-1992。p802.11c、p802.1p、p802.12eが組み込まれています。ISO/IEC 15802-3：1998。
[802.1Q] ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks", 1998.
[802.1Q] ANSI/IEEE Standard 802.1Q、「ローカルおよびメトロポリタンエリアネットワークのIEEE標準：仮想ブリッジ付きローカルエリアネットワーク」、1998。
[BRIDGEMIB] Decker, E., Langille, P., Rijsinghani, A. and K. McCloghrie, "Definitions of Managed Objects for Bridges", RFC 1493, July 1993.
[Bridgemib] Decker、E.、Langille、P.、Rijsinghani、A。and K. McCloghrie、「ブリッジの管理オブジェクトの定義」、RFC 1493、1993年7月。
[INTERFACEMIB] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2233, November 1997.
[Interfacemib] McCloghrie、K。およびF. Kastenholz、「SMIV2を使用したインターフェースグループMIB」、RFC 2233、1997年11月。
[SRBRIDGEMIB] Decker, E., McCloghrie, K., Langille, P. and A. Rijsinghani, "Definitions of Managed Objects for Source Routing Bridges", RFC 1525, September 1993.
[Srbridgemib] Decker、E.、McCloghrie、K.、Langille、P。and A. Rijsinghani、「ソースルーティングブリッジの管理されたオブジェクトの定義」、RFC 1525、1993年9月。
[MIB2] McCloghrie K. and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets", STD 17, RFC 1213, March 1991.
[MIB2] McCloghrie K.およびM. Rose、編集者、「TCP/IPベースのインターネットのネットワーク管理のための管理情報ベース」、STD 17、RFC 1213、1991年3月。
Les Bell 3Com Europe Limited 3Com Centre, Boundary Way Hemel Hempstead Herts. HP2 7YU UK
Les Bell 3com Europe Limited 3Com Center、Boundary Way Hemel Hempstead Herts。HP2 7YU UK
Phone: +44 1442 438025
EMail: Les_Bell@3Com.com
Andrew Smith Extreme Networks 3585 Monroe St. Santa Clara, CA 95051 USA
アンドリュースミスエクストリームネットワーク3585モンローセントサンタクララ、カリフォルニア95051 USA
Phone: +1 408 579 2821
EMail: andrew@extremenetworks.com
Paul Langille Newbridge Networks 5 Corporate Drive Andover, MA 01810 USA
Paul Langille Newbridge Networks 5 Corporate Drive Andover、MA 01810 USA
Phone: +1 978 691 4665
EMail: langille@newbridge.com
Anil Rijhsinghani Cabletron Systems 50 Minuteman Road Andover, MA 01810 USA
Anil Rijhsinghani Cabletron Systems 50 Minuteman Road Andover、MA 01810 USA
Phone: +1 978 684 1295
EMail: anil@cabletron.com
Keith McCloghrie cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA
Keith McCloghrie Cisco Systems、Inc。170 West Tasman Drive San Jose、CA 95134-1706 USA
Phone: +1 408 526 5260
EMail: kzm@cisco.com
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
IETFは、知的財産またはその他の権利の有効性または範囲に関して、この文書に記載されているテクノロジーの実装または使用に関連すると主張される可能性のある他の権利、またはそのような権利に基づくライセンスがどの程度であるかについての程度に関連する可能性があるという立場はありません。利用可能;また、そのような権利を特定するために努力したことも表明していません。標準トラックおよび標準関連のドキュメントの権利に関するIETFの手順に関する情報は、BCP-11に記載されています。出版のために利用可能にされた権利の請求のコピーと、利用可能になるライセンスの保証、またはこの仕様の実装者またはユーザーによるそのような独自の権利の使用のための一般的なライセンスまたは許可を取得しようとする試みの結果を得ることができますIETF事務局から。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETFは、関心のある当事者に、著作権、特許、または特許出願、またはこの基準を実践するために必要な技術をカバーする可能性のあるその他の独自の権利を注意深く招待します。情報をIETFエグゼクティブディレクターに宛ててください。
Copyright (C) The Internet Society (1999). All Rights Reserved.
Copyright（c）The Internet Society（1999）。無断転載を禁じます。
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エディター機能の資金は現在、インターネット協会によって提供されています。