draft-ietf-bridge-bridgemib-05.txt   rfc2674.txt 
Internet Draft E.L. Bell Network Working Group E. Bell
Expires September 1999 3Com Corp. Request for Comments: 2674 3Com Corp.
draft-ietf-bridge-bridgemib-05.txt A. Smith Category: Standards Track A. Smith
Extreme Networks Extreme Networks
P. Langille P. Langille
Newbridge Networks Newbridge Networks
A. Rijhsinghani A. Rijhsinghani
Cabletron Systems Cabletron Systems
K. McCloghrie K. McCloghrie
cisco Systems cisco Systems
March 1999 August 1999
Definitions of Managed Objects for Bridges with Traffic Definitions of Managed Objects for Bridges with Traffic
Classes, Multicast Filtering and Virtual LAN Extensions Classes, Multicast Filtering and Virtual LAN Extensions
Status of this Memo Status of this Memo
This document is an Internet Draft and is in full conformance with all This document specifies an Internet standards track protocol for the
provisions of Section 10 of RFC2026. Internet Drafts are working Internet community, and requests discussion and suggestions for
documents of the Internet Engineering Task Force (IETF), its Areas, and improvements. Please refer to the current edition of the "Internet
its Working Groups. Note that other groups may also distribute working Official Protocol Standards" (STD 1) for the standardization state
documents as Internet Drafts. and status of this protocol. Distribution of this memo is unlimited.
Internet Drafts are draft documents valid for a maximum of six months. Copyright Notice
Internet Drafts may be updated, replaced, or obsoleted by other
documents at any time. It is not appropriate to use Internet Drafts as
reference material or to cite them other than as a "working draft" or
"work in progress."
The list of current Internet-Drafts can be accessed at Copyright (C) The Internet Society (1999). All Rights Reserved.
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Abstract
http://www.ietf.org/shadow.html.
This document is a product of the IETF's Bridge MIB Working Group. This memo defines a portion of the Management Information Base (MIB)
Copyright (C) The Internet Society (1999). All Rights Reserved. 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.
Abstract 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].
This memo defines a portion of the Management Information Base (MIB) for This memo supplements RFC 1493 [BRIDGEMIB] and (to a lesser extent)
use with network management protocols in TCP/IP based internets. In RFC 1525 [SBRIDGEMIB].
particular it defines objects for managing MAC bridges based on the IEEE
802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN (VLAN)
standards for bridging between Local Area Network (LAN) segments.
Provisions are made for support of transparent bridging. Provisions are Table of Contents
also made so that these objects apply to bridges connected by
subnetworks other than LAN segments. This memo also includes several 1 The SNMP Management Framework ................................... 3
MIB modules in a manner that is compliant to the SNMPv2 SMI [5]. 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
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in an Architecture for
Describing SNMP Management Frameworks [ARCH].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in STD
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second 16, RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC 1215
version, called SMIv2, is described in RFC 1902 [5], RFC 1903 [V1TRAPS]. The second version, called SMIv2, is described in STD
[6] and RFC 1904 [7]. 58, RFC 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58, RFC
2580 [V2CONFORM].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [V1PROTO]. A second version of the
protocol, which is not an Internet standards track protocol, is SNMP message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. protocol, is called SNMPv2c and described in RFC 1901
The third version of the message protocol is called SNMPv3 and [V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. message protocol is called SNMPv3 and described in RFC 1906
[V2TRANS], Message Processing and Dispatching [V3MPC] and User-
based Security Model [V3USM].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations described in STD 15, RFC 1157 [V1PROTO]. A second set of
and associated PDU formats is described in RFC 1905 [13]. protocol operations and associated PDU formats is described in
RFC 1905 [V2PROTO].
o A set of fundamental applications described in RFC 2273 [14] and o A set of fundamental applications described in SNMPv3
the view-based access control mechanism described in RFC 2275 Applications [V3APPS] and the view-based access control mechanism
[15]. described in View-based Access Control Model [V3VACM].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. Objects in the MIB are defined the Management Information Base or MIB. Objects in the MIB are
using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A
conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Overview 2. Overview
A common device present in many networks is the Bridge. This device is A common device present in many networks is the Bridge. This device
used to connect Local Area Network segments below the network layer. is used to connect Local Area Network segments below the network
These devices are often known as 'layer 2 switches'. layer. These devices are often known as 'layer 2 switches'.
There are two major modes defined for this bridging; transparent and There are two major modes defined for this bridging: Source-Route and
source route. The transparent method of bridging is defined by IEEE transparent. Source-Route bridging is described by IEEE 802.5
802.1D-1998 [19]. Managed objects for source route bridges are defined [802.5]. and is not discussed further in this document.
in [23].
IEEE 802.1D is augmented by IEEE 802.1Q-1998 [20] to provide support for The transparent method of bridging is defined by IEEE 802.1D-1998
'virtual bridged LANs' where a single bridged physical LAN network may [802.1D] which is an update to the original IEEE 802.1D specification
be used to support multiple logical bridged LANs, each of which offers a [802.1D-ORIG]. Managed objects for that original specification of
service approximately the same as that defined by 802.1D. Such virtual transparent bridging were defined in RFC 1493 [BRIDGEMIB].
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.
This memo defines those objects needed for the management of a bridging The original IEEE 802.1D is augmented by IEEE 802.1Q-1998 [802.1Q] to
entity operating in the transparent mode, as well as some objects provide support for 'virtual bridged LANs' where a single bridged
applicable to all types of bridges. Managed objects for Source-Routing physical LAN network may be used to support multiple logical bridged
are defined in [23]. 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.
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].
2.1. Scope 2.1. Scope
This MIB includes a comprehensive set of managed objects which attempts This MIB includes a comprehensive set of managed objects which
to match the set defined in IEEE 802.1D and IEEE 802.1Q. However, to be attempts to match the set defined in IEEE 802.1D and IEEE 802.1Q.
consistent with the spirit of the SNMP Framework, a subjective judgement However, to be consistent with the spirit of the SNMP Framework, a
was made to omit the objects from those standards most 'costly' to subjective judgement was made to omit the objects from those
implement in an agent and least 'essential' for fault and configuration standards most 'costly' to implement in an agent and least
management. The omissions are described in section 3 below. 'essential' for fault and configuration management. The omissions
are described in section 3 below.
Historical note: Historical note:
RFC 1493 used the following principles for determining inclusion of an The original bridge MIB [BRIDGEMIB] used the following principles for
object in the BRIDGE-MIB module: determining inclusion of an object in the BRIDGE-MIB module:
(1) Start with a small set of essential objects and add only as (1) Start with a small set of essential objects and add only as
further objects are needed. further objects are needed.
(2) Require objects be essential for either fault or configuration (2) Require objects be essential for either fault or configuration
management. management.
(3) Consider evidence of current use and/or utility. (3) Consider evidence of current use and/or utility.
(4) Limit the total of objects. (4) Limit the total of objects.
(5) Exclude objects which are simply derivable from others in this or (5) Exclude objects which are simply derivable from others in
other MIBs. this or other MIBs.
(6) Avoid causing critical sections to be heavily instrumented. The (6) Avoid causing critical sections to be heavily instrumented.
guideline that was followed is one counter per critical section The guideline that was followed is one counter per critical
per layer. section per layer.
3. Structure of MIBs 3. Structure of MIBs
This document defines additional objects, on top of those existing in This document defines additional objects, on top of those existing in
the base BRIDGE-MIB module defined in RFC1493: that MIB module is the original BRIDGE-MIB module defined in [BRIDGEMIB]: that MIB
maintained unchanged for backwards compatibility. Section 3.4.3 of the module is to be maintained unchanged for backwards compatibility.
present document contains some recommendations regarding usage of Section 3.4.3 of the present document contains some recommendations
objects in RFC1493 by devices implementing the enhancements defined regarding usage of objects in the original bridge MIB by devices
here. implementing the enhancements defined here.
Two MIB modules are defined here: Two MIB modules are defined here:
(1) Managed objects for an extended bridge MIB module P-BRIDGE-MIB (1) Managed objects for an extended bridge MIB module P-BRIDGE-MIB
for the traffic class and multicast filtering enhancements for the traffic class and multicast filtering enhancements
defined by IEEE 802.1D-1998. defined by IEEE 802.1D-1998 [802.1D].
(2) Managed objects for a virtual bridge MIB module Q-BRIDGE-MIB for (2) Managed objects for a virtual bridge MIB module Q-BRIDGE-MIB
the Virtual LAN bridging enhancements defined by IEEE for the Virtual LAN bridging enhancements defined by IEEE
802.1Q-1998. 802.1Q-1998 [802.1Q].
3.1. Structure of Extended Bridge MIB module 3.1. Structure of Extended Bridge MIB module
Objects in this MIB are arranged into groups. Each group is organized Objects in this MIB are arranged into groups. Each group is
as a set of related objects. The overall structure and assignment of organized as a set of related objects. The overall structure and
objects to their groups is shown below. assignment of objects to their groups is shown below.
3.1.1. Relationship to IEEE 802.1D-1998 Manageable Objects 3.1.1. Relationship to IEEE 802.1D-1998 Manageable Objects
This section contains a cross-reference to the objects defined in IEEE This section contains a cross-reference to the objects defined in
802.1D-1998 [19]. It also details those objects that are not considered IEEE 802.1D-1998 [802.1D]. It also details those objects that are
necessary in this MIB module. not considered necessary in this MIB module.
Some objects defined by [19] have been included in the virtual bridge Some objects defined by IEEE 802.1D-1998 have been included in the
MIB module rather than this one: entries in dot1qTpGroupTable, virtual bridge MIB module rather than this one: entries in
dot1qForwardAllTable and dot1qForwardUnregisteredTable are required for dot1qTpGroupTable, dot1qForwardAllTable and
virtual bridged LANs with additional indexing (e.g. per-VLAN, per-FDB) dot1qForwardUnregisteredTable are required for virtual bridged LANs
and so are not defined here. Instead, devices which do not implement with additional indexing (e.g. per-VLAN, per-FDB) and so are not
virtual bridged LANs, should implement these tables with a fixed value defined here. Instead, devices which do not implement virtual
for dot1qFdbId (the value 1 is recommended) or dot1qVlanIndex (the value bridged LANs but do implement the Extended Forwarding Services
1 is recommended). Devices which support Extended Filtering Services defined by IEEE 802.1D (i.e. dynamic learning of multicast group
(dynamic learning of Multicast Group Addresses and Group Service addresses and group service requirements in the filtering database)
Requirements in the Filtering Database) should support should implement these tables with a fixed value for dot1qFdbId (the
dot1qTpGroupTable, dot1qForwardAllTable and value 1 is recommended) or dot1qVlanIndex (the value 1 is
dot1qForwardUnregisteredTable. recommended). Devices which support Extended Filtering Services
should support dot1qTpGroupTable, dot1qForwardAllTable and
dot1qForwardUnregisteredTable.
Extended Bridge MIB Name IEEE 802.1D Name Extended Bridge MIB Name IEEE 802.1D-1998 Name
dot1dExtended Bridge dot1dExtBase Bridge
dot1dExtBase dot1dDeviceCapabilities
dot1dDeviceCapabilities dot1dExtendedFilteringServices
dot1dExtendedFilteringServices dot1dTrafficClasses
dot1dTrafficClasses dot1dTrafficClassesEnabled
dot1dTrafficClassesEnabled dot1dGmrpStatus .ApplicantAdministrativeControl
dot1dGmrpStatus .ApplicantAdministrativeControl dot1dPriority
dot1dPriority dot1dPortPriorityTable
dot1dPortPriorityTable dot1dPortDefaultUserPriority .UserPriority
dot1dPortDefaultUserPriority .UserPriority dot1dPortNumTrafficClasses
dot1dPortNumTrafficClasses dot1dUserPriorityRegenTable .UserPriorityRegenerationTable
dot1dUserPriorityRegenTable .UserPriorityRegenerationTable dot1dUserPriority
dot1dUserPriority dot1dRegenUserPriority
dot1dRegenUserPriority dot1dTrafficClassTable .TrafficClassTable
dot1dTrafficClassTable .TrafficClassTable dot1dTrafficClassPriority
dot1dTrafficClassPriority dot1dTrafficClass
dot1dTrafficClass dot1dPortOutboundAccessPriorityTable
dot1dPortOutboundAccessPriorityTable .OutboundAccessPriorityTable
.OutboundAccessPriorityTable dot1dPortOutboundAccessPriority
dot1dPortOutboundAccessPriority dot1dGarp
dot1dGarp dot1dPortGarpTable
dot1dPortGarpTable dot1dPortGarpJoinTime .JoinTime
dot1dPortGarpJoinTime .JoinTime dot1dPortGarpLeaveTime .LeaveTime
dot1dPortGarpLeaveTime .LeaveTime dot1dPortGarpLeaveAllTime .LeaveAllTime
dot1dPortGarpLeaveAllTime .LeaveAllTime dot1dGmrp
dot1dGmrp dot1dPortGmrpTable
dot1dPortGmrpTable dot1dPortGmrpStatus .ApplicantAdministrativeControl
dot1dPortGmrpStatus .ApplicantAdministrativeControl dot1dPortGmrpFailedRegistrations .FailedRegistrations
dot1dPortGmrpFailedRegistrations dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU
.FailedRegistrations dot1dTp
dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU dot1dTpHCPortTable
dot1dTpGroup dot1dTpHCPortInFrames .BridgePort.FramesReceived
dot1dTpHCPortTable dot1dTpHCPortOutFrames .ForwardOutBound
dot1dTpHCPortInFrames .BridgePort.FramesReceived dot1dTpHCPortInDiscards .DiscardInbound
dot1dTpHCPortOutFrames .ForwardOutBound dot1dTpPortOverflowTable
dot1dTpHCPortInDiscards .DiscardInbound dot1dTpPortInOverflowFrames .BridgePort.FramesReceived
dot1dTpPortOverflowTable dot1dTpPortOutOverflowFrames .ForwardOutBound
dot1dTpPortInOverflowFrames .BridgePort.FramesReceived dot1dTpPortInOverflowDiscards .DiscardInbound
dot1dTpPortOutOverflowFrames .ForwardOutBound
dot1dTpPortInOverflowDiscards .DiscardInbound
The following IEEE 802.1D management objects have not been included in The following IEEE 802.1D-1998 management objects have not been
the Bridge MIB for the indicated reasons. included in the Bridge MIB for the indicated reasons.
IEEE 802.1D Object Disposition IEEE 802.1D-1998 Object Disposition
Bridge.StateValue not considered useful Bridge.StateValue not considered useful
Bridge.ApplicantAdministrativeControl Bridge.ApplicantAdministrativeControl
not provided per-attribute not provided per-attribute
(e.g. per-VLAN, per-Group). (e.g. per-VLAN, per-Group).
Only per-{device,port,application} Only per-{device,port,application}
control is provided in this MIB. control is provided in this MIB.
3.1.2. Relationship to IEEE 802.1Q Manageable Objects 3.1.2. Relationship to IEEE 802.1Q Manageable Objects
This section contains a cross-reference to the objects defined in IEEE This section contains section number cross-references to manageable
802.1Q-1998 [20]. These objects have been included in this MIB as they objects defined in IEEE 802.1Q-1998 [802.1Q]. These objects have
provide a natural fit with the 802.1D objects they are located with. been included in this MIB as they provide a natural fit with the IEEE
802.1D objects with which they are co-located.
Extended Bridge MIB Name IEEE 802.1Q Name Extended Bridge MIB Name IEEE 802.1Q-1998 Section and Name
dot1dExtended Bridge dot1dExtBase Bridge
dot1dExtBase dot1dDeviceCapabilities
dot1dDeviceCapabilities dot1qStaticEntryIndividualPort 5.2 implementation options
dot1qStaticEntryIndividualPort 5.2 implementation options dot1qIVLCapable
dot1qIVLCapable dot1qSVLCapable
dot1qSVLCapable dot1qHybridCapable
dot1qHybridCapable dot1qConfigurablePvidTagging 12.10.1.1 read bridge vlan
dot1qConfigurablePvidTagging 12.10.1.1 read bridge vlan config
config dot1dLocalVlanCapable
dot1dPortCapabilitiesTable dot1dPortCapabilitiesTable
dot1dPortCapabilities dot1dPortCapabilities
dot1qDot1qTagging 5.2 implementation options dot1qDot1qTagging 5.2 implementation options
dot1qConfigurableAcceptableFrameTypes dot1qConfigurableAcceptableFrameTypes
5.2 implementation options 5.2 implementation options
dot1qIngressFiltering 5.2 implementation options dot1qIngressFiltering 5.2 implementation options
3.1.3. The dot1dExtBase Group 3.1.3. The dot1dExtBase Group
This group contains the objects which are applicable to all bridges This group contains the objects which are applicable to all bridges
implementing the traffic class and multicast filtering features of implementing the traffic class and multicast filtering features of
802.1D. It includes per-device configuration of GARP and GMRP IEEE 802.1D-1998 [802.1D]. It includes per-device configuration of
protocols. This group will be implemented by all devices which GARP and GMRP protocols. This group will be implemented by all
implement the extensions defined in 802.1D-1998. devices which implement the extensions defined in 802.1D-1998.
3.1.4. The dot1dPriority Group 3.1.4. The dot1dPriority Group
This group contains the objects for configuring and reporting status of This group contains the objects for configuring and reporting status
priority-based queuing mechanisms in a bridge. This includes per- port of priority-based queuing mechanisms in a bridge. This includes per-
user_priority treatment, mapping of user_priority in frames into port user_priority treatment, mapping of user_priority in frames into
internal traffic classes and outbound user_priority and access_priority. internal traffic classes and outbound user_priority and
access_priority.
3.1.5. The dot1dGarp Group 3.1.5. The dot1dGarp Group
This group contains the objects for configuring and reporting on This group contains the objects for configuring and reporting on
operation of the Generic Attribute Registration Protocol (GARP). operation of the Generic Attribute Registration Protocol (GARP).
3.1.6. The dot1dGmrp Group 3.1.6. The dot1dGmrp Group
This group contains the objects for configuring and reporting on This group contains the objects for configuring and reporting on
operation of the GARP Multicast Registration Protocol (GMRP). operation of the GARP Multicast Registration Protocol (GMRP).
3.1.7. The dot1dHCPortTable 3.1.7. The dot1dTpHCPortTable
This table extends the dot1dTp group from RFC1493 and contains the This table extends the dot1dTp group from the original bridge MIB
objects for reporting port bridging statistics for high-capacity network [BRIDGEMIB] and contains the objects for reporting port bridging
interfaces. statistics for high capacity network interfaces.
3.1.8. The dot1dTpPortOverflowTable
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.
3.2. Structure of Virtual Bridge MIB module 3.2. Structure of Virtual Bridge MIB module
Objects in this MIB are arranged into groups. Each group is organized Objects in this MIB are arranged into groups. Each group is
as a set of related objects. The overall structure and assignment of organized as a set of related objects. The overall structure and
objects to their groups is shown below. Some of the original objects assignment of objects to their groups is shown below. Some
from RFC1493 need to be indexed differently when extended in a VLAN manageable objects defined in the original bridge MIB [BRIDGEMIB]
environment so some objects in that module effectively duplicate new need to be indexed differently when they are used in a VLAN bridging
objects defined here: this is necessary for backwards compatibility. environment: these objects are, therefore, effectively duplicated by
new objects with different indexing which are defined in the Virtual
Bridge MIB.
3.2.1. Relationship to IEEE 802.1Q Manageable Objects 3.2.1. Relationship to IEEE 802.1Q Manageable Objects
This section contains a cross-reference to the objects defined in [20]. This section contains section-number cross-references to manageable
It also details those objects that are not considered necessary in this objects defined in clause 12 of IEEE 802.1Q-1998 [802.1Q]. It also
MIB module. details those objects that are not considered necessary in this MIB
module.
Note: unlike IEEE 802.1D, [20] chose not to define a new set of managed Note: unlike IEEE 802.1D-1998, IEEE 802.1Q-1998 [802.1Q] did not
object names so those following are referenced from the descriptions of define exact syntax for a set of managed objects: the following
management operations with section numbering from clause 12 in that cross-references indicate the section numbering of the descriptions
document. of management operations from clause 12 in the latter document.
Virtual Bridge MIB object 802.1Q object Virtual Bridge MIB object IEEE 802.1Q-1998 Reference
dot1qBase dot1qBase
dot1qVlanVersionNumber 12.10.1.1 read bridge vlan config dot1qVlanVersionNumber 12.10.1.1 read bridge vlan config
dot1qMaxVlanId 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 dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan config
dot1qNumVlans dot1qNumVlans
dot1dGvrpStatus 12.9.2.1/2 read/set garp dot1qGvrpStatus 12.9.2.1/2 read/set garp
applicant controls applicant controls
dot1qTp dot1qTp
dot1qFdbTable dot1qFdbTable
dot1qFdbId dot1qFdbId
dot1qFdbDynamicCount 12.7.1.1.3 read filtering d/base dot1qFdbDynamicCount 12.7.1.1.3 read filtering d/base
dot1qTpFdbTable dot1qTpFdbTable
dot1qTpFdbAddress dot1qTpFdbAddress
dot1qTpFdbPort dot1qTpFdbPort
dot1qTpFdbStatus dot1qTpFdbStatus
dot1qTpGroupTable 12.7.7.1 read filtering entry dot1qTpGroupTable 12.7.7.1 read filtering entry
dot1qTpGroupAddress dot1qTpGroupAddress
dot1qTpGroupEgressPorts dot1qTpGroupEgressPorts
dot1qTpGroupLearnt dot1qTpGroupLearnt
dot1qForwardAllTable 12.7.7.1 read filtering entry dot1qForwardAllTable 12.7.7.1 read filtering entry
dot1qForwardAllPorts dot1qForwardAllPorts
dot1qForwardAllStaticPorts dot1qForwardAllStaticPorts
dot1qForwardAllForbiddenPorts dot1qForwardAllForbiddenPorts
dot1qForwardUnregisteredTable 12.7.7.1 read filtering entry dot1qForwardUnregisteredTable 12.7.7.1 read filtering entry
dot1qForwardUnregisteredPorts dot1qForwardUnregisteredPorts
dot1qForwardUnregisteredStaticPorts dot1qForwardUnregisteredStaticPorts
dot1qForwardUnregisteredForbiddenPorts dot1qForwardUnregisteredForbiddenPorts
dot1qStatic dot1qStatic
dot1qStaticUnicastTable 12.7.7.1 create/delete/read dot1qStaticUnicastTable 12.7.7.1 create/delete/read
filtering entry filtering entry
12.7.6.1 read permanent database 12.7.6.1 read permanent database
dot1qStaticUnicastAddress dot1qStaticUnicastAddress
dot1qStaticUnicastReceivePort dot1qStaticUnicastReceivePort
dot1qStaticUnicastAllowedToGoTo dot1qStaticUnicastAllowedToGoTo
dot1qStaticUnicastStatus dot1qStaticUnicastStatus
dot1qStaticMulticastTable 12.7.7.1 create/delete/read dot1qStaticMulticastTable 12.7.7.1 create/delete/read
filtering entry filtering entry
12.7.6.1 read permanent database 12.7.6.1 read permanent database
dot1qStaticMulticastAddress dot1qStaticMulticastAddress
dot1qStaticMulticastReceivePort dot1qStaticMulticastReceivePort
dot1qStaticMulticastStaticEgressPorts dot1qStaticMulticastStaticEgressPorts
dot1qStaticMulticastForbiddenEgressPorts dot1qStaticMulticastForbiddenEgressPorts
dot1qStaticMulticastStatus dot1qStaticMulticastStatus
dot1qVlan dot1qVlan
dot1qVlanNumDeletes dot1qVlanNumDeletes
dot1qVlanCurrentTable 12.10.2.1 read vlan configuration dot1qVlanCurrentTable 12.10.2.1 read vlan configuration
12.10.3.5 read VID to FID 12.10.3.5 read VID to FID
allocations allocations
12.10.3.6 read FID allocated to VID 12.10.3.6 read FID allocated to
12.10.3.7 read VIDs allocated to VID
FID 12.10.3.7 read VIDs allocated to
dot1qVlanTimeMark FID
dot1qVlanIndex dot1qVlanTimeMark
dot1qVlanFdbId dot1qVlanIndex
dot1qVlanCurrentEgressPorts dot1qVlanFdbId
dot1qVlanCurrentUntaggedPorts dot1qVlanCurrentEgressPorts
dot1qVlanStatus dot1qVlanCurrentUntaggedPorts
dot1qVlanCreationTime dot1qVlanStatus
dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read dot1qVlanCreationTime
filtering entry dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read
12.7.6.1 read permanent database filtering entry
12.10.2.2 create vlan config 12.7.6.1 read permanent database
12.10.2.3 delete vlan config 12.10.2.2 create vlan config
dot1qVlanStaticName 12.4.1.3 set bridge name 12.10.2.3 delete vlan config
dot1qVlanStaticEgressPorts dot1qVlanStaticName 12.4.1.3 set bridge name
dot1qVlanForbiddenEgressPorts dot1qVlanStaticEgressPorts
dot1qVlanStaticUntaggedPorts dot1qVlanForbiddenEgressPorts
dot1qVlanStaticRowStatus dot1qVlanStaticUntaggedPorts
dot1qPortVlanConfigTable 12.10.1.1 read bridge vlan dot1qVlanStaticRowStatus
configuration dot1qNextFreeLocalVlanIndex
dot1qPvid 12.10.1.2 configure PVID values dot1qPortVlanTable 12.10.1.1 read bridge vlan
dot1qPortAcceptableFrameTypes 12.10.1.3 configure acceptable configuration
frame types parameter dot1qPvid 12.10.1.2 configure PVID values
dot1qPortIngressFiltering 12.10.1.4 configure ingress dot1qPortAcceptableFrameTypes 12.10.1.3 configure acceptable
filtering parameters frame types parameter
dot1qPortGvrpStatus 12.9.2.2 read/set garp applicant dot1qPortIngressFiltering 12.10.1.4 configure ingress
controls filtering parameters
dot1qPortGvrpFailedRegistrations dot1qPortGvrpStatus 12.9.2.2 read/set garp applicant
dot1qPortGvrpLastPduOrigin controls
dot1qPortVlanStatisticsTable 12.6.1.1 read forwarding port dot1qPortGvrpFailedRegistrations
counters dot1qPortGvrpLastPduOrigin
dot1qTpVlanPortInFrames dot1qPortVlanStatisticsTable 12.6.1.1 read forwarding port
dot1qTpVlanPortOutFrames counters
dot1qTpVlanPortInDiscards dot1qTpVlanPortInFrames
dot1qTpVlanPortInOverflowFrames dot1qTpVlanPortOutFrames
dot1qTpVlanPortOutOverflowFrames dot1qTpVlanPortInDiscards
dot1qTpVlanPortInOverflowDiscards dot1qTpVlanPortInOverflowFrames
dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port dot1qTpVlanPortOutOverflowFrames
counters dot1qTpVlanPortInOverflowDiscards
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
The following IEEE 802.1Q management objects have not been included in dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port
the Bridge MIB for the indicated reasons. 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
IEEE 802.1Q Object Disposition The following IEEE 802.1Q management objects have not been included
in the Bridge MIB for the indicated reasons.
reset bridge (12.4.1.4) not considered useful IEEE 802.1Q-1998 Operation Disposition
reset vlan bridge (12.10.1.5) not considered useful reset bridge (12.4.1.4) not considered useful
read forwarding port counters (12.6.1.1)
discard on error details not considered useful
read permanent database (12.7.6.1) reset vlan bridge (12.10.1.5) not considered useful
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. read forwarding port counters (12.6.1.1)
(12.7.7.4) discard on error details not considered useful
read filtering database (12.7.1.1) read permanent database (12.7.6.1)
filtering database size not considered useful permanent database size not considered useful
number of dynamic group address count rows applicable to each number of static filtering count rows in
entries (12.7.1.3) FDB in dot1dTpGroupTable entries dot1qStaticUnicastTable +
dot1qStaticMulticastTable
number of static VLAN count rows in
registration entries dot1qVlanStaticTable
read garp state (12.9.3.1) not considered useful read filtering entry range use GetNext operation.
(12.7.7.4)
notify vlan registration failure not considered useful read filtering database (12.7.1.1)
(12.10.1.6) filtering database size not considered useful
number of dynamic group address count rows applicable to each
entries (12.7.1.3) FDB in dot1dTpGroupTable
notify learning constraint violation read garp state (12.9.3.1) not considered useful
(12.10.3.10) not considered useful
notify vlan registration failure not considered useful
(12.10.1.6)
notify learning constraint violation
(12.10.3.10) not considered useful
3.2.2. The dot1qBase Group 3.2.2. The dot1qBase Group
This mandatory group contains the objects which are applicable to all This mandatory group contains the objects which are applicable to all
bridges implementing 802.1Q virtual LANs. bridges implementing IEEE 802.1Q virtual LANs.
3.2.3. The dot1qTp Group 3.2.3. The dot1qTp Group
This group contains objects that control the operation and report the This group contains objects that control the operation and report the
status of transparent bridging. This includes management of the dynamic status of transparent bridging. This includes management of the
Filtering Databases for both unicast and multicast forwarding. This dynamic Filtering Databases for both unicast and multicast
group will be implemented by all bridges that perform destination- forwarding. This group will be implemented by all bridges that
address filtering. perform destination-address filtering.
3.2.4. The dot1qStatic Group 3.2.4. The dot1qStatic Group
This group contains objects that control static configuration This group contains objects that control static configuration
information for transparent bridging. This includes management of the information for transparent bridging. This includes management of
static entries in the Filtering Databases for both unicast and multicast the static entries in the Filtering Databases for both unicast and
forwarding. multicast forwarding.
3.2.5. The dot1qVlan Group 3.2.5. The dot1qVlan Group
This group contains objects that control configuration and report status This group contains objects that control configuration and report
of the Virtual LANs known to a bridge. This includes management of the status of the Virtual LANs known to a bridge. This includes
statically configured VLANs as well as reporting VLANs discovered by management of the statically configured VLANs as well as reporting
other means e.g. GVRP. It also controls configuration and reports VLANs discovered by other means e.g. GVRP. It also controls
status of per-port objects relating to VLANs and reports traffic configuration and reports status of per-port objects relating to
statistics. It also provides for management of the VLAN Learning VLANs and reports traffic statistics. It also provides for
Constraints. management of the VLAN Learning Constraints.
3.3. Textual Conventions 3.3. Textual Conventions
The datatypes MacAddress, BridgeId, Timeout, EnabledStatus, PortList, The datatypes MacAddress, BridgeId, Timeout, EnabledStatus, PortList,
VlanIndex and VlanId are used as textual conventions in this document. VlanIndex and VlanId are used as textual conventions in this
These textual conventions have NO effect on either the syntax nor the document. These textual conventions have NO effect on either the
semantics of any managed object. Objects defined using these syntax nor the semantics of any managed object. Objects defined
conventions are always encoded by means of the rules that define their using these conventions are always encoded by means of the rules that
primitive type. Hence, no changes to the SMI or the SNMP are necessary define their primitive type. Hence, no changes to the SMI or the
to accommodate these textual conventions which are adopted merely for SNMP are necessary to accommodate these textual conventions which are
the convenience of readers. adopted merely for the convenience of readers.
3.4. Relationship to Other MIBs 3.4. Relationship to Other MIBs
As described above, some IEEE 802.1D management objects have not been As described above, some IEEE 802.1D management objects have not been
included in this MIB because they overlap with objects in other MIBs included in this MIB because they overlap with objects in other MIBs
applicable to a bridge implementing this MIB. In particular, it is applicable to a bridge implementing this MIB. In particular, it is
assumed that a bridge implementing this MIB will also implement (at assumed that a bridge implementing this MIB will also implement (at
least) the 'system' group defined in MIB-II [24], the 'interfaces' group least) the 'system' group defined in MIB-II [MIB2], the 'interfaces'
defined in [22] and the old Bridge MIB [21]. group defined in [INTERFACEMIB] and the original bridge MIB
[BRIDGEMIB].
3.4.1. Relationship to the 'system' group 3.4.1. Relationship to the 'system' group
In MIB-II, the 'system' group is defined as being mandatory for all In MIB-II, the 'system' group is defined as being mandatory for all
systems such that each managed entity contains one instance of each systems such that each managed entity contains one instance of each
object in the 'system' group. Thus, those objects apply to the entity object in the 'system' group. Thus, those objects apply to the
as a whole irrespective of whether the entity's sole functionality is entity as a whole irrespective of whether the entity's sole
bridging, or whether bridging is only a subset of the entity's functionality is bridging, or whether bridging is only a subset of
functionality. the entity's functionality.
3.4.2. Relation to Interfaces MIB 3.4.2. Relation to Interfaces MIB
RFC 1573, the Interface MIB Evolution [22], requires that any MIB which The Interfaces Group MIB [INTERFACEMIB], requires that any MIB which
is an adjunct of the Interface MIB, clarify specific areas within the is an adjunct of the Interfaces Group MIB, clarify specific areas
Interface MIB. These areas were intentionally left vague in [22] to within the Interfaces Group MIB. These areas were intentionally left
avoid over constraining the MIB, thereby precluding management of vague in the Interfaces Group MIB to avoid over-constraining the MIB,
certain media-types. thereby precluding management of certain media-types.
Section 3.3 of [22] enumerates several areas which a media-specific MIB The Interfaces Group MIB enumerates several areas which a media-
must clarify. Each of these areas is addressed in a following specific MIB must clarify. Each of these areas is addressed in a
subsection. The implementor is referred to [22] in order to understand following subsection. The implementor is referred to the Interfaces
the general intent of these areas. Group MIB in order to understand the general intent of these areas.
In [22], the 'interfaces' group is defined as being mandatory for all In the Interfaces Group MIB, the 'interfaces' group is defined as
systems and contains information on an entity's interfaces, where each being mandatory for all systems and contains information on an
interface is thought of as being attached to a `subnetwork'. (Note that entity's interfaces, where each interface is thought of as being
this term is not to be confused with `subnet' which refers to an attached to a `subnetwork'. (Note that this term is not to be
addressing partitioning scheme used in the Internet suite of protocols.) confused with `subnet' which refers to an addressing partitioning
The term 'segment' is used in this memo to refer to such a subnetwork, scheme used in the Internet suite of protocols.) The term 'segment'
whether it be an Ethernet segment, a 'ring', a WAN link, or even an X.25 is used in this memo to refer to such a subnetwork, whether it be an
virtual circuit. Ethernet segment, a 'ring', a WAN link, or even an X.25 virtual
circuit.
Implicit in this Bridge MIB is the notion of ports on a bridge. Each of Implicit in this Extended Bridge MIB is the notion of ports on a
these ports is associated with one interface of the 'interfaces' group bridge. Each of these ports is associated with one interface of the
(one row in ifTable) and, in most situations, each port is associated 'interfaces' group (one row in ifTable) and, in most situations, each
with a different interface. However, there are situations in which port is associated with a different interface. However, there are
multiple ports are associated with the same interface. An example of situations in which multiple ports are associated with the same
such a situation would be several ports each corresponding one-to-one interface. An example of such a situation would be several ports
with several X.25 virtual circuits but all on the same interface. each corresponding one-to-one with several X.25 virtual circuits but
all on the same interface.
Each port is uniquely identified by a port number. A port number has no Each port is uniquely identified by a port number. A port number has
mandatory relationship to an interface number, but in the simple case a no mandatory relationship to an interface number, but in the simple
port number will have the same value as the corresponding interface's case a port number will have the same value as the corresponding
interface number. Port numbers are in the range (1..dot1dBaseNumPorts). interface's interface number. Port numbers are in the range
(1..dot1dBaseNumPorts).
Some entities perform other functionality as well as bridging through Some entities perform other functionality as well as bridging through
the sending and receiving of data on their interfaces. In such the sending and receiving of data on their interfaces. In such
situations, only a subset of the data sent/received on an interface is situations, only a subset of the data sent/received on an interface
within the domain of the entity's bridging functionality. This subset is within the domain of the entity's bridging functionality. This
is considered to be delineated according to a set of protocols, with subset is considered to be delineated according to a set of
some protocols being bridged, and other protocols not being bridged. protocols, with some protocols being bridged, and other protocols not
For example, in an entity which exclusively performed bridging, all being bridged. For example, in an entity which exclusively performed
protocols would be considered as being bridged, whereas in an entity bridging, all protocols would be considered as being bridged, whereas
which performed IP routing on IP datagrams and only bridged other in an entity which performed IP routing on IP datagrams and only
protocols, only the non-IP data would be considered as being bridged. bridged other protocols, only the non-IP data would be considered as
Thus, this Bridge MIB (and in particular, its counters) is applicable being bridged. Thus, this Extended Bridge MIB (and in particular,
only to that subset of the data on an entity's interfaces which is its counters) is applicable only to that subset of the data on an
sent/received for a protocol being bridged. All such data is entity's interfaces which is sent/received for a protocol being
sent/received via the ports of the bridge. bridged. All such data is sent/received via the ports of the bridge.
3.4.2.1. Layering Model 3.4.2.1. Layering Model
This memo assumes the interpretation of the Interfaces Group to be in This memo assumes the interpretation of the Interfaces Group to be in
accordance with [22] which states that the interfaces table (ifTable) accordance with the Interfaces Group MIB [INTERFACEMIB] which states
contains information on the managed resource's interfaces and that each that the interfaces table (ifTable) contains information on the
sub-layer below the internetwork layer of a network interface is managed resource's interfaces and that each sub-layer below the
considered an interface. internetwork layer of a network interface is considered an interface.
This memo recommends that, within an entity, VLANs which are This document recommends that, within an entity, VLANs which are
instantiated as an entry in dot1qVlanCurrentTable by either management instantiated as an entry in dot1qVlanCurrentTable by either
configuration through dot1qVlanStaticTable or by dynamic means (e.g. management configuration through dot1qVlanStaticTable or by dynamic
through GVRP), are NOT also represented by an entry in ifTable. means (e.g. through GVRP), are NOT also represented by an entry in
ifTable.
Where an entity contains higher-layer protocol entities e.g. IP-layer Where an entity contains higher-layer protocol entities e.g. IP-layer
interfaces, that transmit and receive traffic to/from a VLAN, these interfaces that transmit and receive traffic to/from a VLAN, these
should be represented in the ifTable as interfaces of type should be represented in the ifTable as interfaces of type
propVirtual(53). 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.
3.4.2.2. ifStackTable 3.4.2.2. ifStackTable
In addition, [22] defines a table 'ifStackTable' for describing the In addition, the Interfaces Group MIB [INTERFACEMIB] defines a table
relationship between logical interfaces within an entity. It is 'ifStackTable' for describing the relationship between logical
anticipated that implementors will use this table to describe the interfaces within an entity. It is anticipated that implementors
binding of e.g. IP interfaces to physical ports, although the presence will use this table to describe the binding of e.g. IP interfaces to
of VLANs makes the representation less than perfect for showing physical ports, although the presence of VLANs makes the
connectivity: the ifStackTable cannot represent the full capability of representation less than perfect for showing connectivity: the
the 802.1Q VLAN bridging standard since that makes a distinction between ifStackTable cannot represent the full capability of the IEEE 802.1Q
VLAN bindings on 'ingress' to and 'egress' from a port: these VLAN bridging standard since that makes a distinction between VLAN
relationships may or may not be symmetrical whereas [22] assumes a bindings on 'ingress' to and 'egress' from a port: these
symmetrical binding for transmit and receive. This makes it necessary relationships may or may not be symmetrical whereas Interface MIB
to define other manageable objects for configuring which ports are Evolution assumes a symmetrical binding for transmit and receive.
members of which VLANs. This makes it necessary to define other manageable objects for
configuring which ports are members of which VLANs.
3.4.2.3. ifRcvAddressTable 3.4.2.3. ifRcvAddressTable
This table contains all MAC addresses, unicast, multicast, and This table contains all MAC addresses, unicast, multicast, and
broadcast, for which an interface will receive packets and forward them broadcast, for which an interface will receive packets and forward
up to a higher layer entity for local consumption. Note that this does them up to a higher layer entity for local consumption. Note that
not include addresses for data-link layer control protocols such as this does not include addresses for data-link layer control protocols
Spanning-Tree, GMRP or GVRP. The format of the address, contained in such as Spanning-Tree, GMRP or GVRP. The format of the address,
ifRcvAddressAddress, is the same as for ifPhysAddress. contained in ifRcvAddressAddress, is the same as for ifPhysAddress.
This table does not include unicast or multicast addresses which are This table does not include unicast or multicast addresses which are
accepted for possible forwarding out some other port. This table is accepted for possible forwarding out some other port. This table is
explicitly not intended to provide a bridge address filtering mechanism. explicitly not intended to provide a bridge address filtering
mechanism.
3.4.3. Relation to Basic Bridge MIB 3.4.3. Relation to Original Bridge MIB
This section defines how objects in the basic bridge MIB module should This section defines how objects in the original bridge MIB module
be represented for devices which implement the extensions: some of the [BRIDGEMIB] should be represented for devices which implement the
old objects are less useful in such devices but must still be extensions: some of the old objects are less useful in such devices
implemented for reasons of backwards comaptibility. Note that formal but must still be implemented for reasons of backwards compatibility.
conformance statements for that MIB module do not exist since it is Note that formal conformance statements for that MIB module do not
defined in SMIv1. exist since it is defined in SMIv1.
3.4.3.1. The dot1dBase Group 3.4.3.1. The dot1dBase Group
This mandatory group contains the objects which are applicable to all This mandatory group contains the objects which are applicable to all
types of bridges. Interpretation of this group is unchanged. types of bridges. Interpretation of this group is unchanged.
3.4.3.2. The dot1dStp Group 3.4.3.2. The dot1dStp Group
This group contains the objects that denote the bridge's state with This group contains the objects that denote the bridge's state with
respect to the Spanning Tree Protocol. Interpretation of this group is respect to the Spanning Tree Protocol. Interpretation of this group
unchanged. is unchanged.
3.4.3.3. The dot1dTp Group 3.4.3.3. The dot1dTp Group
This group contains objects that describe the entity's state with This group contains objects that describe the entity's state with
respect to transparent bridging. respect to transparent bridging.
In a device operating with a single Filtering Database, interpretation In a device operating with a single Filtering Database,
of this group is unchanged. interpretation of this group is unchanged.
In a device supporting multiple Filtering Databases, this group is In a device supporting multiple Filtering Databases, this group is
interpreted as follows: interpreted as follows:
dot1dTpLearnedEntryDiscards dot1dTpLearnedEntryDiscards
The number of times that *any* of the FDBs became full. The number of times that *any* of the FDBs became full.
dot1dTpAgingTime dot1dTpAgingTime
This applies to all Filtering Databases. This applies to all Filtering Databases.
dot1dTpFdbTable dot1dTpFdbTable
Report MAC addresses learned on each port, regardless of which Report MAC addresses learned on each port, regardless of which
Filtering Database they have been learnt in. If an address has Filtering Database they have been learnt in. If an address has
been learnt in multiple databases on a single port, report it only been learnt in multiple databases on a single port, report it
once. If an address has been learnt in multiple databases on more only once. If an address has been learnt in multiple
than one port, report the entry on any one of the valid ports. databases on more than one port, report the entry on any one of
the valid ports.
dot1dTpPortTable dot1dTpPortTable
This table is port-based and is not affected by multiple Filtering This table is port-based and is not affected by multiple
Databases or multiple VLANs. The counters should include frames Filtering Databases or multiple VLANs. The counters should
received or transmitted for all VLANs. Note that equivalent 64-bit include frames received or transmitted for all VLANs. Note that
port statistics counters are defined in this document for high- equivalent 64-bit port statistics counters, as well as other
capacity network interfaces with conformance statements to indicate objects to represent the upper 32 bits of these counters, are
for which speeds of interface they are required. defined in this document for high capacity network interfaces.
These have confromance statements to indicate for which speeds of
interface they are required.
3.4.3.4. The dot1dStatic Group 3.4.3.4. The dot1dStatic Group
This optional group contains objects that describe the configuration of This optional group contains objects that describe the configuration
destination-address filtering. 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 In a device operating with a single Filtering Database,
interpreted as follows: interpretation of this group is unchanged.
dot1dStaticTable In a device supporting multiple Filtering Databases, this group is
Entries read from this table include all static entries from all of interpreted as follows:
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.
4. Extensions to RFC 1493 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.
In addition to the objects in RFC1493, this document contains: 3.4.3.5. Additions to the Original Bridge MIB
(1) References point to sections of IEEE 802.1D-1998. In addition to the objects in the original bridge MIB [BRIDGEMIB],
this document contains:
(2) Added support for multiple traffic classes and dynamic multicast (1) support for multiple traffic classes and dynamic multicast
filtering as per IEEE 802.1D-1998. filtering as per IEEE 802.1D-1998 [802.1D].
(3) Added support for bridged Virtual LANs as per IEEE 802.1Q-1998. (2) support for bridged Virtual LANs as per IEEE 802.1Q-1998
[802.1Q].
(4) Added support for 64-bit versions of existing RFC1493 port (3) support for 64-bit versions of original bridge MIB [BRIDGEMIB]
counters. port counters.
5. Definitions for Extended Bridge MIB 4. Definitions for Extended Bridge MIB
P-BRIDGE-MIB DEFINITIONS ::= BEGIN P-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- MIB for IEEE 802.1p devices
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dTp, dot1dTpPort, dot1dBridge, dot1dTp, dot1dTpPort, dot1dBridge,
dot1dBasePortEntry, dot1dBasePort dot1dBasePortEntry, dot1dBasePort
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
pBridgeMIB MODULE-IDENTITY pBridgeMIB MODULE-IDENTITY
LAST-UPDATED "9903020000Z" LAST-UPDATED "9908250000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Les Bell " Les Bell
Postal: 3Com Europe Ltd. Postal: 3Com Europe Ltd.
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead, Herts. HP2 7YU Hemel Hempstead, Herts. HP2 7YU
UK UK
Phone: +44 (1442) 438025 Phone: +44 1442 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
Andrew Smith Andrew Smith
Postal: Extreme Networks Postal: Extreme Networks
10460 Bandley Drive 3585 Monroe St.
Cupertino CA 95014 Santa Clara CA 95051
USA USA
Phone: +1 (408) 342 0999 Phone: +1 408 579 2821
Email: andrew@extremenetworks.com Email: andrew@extremenetworks.com
Paul Langille Paul Langille
Postal: Newbridge Networks Postal: Newbridge Networks
5 Corporate Drive 5 Corporate Drive
Andover, MA 01810 Andover, MA 01810
USA USA
Phone: +1 978 691 4665
Phone: +1 (978) 691 4665
Email: langille@newbridge.com Email: langille@newbridge.com
Anil Rijhsinghani Anil Rijhsinghani
Postal: Cabletron Systems Postal: Cabletron Systems
50 Minuteman Road 50 Minuteman Road
Andover MA 01810 Andover, MA 01810
USA USA
Phone: +1 (978) 684 1295 Phone: +1 978 684 1295
Email: anil@cabletron.com Email: anil@cabletron.com
Keith McCloghrie Keith McCloghrie
Postal: cisco Systems, Inc. Postal: cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
USA USA
Phone: +1 (408) 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing Priority "The Bridge MIB Extension module for managing Priority
and Multicast Filtering, defined by IEEE 802.1D-1998." and Multicast Filtering, defined by IEEE 802.1D-1998."
-- revision history
REVISION "9908250000Z"
DESCRIPTION
"Initial version, published as RFC 2674."
::= { dot1dBridge 6 } ::= { dot1dBridge 6 }
pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 } pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
EnabledStatus ::= TEXTUAL-CONVENTION EnabledStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 21, line 45 skipping to change at page 21, line 29
-- each port. -- each port.
dot1dLocalVlanCapable(7) dot1dLocalVlanCapable(7)
-- can support multiple local -- can support multiple local
-- bridges, outside of the scope -- bridges, outside of the scope
-- of 802.1Q defined VLANs. -- of 802.1Q defined VLANs.
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the optional parts of IEEE 802.1D and 802.1Q "Indicates the optional parts of IEEE 802.1D and 802.1Q
that are implemented by this device and are managable that are implemented by this device and are manageable
through this MIB. Capabilities that are allowed on a through this MIB. Capabilities that are allowed on a
per-port basis are indicated in dot1dPortCapabilities." per-port basis are indicated in dot1dPortCapabilities."
REFERENCE REFERENCE
"ISO/IEC 15802-3 Section 5.2, "ISO/IEC 15802-3 Section 5.2,
IEEE 802.1Q/D11 Section 5.2, 12.10.1.1.3/b/2" IEEE 802.1Q/D11 Section 5.2, 12.10.1.1.3/b/2"
::= { dot1dExtBase 1 } ::= { dot1dExtBase 1 }
dot1dTrafficClassesEnabled OBJECT-TYPE dot1dTrafficClassesEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 23, line 40 skipping to change at page 23, line 17
-- frame received on a Port whose -- frame received on a Port whose
-- VLAN classification does not -- VLAN classification does not
-- include that Port in its Member -- include that Port in its Member
-- set. -- set.
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the parts of IEEE 802.1D and 802.1Q that are "Indicates the parts of IEEE 802.1D and 802.1Q that are
optional on a per-port basis that are implemented by optional on a per-port basis that are implemented by
this device and are managable through this MIB." this device and are manageable through this MIB."
REFERENCE REFERENCE
"ISO/IEC 15802-3 Section 5.2, "ISO/IEC 15802-3 Section 5.2,
IEEE 802.1Q/D11 Section 5.2" IEEE 802.1Q/D11 Section 5.2"
::= { dot1dPortCapabilitiesEntry 1 } ::= { dot1dPortCapabilitiesEntry 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- the dot1dPriority group -- the dot1dPriority group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Port Priority Table -- Port Priority Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dPortPriorityTable OBJECT-TYPE dot1dPortPriorityTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortPriorityEntry SYNTAX SEQUENCE OF Dot1dPortPriorityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains information about every port that "A table that contains information about every port that
skipping to change at page 30, line 39 skipping to change at page 30, line 5
Counter32, Counter32,
dot1dPortGmrpLastPduOrigin dot1dPortGmrpLastPduOrigin
MacAddress MacAddress
} }
dot1dPortGmrpStatus OBJECT-TYPE dot1dPortGmrpStatus OBJECT-TYPE
SYNTAX EnabledStatus SYNTAX EnabledStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of GMRP operation on this port. The value "The administrative state of GMRP operation on this port. The
enabled(1) indicates that GMRP is enabled on this port, value enabled(1) indicates that GMRP is enabled on this port
in all VLANs, as long as dot1dGmrpStatus is also enabled in all VLANs as long as dot1dGmrpStatus is also enabled(1).
for this device. When disabled(2) but dot1dGmrpStatus A value of disabled(2) indicates that GMRP is disabled on
is still enabled for the device, GMRP is disabled on
this port in all VLANs: any GMRP packets received will this port in all VLANs: any GMRP packets received will
be silently discarded and no GMRP registrations will be be silently discarded and no GMRP registrations will be
propagated from other ports. This object affects all propagated from other ports. Setting this to a value of
GMRP Applicant and Registrar state machines on this 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 port. A transition from disabled(2) to enabled(1) will
cause a reset of all GMRP state machines on this port." cause a reset of all GMRP state machines on this port."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1dPortGmrpEntry 1 } ::= { dot1dPortGmrpEntry 1 }
dot1dPortGmrpFailedRegistrations OBJECT-TYPE dot1dPortGmrpFailedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 33, line 11 skipping to change at page 32, line 21
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of valid frames that have been received by this "Count of valid frames that have been received by this
port from its segment which were discarded (i.e., port from its segment which were discarded (i.e.,
filtered) by the Forwarding Process." filtered) by the Forwarding Process."
REFERENCE REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3" "ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 3 } ::= { dot1dTpHCPortEntry 3 }
-- ----------------------------------------------------
-- Upper part of High Capacity Port Table for Transparent Bridges
-- ----------------------------------------------------
dot1dTpPortOverflowTable OBJECT-TYPE dot1dTpPortOverflowTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dTpPortOverflowEntry SYNTAX SEQUENCE OF Dot1dTpPortOverflowEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains information about every high "A table that contains the most-significant bits of
capacity port that is associated with this transparent statistics counters for ports that are associated with this
bridge." 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.
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 } ::= { dot1dTp 6 }
dot1dTpPortOverflowEntry OBJECT-TYPE dot1dTpPortOverflowEntry OBJECT-TYPE
SYNTAX Dot1dTpPortOverflowEntry SYNTAX Dot1dTpPortOverflowEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Statistics information for each high capacity port of a "The most significant bits of statistics counters for a high
transparent bridge." 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 } INDEX { dot1dTpPort }
::= { dot1dTpPortOverflowTable 1 } ::= { dot1dTpPortOverflowTable 1 }
Dot1dTpPortOverflowEntry ::= Dot1dTpPortOverflowEntry ::=
SEQUENCE { SEQUENCE {
dot1dTpPortInOverflowFrames dot1dTpPortInOverflowFrames
Counter32, Counter32,
dot1dTpPortOutOverflowFrames dot1dTpPortOutOverflowFrames
Counter32, Counter32,
dot1dTpPortInOverflowDiscards dot1dTpPortInOverflowDiscards
skipping to change at page 38, line 5 skipping to change at page 37, line 32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for device support of Priority "The compliance statement for device support of Priority
and Multicast Filtering extended bridging services." and Multicast Filtering extended bridging services."
MODULE MODULE
MANDATORY-GROUPS { pBridgeExtCapGroup } MANDATORY-GROUPS { pBridgeExtCapGroup }
GROUP pBridgeDeviceGmrpGroup GROUP pBridgeDeviceGmrpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices supporting the "This group is mandatory for devices supporting the GMRP
GMRP application, defined by the extended filtering application, defined by IEEE 802.1D Extended Filtering
services." Services."
GROUP pBridgeDevicePriorityGroup GROUP pBridgeDevicePriorityGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by the the priority forwarding operations defined by IEEE
extended bridge services." 802.1D."
GROUP pBridgeDefaultPriorityGroup GROUP pBridgeDefaultPriorityGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by the the priority forwarding operations defined by the
extended bridge services with media types, such as extended bridge services with media types, such as
Ethernet, that do not support native User Priority." Ethernet, that do not support native User Priority."
GROUP pBridgeRegenPriorityGroup GROUP pBridgeRegenPriorityGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by the the priority forwarding operations defined by IEEE 802.1D
extended bridge services with media types that also and which have interface media types that support
support native User Priority." native User Priority e.g. IEEE 802.5."
GROUP pBridgePriorityGroup GROUP pBridgePriorityGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for devices supporting "This group is mandatory only for devices supporting
the priority forwarding operations defined by the the priority forwarding operations defined by IEEE 802.1D."
extended bridge services."
GROUP pBridgeAccessPriorityGroup GROUP pBridgeAccessPriorityGroup
DESCRIPTION DESCRIPTION
"This group is optional." "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."
GROUP pBridgePortGarpGroup GROUP pBridgePortGarpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices supporting any "This group is mandatory for devices supporting any
of the GARP applications: e.g. GMRP, defined by the of the GARP applications: e.g. GMRP, defined by the
extended filtering services of 802.1D; or GVRP, extended filtering services of 802.1D; or GVRP,
defined by 802.1Q (refer to the Q-BRIDGE-MIB for defined by 802.1Q (refer to the Q-BRIDGE-MIB for
conformance statements for GVRP)." conformance statements for GVRP)."
GROUP pBridgePortGmrpGroup GROUP pBridgePortGmrpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices supporting the "This group is mandatory for devices supporting the
GMRP application, defined by the extended filtering GMRP application, as defined by IEEE 802.1D Extended
services." Filtering Services."
GROUP pBridgeHCPortGroup GROUP pBridgeHCPortGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the network interface "Support for this group in a device is mandatory for those
to which this bridge port is attached has the bridge ports which map to network interfaces that have the
value of the corresponding instance of ifSpeed value of the corresponding instance of ifSpeed
greater than 650,000,000 bits/second." greater than 650,000,000 bits/second."
GROUP pBridgePortOverflowGroup GROUP pBridgePortOverflowGroup
DESCRIPTION DESCRIPTION
"This group is optional." "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."
OBJECT dot1dPortNumTrafficClasses OBJECT dot1dPortNumTrafficClasses
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dot1dTrafficClass OBJECT dot1dTrafficClass
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dot1dRegenUserPriority OBJECT dot1dRegenUserPriority
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { pBridgeCompliances 1 } ::= { pBridgeCompliances 1 }
END END
6. Definitions for Virtual Bridge MIB
5. Definitions for Virtual Bridge MIB
Q-BRIDGE-MIB DEFINITIONS ::= BEGIN Q-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- MIB for IEEE 802.1Q Devices
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Counter64, Unsigned32, TimeTicks Counter32, Counter64, Unsigned32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, TruthValue, DisplayString, TEXTUAL-CONVENTION, RowStatus, TruthValue, TEXTUAL-CONVENTION, MacAddress
MacAddress
FROM SNMPv2-TC FROM SNMPv2-TC
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dBridge, dot1dBasePortEntry, dot1dBasePort dot1dBridge, dot1dBasePortEntry, dot1dBasePort
FROM BRIDGE-MIB FROM BRIDGE-MIB
EnabledStatus EnabledStatus
FROM P-BRIDGE-MIB FROM P-BRIDGE-MIB
TimeFilter TimeFilter
FROM RMON2-MIB; FROM RMON2-MIB;
qBridgeMIB MODULE-IDENTITY qBridgeMIB MODULE-IDENTITY
LAST-UPDATED "9903020000Z" LAST-UPDATED "9908250000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Les Bell " Les Bell
Postal: 3Com Europe Ltd. Postal: 3Com Europe Ltd.
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead, Herts. HP2 7YU Hemel Hempstead, Herts. HP2 7YU
UK UK
Phone: +44 (1442) 438025 Phone: +44 1442 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
Andrew Smith Andrew Smith
Postal: Extreme Networks Postal: Extreme Networks
10460 Bandley Drive 3585 Monroe St.
Cupertino CA 95014 Santa Clara CA 95051
USA USA
Phone: +1 (408) 342 0999 Phone: +1 408 579 2821
Email: andrew@extremenetworks.com Email: andrew@extremenetworks.com
Paul Langille Paul Langille
Postal: Newbridge Networks Postal: Newbridge Networks
5 Corporate Drive 5 Corporate Drive
Andover, MA 01810 Andover, MA 01810
USA USA
Phone: +1 (978) 691 4665 Phone: +1 978 691 4665
Email: langille@newbridge.com Email: langille@newbridge.com
Anil Rijhsinghani Anil Rijhsinghani
Postal: Cabletron Systems Postal: Cabletron Systems
50 Minuteman Road 50 Minuteman Road
Andover MA 01810 Andover, MA 01810
USA USA
Phone: +1 (978) 684 1295 Phone: +1 978 684 1295
Email: anil@cabletron.com Email: anil@cabletron.com
Keith McCloghrie Keith McCloghrie
Postal: cisco Systems, Inc. Postal: cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
USA USA
Phone: +1 (408) 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The VLAN Bridge MIB module for managing Virtual Bridged "The VLAN Bridge MIB module for managing Virtual Bridged
Local Area Networks, as defined by IEEE 802.1Q-1998." Local Area Networks, as defined by IEEE 802.1Q-1998."
-- revision history
REVISION "9908250000Z"
DESCRIPTION
"Initial version, published as RFC 2674."
::= { dot1dBridge 7 } ::= { dot1dBridge 7 }
qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 } qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
PortList ::= TEXTUAL-CONVENTION PortList ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 42, line 13 skipping to change at page 41, line 39
value of this object. If that bit has a value of '1' value of this object. If that bit has a value of '1'
then that port is included in the set of ports; the port then that port is included in the set of ports; the port
is not included if its bit has a value of '0'." is not included if its bit has a value of '0'."
SYNTAX OCTET STRING SYNTAX OCTET STRING
VlanIndex ::= TEXTUAL-CONVENTION VlanIndex ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value used to index per-VLAN tables: values of 0 and "A value used to index per-VLAN tables: values of 0 and
4095 are not permitted; if the value is between 1 and 4095 are not permitted; if the value is between 1 and
4094 inclusive, it represents an 802.1Q VLAN-ID with 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with
global scope within a given bridged domain (see VlanId global scope within a given bridged domain (see VlanId
textual convention). If the value is greater than 4095 textual convention). If the value is greater than 4095
then it represents a VLAN with scope local to the then it represents a VLAN with scope local to the
particular agent." 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 SYNTAX Unsigned32
VlanId ::= TEXTUAL-CONVENTION VlanId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The 12-bit VLAN ID used in the VLAN Tag header." "A 12-bit VLAN ID used in the VLAN Tag header."
SYNTAX INTEGER (1..4094) SYNTAX INTEGER (1..4094)
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- groups in the Q-BRIDGE MIB -- groups in the Q-BRIDGE MIB
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qBase OBJECT IDENTIFIER ::= { qBridgeMIBObjects 1 } dot1qBase OBJECT IDENTIFIER ::= { qBridgeMIBObjects 1 }
dot1qTp OBJECT IDENTIFIER ::= { qBridgeMIBObjects 2 } dot1qTp OBJECT IDENTIFIER ::= { qBridgeMIBObjects 2 }
dot1qStatic OBJECT IDENTIFIER ::= { qBridgeMIBObjects 3 } dot1qStatic OBJECT IDENTIFIER ::= { qBridgeMIBObjects 3 }
dot1qVlan OBJECT IDENTIFIER ::= { qBridgeMIBObjects 4 } dot1qVlan OBJECT IDENTIFIER ::= { qBridgeMIBObjects 4 }
skipping to change at page 62, line 36 skipping to change at page 61, line 45
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Static information for a VLAN configured into the "Static information for a VLAN configured into the
device by (local or network) management." device by (local or network) management."
INDEX { dot1qVlanIndex } INDEX { dot1qVlanIndex }
::= { dot1qVlanStaticTable 1 } ::= { dot1qVlanStaticTable 1 }
Dot1qVlanStaticEntry ::= Dot1qVlanStaticEntry ::=
SEQUENCE { SEQUENCE {
dot1qVlanStaticName dot1qVlanStaticName
DisplayString, SnmpAdminString,
dot1qVlanStaticEgressPorts dot1qVlanStaticEgressPorts
PortList, PortList,
dot1qVlanForbiddenEgressPorts dot1qVlanForbiddenEgressPorts
PortList, PortList,
dot1qVlanStaticUntaggedPorts dot1qVlanStaticUntaggedPorts
PortList, PortList,
dot1qVlanStaticRowStatus dot1qVlanStaticRowStatus
RowStatus RowStatus
} }
dot1qVlanStaticName OBJECT-TYPE dot1qVlanStaticName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An administratively assigned string, which may be used "An administratively assigned string, which may be used
to identify the VLAN." to identify the VLAN."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 1 } ::= { dot1qVlanStaticEntry 1 }
dot1qVlanStaticEgressPorts OBJECT-TYPE dot1qVlanStaticEgressPorts OBJECT-TYPE
skipping to change at page 64, line 12 skipping to change at page 63, line 21
"IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 3 } ::= { dot1qVlanStaticEntry 3 }
dot1qVlanStaticUntaggedPorts OBJECT-TYPE dot1qVlanStaticUntaggedPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which should transmit egress packets "The set of ports which should transmit egress packets
for this VLAN as untagged. The default value of this for this VLAN as untagged. The default value of this
object for the default VLAN (VlanId 001) is a string object for the default VLAN (dot1qVlanIndex = 1) is a string
of appropriate length including all ports. There is no of appropriate length including all ports. There is no
specified default for other VLANs. If a device cannot specified default for other VLANs. If a device agent cannot
support a value being set then its agent will reject the support the set of ports being set then it will reject the
set operation. Attempts to set more than one VLAN to be set operation with an error. An example might be if a
untagged on egress may be rejected by devices which do manager attempts to set more than one VLAN to be untagged
not support this option." on egress where the device does not support this IEEE 802.1Q
option."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 4 } ::= { dot1qVlanStaticEntry 4 }
dot1qVlanStaticRowStatus OBJECT-TYPE dot1qVlanStaticRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the status of this entry." "This object indicates the status of this entry."
::= { dot1qVlanStaticEntry 5 } ::= { dot1qVlanStaticEntry 5 }
dot1qNextFreeLocalVlanIndex OBJECT-TYPE dot1qNextFreeLocalVlanIndex OBJECT-TYPE
SYNTAX INTEGER (0|4096..2147483647) SYNTAX INTEGER (0|4096..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The next available value for dot1qVlanIndex of a local "The next available value for dot1qVlanIndex of a local
VLAN entry in dot1qVlanStaticTable. This will always VLAN entry in dot1qVlanStaticTable. This will report
report values >=4096, if a new Local VLAN may be values >=4096 if a new Local VLAN may be created or else
created, or the value 0 if this is not possible. A row the value 0 if this is not possible.
creation operation in this table for an entry with a
local VlanIndex value may fail if this value is not used A row creation operation in this table for an entry with a local
as the index. This value will automatically change when VlanIndex value may fail if the current value of this object
the current value is used." 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.
This value will automatically change when the current value is
used to create a new row."
::= { dot1qVlan 4 } ::= { dot1qVlan 4 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The VLAN Port Configuration Table -- The VLAN Port Configuration Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qPortVlanTable OBJECT-TYPE dot1qPortVlanTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanEntry SYNTAX SEQUENCE OF Dot1qPortVlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing per port control and status "A table containing per port control and status
information for VLAN configuration in the device." information for VLAN configuration in the device."
::= { dot1qVlan 5 } ::= { dot1qVlan 5 }
dot1qPortVlanEntry OBJECT-TYPE dot1qPortVlanEntry OBJECT-TYPE
skipping to change at page 65, line 45 skipping to change at page 65, line 17
dot1qPortGvrpLastPduOrigin dot1qPortGvrpLastPduOrigin
MacAddress MacAddress
} }
dot1qPvid OBJECT-TYPE dot1qPvid OBJECT-TYPE
SYNTAX VlanIndex SYNTAX VlanIndex
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PVID, the VLAN ID assigned to untagged frames or "The PVID, the VLAN ID assigned to untagged frames or
Prority-Tagged frames received on this port." Priority-Tagged frames received on this port."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.1" "IEEE 802.1Q/D11 Section 12.10.1.1"
DEFVAL { 1 } DEFVAL { 1 }
::= { dot1qPortVlanEntry 1 } ::= { dot1qPortVlanEntry 1 }
dot1qPortAcceptableFrameTypes OBJECT-TYPE dot1qPortAcceptableFrameTypes OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
admitAll(1), admitAll(1),
admitOnlyVlanTagged(2) admitOnlyVlanTagged(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this is admitOnlyVlanTagged(2) the device will "When this is admitOnlyVlanTagged(2) the device will
discard untagged frames or Prority-Tagged frames discard untagged frames or Priority-Tagged frames
received on this port. When admitAll(1), untagged received on this port. When admitAll(1), untagged
frames or Prority-Tagged frames received on this port frames or Priority-Tagged frames received on this port
will be accepted and assigned to the PVID for this port. will be accepted and assigned to the PVID for this port.
This control does not affect VLAN independent BPDU This control does not affect VLAN independent BPDU
frames, such as GVRP and STP. It does affect VLAN frames, such as GVRP and STP. It does affect VLAN
dependent BPDU frames, such as GMRP." dependent BPDU frames, such as GMRP."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.1.3" "IEEE 802.1Q/D11 Section 12.10.1.3"
DEFVAL { admitAll } DEFVAL { admitAll }
::= { dot1qPortVlanEntry 2 } ::= { dot1qPortVlanEntry 2 }
skipping to change at page 67, line 47 skipping to change at page 67, line 18
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Per port VLAN Statistics Table -- Per port VLAN Statistics Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qPortVlanStatisticsTable OBJECT-TYPE dot1qPortVlanStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing per port, per VLAN statistics for "A table containing per-port, per-VLAN statistics for
traffic received." 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.
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 } ::= { dot1qVlan 6 }
dot1qPortVlanStatisticsEntry OBJECT-TYPE dot1qPortVlanStatisticsEntry OBJECT-TYPE
SYNTAX Dot1qPortVlanStatisticsEntry SYNTAX Dot1qPortVlanStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Traffic statistics for a VLAN on an interface." "Traffic statistics for a VLAN on an interface."
INDEX { dot1dBasePort, dot1qVlanIndex } INDEX { dot1dBasePort, dot1qVlanIndex }
::= { dot1qPortVlanStatisticsTable 1 } ::= { dot1qPortVlanStatisticsTable 1 }
skipping to change at page 69, line 11 skipping to change at page 68, line 43
::= { dot1qPortVlanStatisticsEntry 1 } ::= { dot1qPortVlanStatisticsEntry 1 }
dot1qTpVlanPortOutFrames OBJECT-TYPE dot1qTpVlanPortOutFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid frames transmitted by this port to "The number of valid frames transmitted by this port to
its segment from the local forwarding process for this its segment from the local forwarding process for this
VLAN. This includes bridge management frames originated VLAN. This includes bridge management frames originated
by this device whach are classified as belonging to this by this device which are classified as belonging to this
VLAN (e.g. GMRP, but not GVRP or STP)." VLAN (e.g. GMRP, but not GVRP or STP)."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanStatisticsEntry 2 } ::= { dot1qPortVlanStatisticsEntry 2 }
dot1qTpVlanPortInDiscards OBJECT-TYPE dot1qTpVlanPortInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 70, line 26 skipping to change at page 70, line 11
REFERENCE REFERENCE
"ISO/IEC 15802-3 Section 14.6.1.1.3" "ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1qPortVlanStatisticsEntry 6 } ::= { dot1qPortVlanStatisticsEntry 6 }
dot1qPortVlanHCStatisticsTable OBJECT-TYPE dot1qPortVlanHCStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing per port, per VLAN statistics for "A table containing per port, per VLAN statistics for
traffic received on high capacity interfaces." traffic on high capacity interfaces."
::= { dot1qVlan 7 } ::= { dot1qVlan 7 }
dot1qPortVlanHCStatisticsEntry OBJECT-TYPE dot1qPortVlanHCStatisticsEntry OBJECT-TYPE
SYNTAX Dot1qPortVlanHCStatisticsEntry SYNTAX Dot1qPortVlanHCStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Traffic statistics for a VLAN on a high capacity "Traffic statistics for a VLAN on a high capacity
interface." interface."
INDEX { dot1dBasePort, dot1qVlanIndex } INDEX { dot1dBasePort, dot1qVlanIndex }
skipping to change at page 71, line 28 skipping to change at page 71, line 13
::= { dot1qPortVlanHCStatisticsEntry 1 } ::= { dot1qPortVlanHCStatisticsEntry 1 }
dot1qTpVlanPortHCOutFrames OBJECT-TYPE dot1qTpVlanPortHCOutFrames OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid frames transmitted by this port to "The number of valid frames transmitted by this port to
its segment from the local forwarding process for this its segment from the local forwarding process for this
VLAN. This includes bridge management frames originated VLAN. This includes bridge management frames originated
by this device whach are classified as belonging to this by this device which are classified as belonging to this
VLAN (e.g. GMRP, but not GVRP or STP)." VLAN (e.g. GMRP, but not GVRP or STP)."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanHCStatisticsEntry 2 } ::= { dot1qPortVlanHCStatisticsEntry 2 }
dot1qTpVlanPortHCInDiscards OBJECT-TYPE dot1qTpVlanPortHCInDiscards OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 77, line 35 skipping to change at page 77, line 13
::= { qBridgeGroups 9 } ::= { qBridgeGroups 9 }
qBridgeVlanStatisticsOverflowGroup OBJECT-GROUP qBridgeVlanStatisticsOverflowGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qTpVlanPortInOverflowFrames, dot1qTpVlanPortInOverflowFrames,
dot1qTpVlanPortOutOverflowFrames, dot1qTpVlanPortOutOverflowFrames,
dot1qTpVlanPortInOverflowDiscards dot1qTpVlanPortInOverflowDiscards
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing per-port packet "A collection of objects providing overflow counters for
overflow statistics for all VLANs currently configured per-port packet statistics for all VLANs currently configured
on this device." 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 } ::= { qBridgeGroups 10 }
qBridgeVlanHCStatisticsGroup OBJECT-GROUP qBridgeVlanHCStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qTpVlanPortHCInFrames, dot1qTpVlanPortHCInFrames,
dot1qTpVlanPortHCOutFrames, dot1qTpVlanPortHCOutFrames,
dot1qTpVlanPortHCInDiscards dot1qTpVlanPortHCInDiscards
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing per-port packet "A collection of objects providing per-port packet
statistics for all VLANs currently configured on this statistics for all VLANs currently configured on this
device for high capacity interfaces." 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 } ::= { qBridgeGroups 11 }
qBridgeLearningConstraintsGroup OBJECT-GROUP qBridgeLearningConstraintsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qConstraintType, dot1qConstraintType,
dot1qConstraintStatus dot1qConstraintStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the Filtering Database "A collection of objects defining the Filtering Database
skipping to change at page 79, line 27 skipping to change at page 79, line 7
extended filtering services. All objects must be extended filtering services. All objects must be
read-write if extended-filtering services are read-write if extended-filtering services are
enabled." enabled."
GROUP qBridgeFdbStaticGroup GROUP qBridgeFdbStaticGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
GROUP qBridgeVlanStatisticsGroup GROUP qBridgeVlanStatisticsGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional as there may be significant
implementation cost associated with its support."
GROUP qBridgeVlanStatisticsOverflowGroup GROUP qBridgeVlanStatisticsOverflowGroup
DESCRIPTION DESCRIPTION
"This group is optional." "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."
GROUP qBridgeVlanHCStatisticsGroup GROUP qBridgeVlanHCStatisticsGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional as there may be significant
implementation cost associated with its support. It is most
relevant for high capacity interfaces."
GROUP qBridgeLearningConstraintsGroup GROUP qBridgeLearningConstraintsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices implementing "This group is mandatory for devices implementing
both Independent VLAN Learning (IVL) and Shared both Independent VLAN Learning (IVL) and Shared
VLAN Learning (SVL) modes of operation of the VLAN Learning (SVL) modes of operation of the
filtering database." filtering database, as defined by IEEE 802.1Q."
GROUP qBridgeLearningConstraintDefaultGroup GROUP qBridgeLearningConstraintDefaultGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices implementing "This group is mandatory for devices implementing
both Independent VLAN Learning (IVL) and Shared both Independent VLAN Learning (IVL) and Shared
VLAN Learning (SVL) modes of operation of the VLAN Learning (SVL) modes of operation of the
filtering database." filtering database, as defined by IEEE 802.1Q."
OBJECT dot1qPortAcceptableFrameTypes OBJECT dot1qPortAcceptableFrameTypes
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required as this is an optional
capability in IEEE 802.1Q."
OBJECT dot1qPortIngressFiltering OBJECT dot1qPortIngressFiltering
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required as this is an optional
capability in IEEE 802.1Q."
OBJECT dot1qConstraintSetDefault OBJECT dot1qConstraintSetDefault
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required as this is an optional
capability in IEEE 802.1Q."
OBJECT dot1qConstraintTypeDefault OBJECT dot1qConstraintTypeDefault
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required as this is an optional
capability in IEEE 802.1Q."
::= { qBridgeCompliances 1 } ::= { qBridgeCompliances 1 }
END END
7. Acknowledgments
This document expands upon previous work which resulted in RFC1493. 6. Acknowledgments
Much of the groundwork for this document was performed by the IEEE 802.1 This document expands upon previous work which resulted in the
working group during the definition of the IEEE 802.1D updates [19] and original bridge MIB [BRIDGEMIB].
IEEE 802.1Q [20].
The authors wish to thank the members of the Bridge Working Group for Much of the groundwork for this document was performed by the IEEE
their many comments and suggestions which improved this effort. 802.1 working group during the definition of the IEEE 802.1D updates
[802.1D] and IEEE 802.1Q [802.1Q].
8. References 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.
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 7. Security Considerations
Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998
[2] Rose, M., and K. McCloghrie, "Structure and Identification of There are a number of management objects defined in this MIB that
Management Information for TCP/IP-based Internets", RFC 1155, have a MAX-ACCESS clause of read-write and/or read-create. Such
Performance Systems International, Hughes LAN Systems, May 1990 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.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, SNMPv1 by itself is not a secure environment. Even if the network
Performance Systems International, Hughes LAN Systems, March 1991 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.
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", It is recommended that the implementers consider the security
RFC 1215, Performance Systems International, March 1991 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.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure It is then a customer/user responsibility to ensure that the SNMP
of Management Information for Version 2 of the Simple Network entity giving access to an instance of this MIB, is properly
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco configured to give access to the objects only to those principals
Systems, Inc., Dover Beach Consulting, Inc., International Network (users) that have legitimate rights to indeed GET or SET
Services, January 1996. (change/create/delete) them.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 8. References
Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance [ARCH]
Statements for Version 2 of the Simple Network Management Protocol Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
(SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., Describing SNMP Management Frameworks", RFC 2571, April 1999.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [V1PROTO]
Management Protocol", RFC 1157, SNMP Research, Performance Systems Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
International, Performance Systems International, MIT Laboratory Network Management Protocol", STD 15, RFC 1157, May 1990.
for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [V1SMI]
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, Rose, M. and K. McCloghrie, "Structure and Identification of
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., Management Information for TCP/IP-based Internets", STD 16, RFC
International Network Services, January 1996. 1155, May 1990.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [V1CONCISE]
Mappings for Version 2 of the Simple Network Management Protocol Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., RFC 1212, March 1991.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [V1TRAPS]
Processing and Dispatching for the Simple Network Management Rose, M., "A Convention for Defining Traps for use with the
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, SNMP", RFC 1215, March 1991.
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [V2SMI]
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
2274, IBM T. J. Watson Research, January 1998. M. and S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [V2TC]
Operations for Version 2 of the Simple Network Management Protocol McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
Dover Beach Consulting, Inc., International Network Services, RFC 2579, April 1999.
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [V2CONFORM]
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
Systems, January 1998 M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
58, RFC 2580, April 1999.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [V2COMMUNITY]
Control Model (VACM) for the Simple Network Management Protocol Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., "Introduction to Community-based SNMPv2", RFC 1901, January
Cisco Systems, Inc., January 1998 1996.
[16] Information processing systems - Open Systems Interconnection - [V2TRANS]
Specification of Abstract Syntax Notation One (ASN.1), Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
International Organization for Standardization, International Mappings for Version 2 of the Simple Network Management Protocol
Standard 8824, December 1987. (SNMPv2)", RFC 1906, January 1996.
[17] Information processing systems - Open Systems Interconnection - [V2PROTO]
Specification of Basic Encoding Rules for Abstract Notation One Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
(ASN.1), International Organization for Standardization, Operations for Version 2 of the Simple Network Management
International Standard 8825, December 1987. Protocol (SNMPv2)", RFC 1905, January 1996.
[18] ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges". [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.
[19] "Information technology - Telecommunications and information [V3MPC]
exchange between systems - Local and metropolitan area networks - Case, J., Harrington D., Presuhn, R. and B. Wijnen, "Message
Common specifications - Part 3: Media Access Control (MAC) Bridges: Processing and Dispatching for the Simple Network Management
Revision. This is a revision of ISO/IEC 10038: 1993, 802.1j-1992 Protocol (SNMP)", RFC 2572, April 1999.
and 802.6k-1992. It incorporates P802.11c, P802.1p and P802.12e."
ISO/IEC 15802-3: 1998.
[20] ANSI/IEEE Draft Standard P802.1Q/D11, "IEEE Standards for Local and [V3USM]
Metropolitan Area Networks: Virtual Bridged Local Area Networks", Blumenthal, U. and B. Wijnen, "The User-Based Security Model
July 1998. (USM) for Version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999.
[21] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K., [V3APPS]
"Definitions of Managed Objects for Bridges", RFC 1493, cisco Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC
Systems, Digital Equipment, Hughes LAN Systems, July 1993. 2573, April 1999.
[22] McCloghrie, K., Kastenholz, F. "Evolution of the Interfaces Group [V3VACM]
of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, January Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
1994. Control Model for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999.
[23] Decker, E., McCloghrie, K., Langille, P., Rijsinghani, A. [ASN1]
"Definitions of Managed Objects for Source Routing Bridges", RFC Information processing systems - Open Systems Interconnection -
1525, cisco Systems, Hughes LAN Systems, Digital Equipment, Specification of Abstract Syntax Notation One (ASN.1),
September 1993 International Organization for Standardization, International
Standard 8824, December 1987.
[24] McCloghrie K., and M. Rose, Editors, "Management Information Base [ASN1BER]
for Network Management of TCP/IP-based internets", STD 17, RFC Information processing systems - Open Systems Interconnection -
1213, Hughes LAN Systems, Performance Systems International, March Specification of Basic Encoding Rules for Abstract Notation One
1991. (ASN.1), International Organization for Standardization,
International Standard 8825, December 1987.
9. Security Considerations [802.1D-ORIG]
ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges".
There are a number of management objects defined in this MIB that have a [802.1D]
MAX-ACCESS clause of read-write and/or read-create. Such objects may be "Information technology - Telecommunications and information
considered sensitive or vulnerable in some network environments. The exchange between systems - Local and metropolitan area networks
support for SET operations in a non-secure environment without proper - Common specifications - Part 3: Media Access Control (MAC)
protection can have a negative effect on network operations. 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.
SNMPv1 by itself is not a secure environment. Even if the network [802.1Q]
itself is secure (for example by using IPSec), even then, there is no ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and
control as to who on the secure network is allowed to access and GET/SET Metropolitan Area Networks: Virtual Bridged Local Area
(read/change/create/delete) the objects in this MIB. Networks", 1998.
It is recommended that the implementers consider the security features [BRIDGEMIB]
as provided by the SNMPv3 framework. Specifically, the use of the User- Decker, E., Langille, P., Rijsinghani, A. and K. McCloghrie,
based Security Model RFC 2274 [12] and the View-based Access Control "Definitions of Managed Objects for Bridges", RFC 1493, July
Model RFC 2275 [15] is recommended. 1993.
It is then a customer/user responsibility to ensure that the SNMP entity [INTERFACEMIB]
giving access to an instance of this MIB, is properly configured to give McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB
access to the objects only to those principals (users) that have using SMIv2", RFC 2233, November 1997.
legitimate rights to indeed GET or SET (change/create/delete) them.
10. Authors' Addresses [SRBRIDGEMIB]
Decker, E., McCloghrie, K., Langille, P. and A. Rijsinghani,
"Definitions of Managed Objects for Source Routing Bridges", RFC
1525, September 1993.
Les Bell [MIB2]
3Com Europe Limited McCloghrie K. and M. Rose, Editors, "Management Information Base
3Com Centre, Boundary Way for Network Management of TCP/IP-based internets", STD 17, RFC
Hemel Hempstead 1213, March 1991.
Herts. HP2 7YU
UK
+44 (1442) 438025
Les_Bell@3Com.com
Andrew Smith 9. Authors' Addresses
Extreme Networks
10460 Bandley Drive
Cupertino CA 95014
USA
+1 (408) 342 0999
andrew@extremenetworks.com
Paul Langille Les Bell
Newbridge Networks 3Com Europe Limited
5 Corporate Drive 3Com Centre, Boundary Way
Andover, MA 01810 Hemel Hempstead
USA Herts. HP2 7YU
+1 (978) 691 4665 UK
langille@newbridge.com
Anil Rijhsinghani Phone: +44 1442 438025
Cabletron Systems EMail: Les_Bell@3Com.com
50 Minuteman Road
Andover MA 01810
USA
+1 (978) 684-1295
anil@cabletron.com
Keith McCloghrie Andrew Smith
cisco Systems, Inc. Extreme Networks
170 West Tasman Drive 3585 Monroe St.
San Jose, CA 95134-1706 Santa Clara, CA 95051
USA USA
+1 (408) 526 5260
kzm@cisco.com
Table of Contents Phone: +1 408 579 2821
EMail: andrew@extremenetworks.com
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
Phone: +1 978 684 1295
EMail: anil@cabletron.com
Keith McCloghrie
cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
Phone: +1 408 526 5260
EMail: kzm@cisco.com
10. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. 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.
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.
11. Full Copyright Statement
1 The SNMP Management Framework ................................... 2
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 .............. 7
3.1.3 The dot1dExtBase Group ...................................... 8
3.1.4 The dot1dPriority Group ..................................... 8
3.1.5 The dot1dGarp Group ......................................... 8
3.1.6 The dot1dGmrp Group ......................................... 8
3.1.7 The dot1dHCPortTable ........................................ 8
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 ......................................... 12
3.2.3 The dot1qTp Group ........................................... 12
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 .................................... 13
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 .............................................. 15
3.4.2.3 ifRcvAddressTable ......................................... 16
3.4.3 Relation to Basic Bridge MIB ................................ 16
3.4.3.1 The dot1dBase Group ....................................... 16
3.4.3.2 The dot1dStp Group ........................................ 16
3.4.3.3 The dot1dTp Group ......................................... 17
3.4.3.4 The dot1dStatic Group ..................................... 17
4 Extensions to RFC 1493 .......................................... 18
5 Definitions for Extended Bridge MIB ............................. 19
6 Definitions for Virtual Bridge MIB .............................. 40
7 Acknowledgments ................................................. 81
8 References ...................................................... 81
9 Security Considerations ......................................... 84
10 Authors' Addresses ............................................. 85
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished to
to others, and derivative works that comment on or otherwise others, and derivative works that comment on or otherwise explain it
explain it or assist in its implmentation may be prepared, copied, or assist in its implementation may be prepared, copied, published
published and distributed, in whole or in part, without and distributed, in whole or in part, without restriction of any
restriction of any kind, provided that the above copyright notice kind, provided that the above copyright notice and this paragraph are
and this paragraph are included on all such copies and derivative included on all such copies and derivative works. However, this
works. However, this document itself may not be modified in any document itself may not be modified in any way, such as by removing
way, such as by removing the copyright notice or references to the the copyright notice or references to the Internet Society or other
Internet Society or other Internet organizations, except as needed Internet organizations, except as needed for the purpose of
for the purpose of developing Internet standards in which case the developing Internet standards in which case the procedures for
procedures for copyrights defined in the Internet Standards copyrights defined in the Internet Standards process must be
process must be followed, or as required to translate it into followed, or as required to translate it into languages other than
languages other than English. English.
The limited permissions granted above are perpetual and will not The limited permissions granted above are perpetual and will not be
be revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on This document and the information contained herein is provided on an
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 222 change blocks. 
835 lines changed or deleted 998 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/