draft-ietf-bridge-bridgemib-01.txt   draft-ietf-bridge-bridgemib-02.txt 
Internet Draft E.L. Bell Internet Draft E.L. Bell
Expires February 1999 3Com Corp. Expires April 1999 3Com Corp.
draft-ietf-bridge-bridgemib-01.txt A. Smith draft-ietf-bridge-bridgemib-02.txt A. Smith
Standards Track Extreme Networks Standards Track Extreme Networks
P. Langille P. Langille
Acacia Networks Acacia Networks
A. Rijhsinghani A. Rijhsinghani
Cabletron Systems Cabletron Systems
K. McCloghrie K. McCloghrie
cisco Systems cisco Systems
August 1998 October 1998
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. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, documents of the Internet Engineering Task Force (IETF), its Areas, and
and its Working Groups. Note that other groups may also distribute its Working Groups. Note that other groups may also distribute working
working documents as Internet Drafts. documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six Internet Drafts are draft documents valid for a maximum of six months.
months. Internet Drafts may be updated, replaced, or obsoleted by Internet Drafts may be updated, replaced, or obsoleted by other
other documents at any time. It is not appropriate to use Internet documents at any time. It is not appropriate to use Internet Drafts as
Drafts as reference material or to cite them other than as a "working reference material or to cite them other than as a "working draft" or
draft" or "work in progress." "work in progress."
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe),
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
Rim).
This document is a product of the IETF's Bridge MIB Working Group. This document is a product of the IETF's Bridge MIB Working Group.
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB) for
for use with network management protocols in TCP/IP based internets. use with network management protocols in TCP/IP based internets. In
In particular it defines objects for managing MAC bridges based on particular it defines objects for managing MAC bridges based on the IEEE
the IEEE 802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN 802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN (VLAN)
(VLAN) standards for bridging between Local Area Network (LAN) standards for bridging between Local Area Network (LAN) segments.
segments. Provisions are made for support of transparent bridging. Provisions are made for support of transparent bridging. Provisions are
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
SNMPv2 SMI [18].
1. The SNMP Network Management Framework 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 SNMPv2 SMI [5].
The SNMP Network Management Framework consists of several major 1. The SNMP Management Framework
components. They are:
o RFC 1902 [18] which defines the SMI, the mechanisms used for The SNMP Management Framework presently consists of five major
describing and naming objects for the purpose of management. components:
This supercedes an earlier definition of SMI in RFC 1155 [3].
o STD 17, RFC 1213 [5] defines MIB-II, the core set of managed o An overall architecture, described in RFC 2271 [1].
objects for the Internet suite of protocols.
o RFC 1157 [4] and RFC 1905 [17] which define two versions of o Mechanisms for describing and naming objects and events for the
protocols providing network access to managed objects. purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second
version, called SMIv2, is described in RFC 1902 [5], RFC 1903
[6] and RFC 1904 [7].
Textual conventions are defined in RFC 1903 [19] and conformance o Message protocols for transferring management information. The
statements are defined in RFC 1904 [20]. first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
The Framework permits new objects to be defined for the purpose of o Protocol operations for accessing management information. The
experimentation and evaluation. first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations
and associated PDU formats is described in RFC 1905 [13].
This memo specifies MIB modules that are compliant to the SNMPv2 SMI o A set of fundamental applications described in RFC 2273 [14] and
[18]. the view-based access control mechanism described in RFC 2275
[15].
1.1. Object Definitions Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined
using the mechanisms defined in the SMI.
Managed objects are accessed via a virtual information store, termed This memo specifies a MIB module that is compliant to the SMIv2. A MIB
the Management Information Base or MIB. Objects in the MIB are conforming to the SMIv1 can be produced through the appropriate
defined using the subset of Abstract Syntax Notation One (ASN.1) translations. The resulting translated MIB must be semantically
defined in the SMI. In particular, each object object type is named
by an OBJECT IDENTIFIER, an administratively assigned name. The equivalent, except where objects or events are omitted because no
object type together with an object instance serves to uniquely translation is possible (use of Counter64). Some machine readable
identify a specific instantiation of the object. For human information in SMIv2 will be converted into textual descriptions in
convenience, we often use a textual string, termed the descriptor, to SMIv1 during the translation process. However, this loss of machine
refer to the object type. readable information is not considered to change the semantics of the
MIB.
2. Overview 2. Overview
A common device present in many networks is the Bridge. This device A common device present in many networks is the Bridge. This device is
is used to connect Local Area Network segments below the network used to connect Local Area Network segments below the network layer.
layer. These devices are often known as 'layer 2 switches'. 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; transparent and
source route. The transparent method of bridging is defined by IEEE source route. The transparent method of bridging is defined by IEEE
802.1D-1998 [11]. Managed objects for source route bridges are 802.1D-1998 [19]. Managed objects for source route bridges are defined
defined in [15]. in [23].
IEEE 802.1D is augmented by IEEE 802.1Q-1998 [12] to provide support IEEE 802.1D is augmented by IEEE 802.1Q-1998 [20] to provide support for
for 'virtual bridged LANs' where a single bridged physical LAN 'virtual bridged LANs' where a single bridged physical LAN network may
network may be used to support multiple logical bridged LANs, each of be used to support multiple logical bridged LANs, each of which offers a
which offers a service approximately the same as that defined by service approximately the same as that defined by 802.1D. Such virtual
802.1D. Such virtual LANs (VLANs) are an integral feature of LANs (VLANs) are an integral feature of switched LAN networks. A VLAN
switched LAN networks. A VLAN can be viewed as a group of end- can be viewed as a group of end-stations on multiple LAN segments and
stations on multiple LAN segments and can communicate as if they were can communicate as if they were on a single LAN. IEEE 802.1Q defines
on a single LAN. IEEE 802.1Q defines port-based Virtual LANs where port-based Virtual LANs where membership is determined by the bridge
membership is determined by the bridge port on which data frames are port on which data frames are received. This memo defines the objects
received. This memo defines the objects needed for the management of needed for the management of port-based VLANs in bridge entities.
port-based VLANs in bridge entities.
This memo defines those objects needed for the management of a This memo defines those objects needed for the management of a bridging
bridging entity operating in the transparent mode, as well as some entity operating in the transparent mode, as well as some objects
objects applicable to all types of bridges. Managed objects for applicable to all types of bridges. Managed objects for Source-Routing
Source-Routing are defined in [15]. are defined in [23].
2.1. Scope 2.1. Scope
This MIB includes a comprehensive set of managed objects which This MIB includes a comprehensive set of managed objects which attempts
attempts to match the set defined in IEEE 802.1D and IEEE 802.1Q. to match the set defined in IEEE 802.1D and IEEE 802.1Q. However, to be
However, to be consistent with the spirit of the SNMP Framework, a consistent with the spirit of the SNMP Framework, a subjective judgement
subjective judgement was made to omit the objects from those was made to omit the objects from those standards most 'costly' to
standards most 'costly' to implement in an agent and least implement in an agent and least 'essential' for fault and configuration
'essential' for fault and configuration management. The omissions management. The omissions are described in section 3 below.
are described in section 3 below.
Historical note: Historical note:
RFC 1493 used the following principles for determining inclusion of RFC 1493 used the following principles for determining inclusion of an
an object in the BRIDGE-MIB module: 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
further objects are needed. 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 (5) Exclude objects which are simply derivable from others in this or
or other MIBs. other MIBs.
(6) Avoid causing critical sections to be heavily instrumented. The (6) Avoid causing critical sections to be heavily instrumented. The
guideline that was followed is one counter per critical section guideline that was followed is one counter per critical section per
per layer. 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 base BRIDGE-MIB module defined in RFC1493: that MIB module is
maintained unchanged for backwards compatibility. Section 3.4.3 of maintained unchanged for backwards compatibility. Section 3.4.3 of the
the present document contains some recommendations regarding usage of present document contains some recommendations regarding usage of
objects in RFC1493 by devices implementing the enhancements defined objects in RFC1493 by devices implementing the enhancements defined
here. 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
for the traffic class and multicast filtering enhancements the traffic class and multicast filtering enhancements defined by
defined by IEEE 802.1D-1998. IEEE 802.1D-1998.
(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 for
the Virtual LAN bridging enhancements defined by IEEE 802.1Q- the Virtual LAN bridging enhancements defined by IEEE 802.1Q-1998.
1998.
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 Objects in this MIB are arranged into groups. Each group is organized
organized as a set of related objects. The overall structure and as a set of related objects. The overall structure and assignment of
assignment of objects to their groups is shown below. 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 This section contains a cross-reference to the objects defined in IEEE
IEEE 802.1D-1998 [11]. It also details those objects that are not 802.1D-1998 [19]. It also details those objects that are not considered
considered necessary in this MIB module. necessary in this MIB module.
Some objects defined by [11] have been included in the virtual bridge Some objects defined by [19] have been included in the virtual bridge
MIB module rather than this one: entries in dot1qTpGroupTable, MIB module rather than this one: entries in dot1qTpGroupTable,
dot1qForwardAllTable and dot1qForwardUnregisteredTable are required dot1qForwardAllTable and dot1qForwardUnregisteredTable are required for
for virtual bridged LANs with additional indexing (e.g. per-VLAN, virtual bridged LANs with additional indexing (e.g. per-VLAN, per-FDB)
per-FDB) and so are not defined here. Instead, devices which do not and so are not defined here. Instead, devices which do not implement
implement virtual bridged LANs, should implement these tables with a virtual bridged LANs, should implement these tables with a fixed value
fixed value for dot1qFdbId (the value 1 is recommended) or for dot1qFdbId (the value 1 is recommended) or dot1qVlanIndex (the value
dot1qVlanIndex (the value 1 is recommended). Devices which support 1 is recommended). Devices which support Extended Filtering Services
Extended Filtering Services (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 support dot1qTpGroupTable, dot1qForwardAllTable and dot1qTpGroupTable, dot1qForwardAllTable and
dot1qForwardUnregisteredTable. dot1qForwardUnregisteredTable.
Extended Bridge MIB Name IEEE 802.1D Name Extended Bridge MIB Name IEEE 802.1D Name
dot1dExtended Bridge dot1dExtended Bridge
dot1dExtBase dot1dExtBase
dot1dDeviceCapabilities dot1dDeviceCapabilities
dot1dExtendedFilteringServices
dot1dTrafficClasses
dot1dTrafficClassesEnabled dot1dTrafficClassesEnabled
dot1dGmrpStatus dot1dGmrpStatus .ApplicantAdministrativeControl
.ApplicantAdministrativeControl
dot1dPortCapabilitiesTable
dot1dPortCapabilities
dot1dPriority dot1dPriority
dot1dPortPriorityTable dot1dPortPriorityTable
dot1dPortDefaultUserPriority .UserPriority dot1dPortDefaultUserPriority .UserPriority
dot1dPortNumTrafficClasses dot1dPortNumTrafficClasses
dot1dUserPriorityRegenTable .UserPriorityRegenerationTable dot1dUserPriorityRegenTable .UserPriorityRegenerationTable
dot1dUserPriority dot1dUserPriority
dot1dRegenUserPriority dot1dRegenUserPriority
dot1dTrafficClassTable .TrafficClassTable dot1dTrafficClassTable .TrafficClassTable
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 dot1dPortGmrpStatus .ApplicantAdministrativeControl
.ApplicantAdministrativeControl
dot1dPortGmrpFailedRegistrations dot1dPortGmrpFailedRegistrations
.FailedRegistrations .FailedRegistrations
dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU
dot1dTpGroup
dot1dTpHCPortTable
dot1dTpHCPortInFrames .BridgePort.FramesReceived
dot1dTpHCPortOutFrames .ForwardOutBound
dot1dTpHCPortInDiscards .DiscardInbound
The following IEEE 802.1D management objects have not been included The following IEEE 802.1D management objects have not been included in
in the Bridge MIB for the indicated reasons. the Bridge MIB for the indicated reasons.
IEEE 802.1D Object Disposition IEEE 802.1D 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 Only per-{device,port,application}
per-{device,port,application}
control is provided in this MIB. control is provided in this MIB.
3.1.2. The dot1dExtBase Group 3.1.2. Relationship to IEEE 802.1Q Manageable Objects
This section contains a cross-reference to the objects defined in IEEE
802.1Q-1998 [20]. These objects have been included in this MIB as they
provide a natural fit with the 802.1D objects they are located with.
Extended Bridge MIB Name IEEE 802.1Q Name
dot1dExtended Bridge
dot1dExtBase
dot1dDeviceCapabilities
dot1qStaticEntryIndividualPort 5.2 implementation options
dot1qIVLCapable
dot1qSVLCapable
dot1qHybridCapable
dot1qConfigurablePvidTagging 12.10.1.1 read bridge vlan
config
dot1dPortCapabilitiesTable
dot1dPortCapabilities
dot1qDot1qTagging 5.2 implementation options
dot1qConfigurableAcceptableFrameTypes
5.2 implementation options
dot1qIngressFiltering 5.2 implementation options
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 802.1D. It includes per-device configuration of GARP and GMRP
protocols. This group will be implemented by all devices which protocols. This group will be implemented by all devices which
implement the extensions defined in 802.1D-1998. implement the extensions defined in 802.1D-1998.
3.1.3. The dot1dPriority Group 3.1.4. The dot1dPriority Group
This group contains the objects for configuring and reporting status This group contains the objects for configuring and reporting status of
of priority-based queuing mechanisms in a bridge. This includes per- priority-based queuing mechanisms in a bridge. This includes per- port
port user_priority treatment, mapping of user_priority in frames into user_priority treatment, mapping of user_priority in frames into
internal traffic classes and outbound user_priority and internal traffic classes and outbound user_priority and access_priority.
access_priority.
3.1.4. 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.5. 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.6. The dot1dHCPort Group 3.1.7. The dot1dHCPortTable
This group contains the objects for reporting port bridging This table extends the dot1dTp group from RFC1493 and contains the
statistics for high-capacity network interfaces. objects for reporting port bridging statistics for high-capacity network
interfaces.
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 Objects in this MIB are arranged into groups. Each group is organized
organized as a set of related objects. The overall structure and as a set of related objects. The overall structure and assignment of
assignment of objects to their groups is shown below. Some of the objects to their groups is shown below. Some of the original objects
original objects from RFC1493 need to be indexed differently when from RFC1493 need to be indexed differently when extended in a VLAN
extended in a VLAN environment so some objects in that module environment so some objects in that module effectively duplicate new
effectively duplicate new objects defined here: this is necessary for objects defined here: this is necessary for backwards compatibility.
backwards compatibility.
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 This section contains a cross-reference to the objects defined in [20].
[12]. It also details those objects that are not considered It also details those objects that are not considered necessary in this
necessary in this MIB module. MIB module.
Note: unlike IEEE 802.1D, [12] chose not to define a new set of Note: unlike IEEE 802.1D, [20] chose not to define a new set of managed
managed object names so those following are referenced from the object names so those following are referenced from the descriptions of
descriptions of management operations with section numbering from management operations with section numbering from clause 12 in that
clause 12 in that document. document.
Virtual Bridge MIB object 802.1Q object Virtual Bridge MIB object 802.1Q object
dot1dDeviceCapabilities
dot1qStaticEntryIndividualPort 5.2 implementation options
dot1qIVLCapable
dot1qSVLCapable
dot1qHybridCapable
dot1dPortCapabilities
dot1qConfigurablePvidTagging 12.10.1.1 read bridge vlan
config
dot1qDot1qTagging 5.2 implementation options
dot1qConfigurableAcceptableFrameTypes 5.2 implementation options
dot1qPortIngressFiltering 5.2 implementation options
dot1qBase dot1qBase
dot1qVlanVersionNumber 12.10.1.1 read bridge vlan dot1qVlanVersionNumber 12.10.1.1 read bridge vlan config
config dot1qMaxVlanId 12.10.1.1 read bridge vlan config
dot1qMaxVlanId 12.10.1.1 read bridge vlan dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan config
config
dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan
config
dot1qNumVlans dot1qNumVlans
dot1dGvrpStatus 12.9.2.1/2 read/set garp dot1dGvrpStatus 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
dot1qTpGroupAllowedToGoTo dot1qTpGroupEgressPorts
dot1qTpGroupLearnt dot1qTpGroupLearnt
dot1qForwardAllTable 12.7.7.1 read filtering entry dot1qForwardAllTable 12.7.7.1 read filtering entry
dot1qForwardAllPorts dot1qForwardAllPorts
dot1qForwardAllStaticPorts dot1qForwardAllStaticPorts
dot1qForwardUnregisteredTable 12.7.7.1 read filtering entry dot1qForwardUnregisteredTable 12.7.7.1 read filtering entry
dot1qForwardUnregisteredPorts dot1qForwardUnregisteredPorts
dot1qForwardUnregisteredStaticPorts dot1qForwardUnregisteredStaticPorts
dot1qStatic dot1qStatic
dot1qStaticUnicastTable 12.7.7.1 create/delete/read dot1qStaticUnicastTable 12.7.7.1 create/delete/read
filtering entry filtering entry
skipping to change at page 9, line 13 skipping to change at page 10, line 25
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 dot1qVlanCurrentTable 12.10.2.1 read vlan configuration
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 allocation 12.10.3.6 read FID allocated to VID
for
VID
12.10.3.7 read VIDs allocated to 12.10.3.7 read VIDs allocated to
FID FID
dot1qVlanTimeMark dot1qVlanTimeMark
dot1qVlanIndex dot1qVlanIndex
dot1qVlanFdbId dot1qVlanFdbId
dot1qVlanCurrentEgressPorts dot1qVlanCurrentEgressPorts
dot1qVlanCurrentUntaggedPorts dot1qVlanCurrentUntaggedPorts
dot1qVlanStatus dot1qVlanStatus
dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read
filtering entry filtering entry
12.7.6.1 read permanent database 12.7.6.1 read permanent database
12.10.2.2 create vlan config 12.10.2.2 create vlan config
12.10.2.3 delete vlan config 12.10.2.3 delete vlan config
dot1qVlanStaticName 12.4.1.3 set bridge name dot1qVlanStaticName 12.4.1.3 set bridge name
dot1qVlanStaticEgressPorts dot1qVlanStaticEgressPorts
dot1qVlanForbiddenEgressPorts dot1qVlanForbiddenEgressPorts
dot1qVlanStaticUntagged dot1qVlanStaticUntaggedPorts
dot1qVlanStaticRowStatus dot1qVlanStaticRowStatus
dot1qPortVlanConfigTable 12.10.1.1 read bridge vlan dot1qPortVlanConfigTable 12.10.1.1 read bridge vlan
configuration configuration
dot1qPvid 12.10.1.2 configure PVID values dot1qPvid 12.10.1.2 configure PVID values
dot1qPortAcceptableFrameTypes 12.10.1.3 configure acceptable dot1qPortAcceptableFrameTypes 12.10.1.3 configure acceptable
frame types parameter frame types parameter
dot1qPortIngressFiltering 12.10.1.4 configure ingress dot1qPortIngressFiltering 12.10.1.4 configure ingress
filtering parameters filtering parameters
dot1qPortGvrpStatus 12.9.2.2 read/set garp applicant dot1qPortGvrpStatus 12.9.2.2 read/set garp applicant
controls controls
dot1qPortGvrpFailedRegistrations dot1qPortGvrpFailedRegistrations
dot1qPortGvrpLastPduOrigin dot1qPortGvrpLastPduOrigin
dot1qPortVlanStatisticsTable 12.6.1.1 read forwarding port dot1qPortVlanStatisticsTable 12.6.1.1 read forwarding port
counters counters
dot1qFramesReceived dot1qTpVlanPortInFrames
dot1qOctetsReceived (optional) dot1qTpVlanPortOutFrames
dot1qForwardOutbound dot1qTpVlanPortInDiscards
dot1qDiscardInbound
dot1qDiscardNoBuffers
dot1qDiscardTransitDelayExceeded
dot1qDiscardError
dot1qDiscardOnIngressFiltering (optional)
dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port
counters counters
dot1qHCFramesReceived dot1qTpVlanPortHCInFrames
dot1qHCOctetsReceived (optional) dot1qTpVlanPortHCOutFrames
dot1qHCForwardOutbound dot1qTpVlanPortHCInDiscards
dot1qHCDiscardInbound
dot1qHCDiscardNoBuffers
dot1qHCDiscardTransitDelayExceeded
dot1qHCDiscardError
dot1qHCDiscardOnIngressFiltering (optional)
dot1qLearningConstraintsLastChange
dot1qLearningConstraintsTable 12.10.3.1/3/4 read/set/delete dot1qLearningConstraintsTable 12.10.3.1/3/4 read/set/delete
vlan learning vlan learning constraints
constraints
12.10.3.2 read vlan learning 12.10.3.2 read vlan learning
constraints for VID constraints for VID
dot1qConstraintVlan dot1qConstraintVlan
dot1qConstraintSet dot1qConstraintSet
dot1qConstraintType dot1qConstraintType
dot1qConstraintStatus dot1qConstraintStatus
dot1qConstraintSetDefault dot1qConstraintSetDefault
dot1qConstraintTypeDefault dot1qConstraintTypeDefault
The following IEEE 802.1Q management objects have not been included The following IEEE 802.1Q management objects have not been included in
in the Bridge MIB for the indicated reasons. the Bridge MIB for the indicated reasons.
IEEE 802.1Q Object Disposition IEEE 802.1Q Object Disposition
reset bridge (12.4.1.4) not considered useful[Issue reset bridge (12.4.1.4) not considered useful
46]
reset vlan bridge (12.10.1.5) not considered useful[Issue reset vlan bridge (12.10.1.5) not considered useful
38]
read forwarding port counters (12.6.1.1) read forwarding port counters (12.6.1.1)
discard on error details not considered useful discard on error details not considered useful
read permanent database (12.7.6.1) read permanent database (12.7.6.1)
permanent database size not considered useful permanent database size not considered useful
number of static filtering entries number of static filtering count rows in
count rows in dot1qStaticTable entries dot1qStaticUnicastTable +
dot1qStaticMulticastTable
number of static VLAN count rows in number of static VLAN count rows in
registration entries dot1qVlanStaticTable registration entries dot1qVlanStaticTable
read filtering entry range use GetNext operation. read filtering entry range use GetNext operation.
(12.7.7.4) (12.7.7.4)
read filtering database (12.7.1.1) read filtering database (12.7.1.1)
filtering database size not considered useful filtering database size not considered useful
number of dynamic group address count rows applicable to each
entries (12.7.1.3) FDB in dot1dTpGroupTable
read garp state (12.9.3.1) not considered useful read garp state (12.9.3.1) not considered useful
notify vlan registration failure not considered useful notify vlan registration failure not considered useful
(12.10.1.6) (12.10.1.6)
notify learning constraint violation notify learning constraint violation
(12.10.3.10) not considered useful (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 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 status of transparent bridging. This includes management of the dynamic
dynamic Filtering Databases for both unicast and multicast Filtering Databases for both unicast and multicast forwarding. This
forwarding. This group will be implemented by all bridges that group will be implemented by all bridges that perform destination-
perform destination-address filtering. 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 information for transparent bridging. This includes management of the
the static entries in the Filtering Databases for both unicast and static entries in the Filtering Databases for both unicast and multicast
multicast forwarding. forwarding.
3.2.5. The dot1qVlan Group 3.2.5. The dot1qVlan Group
This group contains objects that control configuration and report This group contains objects that control configuration and report status
status of the Virtual LANs known to a bridge. This includes of the Virtual LANs known to a bridge. This includes management of the
management of the statically configured VLANs as well as reporting statically configured VLANs as well as reporting VLANs discovered by
VLANs discovered by other means e.g. GVRP. It also controls other means e.g. GVRP. It also controls configuration and reports
configuration and reports status of per-port objects relating to status of per-port objects relating to VLANs and reports traffic
VLANs and reports traffic statistics. It also provides for statistics. It also provides for management of the VLAN Learning
management of the VLAN Learning Constraints. 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 VlanIndex and VlanId are used as textual conventions in this document.
document. These textual conventions have NO effect on either the These textual conventions have NO effect on either the syntax nor the
syntax nor the semantics of any managed object. Objects defined semantics of any managed object. Objects defined using these
using these conventions are always encoded by means of the rules that conventions are always encoded by means of the rules that define their
define their primitive type. Hence, no changes to the SMI or the primitive type. Hence, no changes to the SMI or the SNMP are necessary
SNMP are necessary to accommodate these textual conventions which are to accommodate these textual conventions which are adopted merely for
adopted merely for the convenience of readers. 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 [6], the 'interfaces' least) the 'system' group defined in MIB-II [24], the 'interfaces' group
group defined [14] and the old Bridge MIB [13]. defined in [22] and the old Bridge MIB [21].
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 object in the 'system' group. Thus, those objects apply to the entity
entity as a whole irrespective of whether the entity's sole as a whole irrespective of whether the entity's sole functionality is
functionality is bridging, or whether bridging is only a subset of bridging, or whether bridging is only a subset of the entity's
the entity's functionality. functionality.
3.4.2. Relation to Interfaces MIB 3.4.2. Relation to Interfaces MIB
RFC 1573, the Interface MIB Evolution [14], requires that any MIB RFC 1573, the Interface MIB Evolution [22], requires that any MIB which
which is an adjunct of the Interface MIB, clarify specific areas is an adjunct of the Interface MIB, clarify specific areas within the
within the Interface MIB. These areas were intentionally left vague Interface MIB. These areas were intentionally left vague in [22] to
in [14] to avoid over constraining the MIB, thereby precluding avoid over constraining the MIB, thereby precluding management of
management of certain media-types. certain media-types.
Section 3.3 of [14] enumerates several areas which a media-specific Section 3.3 of [22] enumerates several areas which a media-specific MIB
MIB must clarify. Each of these areas is addressed in a following must clarify. Each of these areas is addressed in a following
subsection. The implementor is referred to [14] in order to subsection. The implementor is referred to [22] in order to understand
understand the general intent of these areas. the general intent of these areas.
In [14], the 'interfaces' group is defined as being mandatory for all In [22], the 'interfaces' group is defined as being mandatory for all
systems and contains information on an entity's interfaces, where systems and contains information on an entity's interfaces, where each
each interface is thought of as being attached to a `subnetwork'. interface is thought of as being attached to a `subnetwork'. (Note that
(Note that this term is not to be confused with `subnet' which refers this term is not to be confused with `subnet' which refers to an
to an addressing partitioning scheme used in the Internet suite of addressing partitioning scheme used in the Internet suite of protocols.)
protocols.) The term 'segment' is used in this memo to refer to such The term 'segment' is used in this memo to refer to such a subnetwork,
a subnetwork, whether it be an Ethernet segment, a 'ring', a WAN whether it be an Ethernet segment, a 'ring', a WAN link, or even an X.25
link, or even an X.25 virtual circuit. virtual circuit.
Implicit in this Bridge MIB is the notion of ports on a bridge. Each Implicit in this Bridge MIB is the notion of ports on a bridge. Each of
of these ports is associated with one interface of the 'interfaces' these ports is associated with one interface of the 'interfaces' group
group (one row in ifTable) and, in most situations, each port is (one row in ifTable) and, in most situations, each port is associated
associated with a different interface. However, there are situations with a different interface. However, there are situations in which
in which multiple ports are associated with the same interface. An multiple ports are associated with the same interface. An example of
example of such a situation would be several ports each corresponding such a situation would be several ports each corresponding one-to-one
one-to-one with several X.25 virtual circuits but all on the same with several X.25 virtual circuits but all on the same interface.
interface.
Each port is uniquely identified by a port number. A port number has Each port is uniquely identified by a port number. A port number has no
no mandatory relationship to an interface number, but in the simple mandatory relationship to an interface number, but in the simple case a
case a port number will have the same value as the corresponding port number will have the same value as the corresponding interface's
interface's interface number. Port numbers are in the range interface number. Port numbers are in the range (1..dot1dBaseNumPorts).
(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 situations, only a subset of the data sent/received on an interface is
is within the domain of the entity's bridging functionality. This within the domain of the entity's bridging functionality. This subset
subset is considered to be delineated according to a set of is considered to be delineated according to a set of protocols, with
protocols, with some protocols being bridged, and other protocols not some protocols being bridged, and other protocols not being bridged.
being bridged. For example, in an entity which exclusively performed For example, in an entity which exclusively performed bridging, all
bridging, all protocols would be considered as being bridged, whereas protocols would be considered as being bridged, whereas in an entity
in an entity which performed IP routing on IP datagrams and only which performed IP routing on IP datagrams and only bridged other
bridged other protocols, only the non-IP data would be considered as protocols, only the non-IP data would be considered as being bridged.
being bridged. Thus, this Bridge MIB (and in particular, its
counters) is applicable only to that subset of the data on an Thus, this Bridge MIB (and in particular, its counters) is applicable
entity's interfaces which is sent/received for a protocol being only to that subset of the data on an entity's interfaces which is
bridged. All such data is sent/received via the ports of the bridge. sent/received for a protocol being 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 [14] which states that the interfaces table (ifTable) accordance with [22] which states that the interfaces table (ifTable)
contains information on the managed resource's interfaces and that contains information on the managed resource's interfaces and that each
each sub-layer below the internetwork layer of a network interface is sub-layer below the internetwork layer of a network interface is
considered an interface. considered an interface.
This memo recommends that, within an entity, VLANs which are This memo recommends that, within an entity, VLANs which are
instantiated as an entry in dot1qVlanCurrentTable by either instantiated as an entry in dot1qVlanCurrentTable by either management
management configuration through dot1qVlanStaticTable or by dynamic configuration through dot1qVlanStaticTable or by dynamic means (e.g.
means (e.g. through GVRP), are NOT also represented by an entry in through GVRP), are NOT also represented by an entry in ifTable.
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).
3.4.2.2. ifStackTable 3.4.2.2. ifStackTable
In addition, [14] defines a table 'ifStackTable' for describing the In addition, [22] defines a table 'ifStackTable' for describing the
relationship between logical interfaces within an entity. It is relationship between logical interfaces within an entity. It is
anticipated that implementors will use this table to describe the anticipated that implementors will use this table to describe the
binding of e.g. IP interfaces to physical ports, although the binding of e.g. IP interfaces to physical ports, although the presence
presence of VLANs makes the representation less than perfect for of VLANs makes the representation less than perfect for showing
showing connectivity: the ifStackTable cannot represent the full connectivity: the ifStackTable cannot represent the full capability of
capability of the 802.1Q VLAN bridging standard since that makes a the 802.1Q VLAN bridging standard since that makes a distinction between
distinction between VLAN bindings on 'ingress' to and 'egress' from a VLAN bindings on 'ingress' to and 'egress' from a port: these
port: these relationships may or may not be symmetrical whereas [14] relationships may or may not be symmetrical whereas [22] assumes a
assumes a symmetrical binding for transmit and receive. This makes symmetrical binding for transmit and receive. This makes it necessary
it necessary to define other manageable objects for configuring which to define other manageable objects for configuring which ports are
ports are members of which VLANs. 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 broadcast, for which an interface will receive packets and forward them
them up to a higher layer entity for local consumption. Note that
this does not include addresses for data-link layer control protocols up to a higher layer entity for local consumption. Note that this does
such as Spanning-Tree, GMRP or GVRP. The format of the address, not include addresses for data-link layer control protocols such as
contained in ifRcvAddressAddress, is the same as for ifPhysAddress. Spanning-Tree, GMRP or GVRP. The format of the address, 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 explicitly not intended to provide a bridge address filtering mechanism.
mechanism.
3.4.3. Relation to Basic Bridge MIB 3.4.3. Relation to Basic Bridge MIB
This section defines how objects in the basic bridge MIB module This section defines how objects in the basic bridge MIB module should
should be represented for devices which implement the extensions: be represented for devices which implement the extensions: some of the
some of the old objects are less useful in such devices but must old objects are less useful in such devices but must still be
still be implemented for reasons of backwards comaptibility. Note implemented for reasons of backwards comaptibility. Note that formal
that formal conformance statements for that MIB module do not exist conformance statements for that MIB module do not exist since it is
since it is defined in SMIv1. 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 respect to the Spanning Tree Protocol. Interpretation of this group is
is unchanged. 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, In a device operating with a single Filtering Database, interpretation
interpretation of this group is unchanged. 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 been learnt in multiple databases on a single port, report it only
only once. If an address has been learnt in multiple databases once. If an address has been learnt in multiple databases on more
on more than one port, report the entry on any one of the valid than one port, report the entry on any one of the valid ports.
ports.
dot1dTpPortTable dot1dTpPortTable
This table is port-based and is not affected by multiple This table is port-based and is not affected by multiple Filtering
Filtering Databases or multiple VLANs. The counters should Databases or multiple VLANs. The counters should include frames
include frames received or transmitted for all VLANs. Note received or transmitted for all VLANs. Note that equivalent 64-bit
that equivalent 64-bit port statistics counters are defined in port statistics counters are defined in this document for high-
this document for high-capacity network interfaces with capacity network interfaces with conformance statements to indicate
conformance statements to indicate for which speeds of for which speeds of interface they are required.
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 This optional group contains objects that describe the configuration of
of destination-address filtering. destination-address filtering.
In a device operating with a single Filtering Database, In a device operating with a single Filtering Database, interpretation
interpretation of this group is unchanged. 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:
dot1dStaticTable dot1dStaticTable
Entries read from this table include all static entries from Entries read from this table include all static entries from all of
all of the Filtering Databases. Entries for the same MAC the Filtering Databases. Entries for the same MAC address and
address and receive port in more than one Filtering Database receive port in more than one Filtering Database must appear only
must appear only once since these are the indices of this once since these are the indices of this table. This table should
table. This table should be implemented as read-only in be implemented as read-only in devices that support multiple
devices that support multiple Forwarding Databases - instead, Forwarding Databases - instead, write access should be provided
write access should be provided through dot1qStaticUnicastTable through dot1qStaticUnicastTable and dot1qStaticMulticastTable, as
and dot1qStaticMulticastTable, as defined in this document. defined in this document.
4. Extensions to RFC 1493 4. Extensions to RFC 1493
In addition to the objects in RFC1493, this document contains: In addition to the objects in RFC1493, this document contains:
(1) References point to sections of IEEE 802.1D-1998. (1) References point to sections of IEEE 802.1D-1998.
(2) Added support for multiple traffic classes and dynamic multicast (2) Added support for multiple traffic classes and dynamic multicast
filtering as per IEEE 802.1D-1998. filtering as per IEEE 802.1D-1998.
(3) Added support for bridged Virtual LANs as per IEEE 802.1Q-1998. (3) Added support for bridged Virtual LANs as per IEEE 802.1Q-1998.
(4) Added support for 64-bit versions of existing RFC1493 port (4) Added support for 64-bit versions of existing RFC1493 port
counters. counters.
5. Change Log and Editorial Stuff 5. Change Log and Editorial Stuff
5.1. Changes since draft-ietf-bridge-bridgemib-00.txt 5.1. Changes since draft-ietf-bridge-bridgemib-01.txt
VLAN tables indexed by VlanIndex, not ifIndex Traffic Classes:
- same as VlanId for < 4095 and of local scope if >= 4096. Split into separate conformance groups, according to the
requirements for the supported media. Descriptions and
capabilities updated to reflect this.
Statistics:
Simplified to be more like RFC1493.
VID and FID:
Restrictions removed to allow local identities outside of the
802.1Q range.
SMIv2 conformance:
Replaced INTEGER with 'UInteger32' (where no range was specified).
Replaced 'Timeout' with 'TimeInterval'.
New objects added: New objects added:
dot1qFdbDynamicCount, dot1dPortCapabilitiesTable, dot1qTpVlanPortInFrames, dot1qTpVlanPortOutFrames,
dot1dDeviceCapabilities, dot1qVlanTimeMark, dot1qVlanNumDeletes, dot1qTpVlanPortInDiscards, dot1qTpVlanPortHCInFrames,
dot1qLearningConstraintsLastChange dot1qTpVlanPortHCOutFrames, dot1qTpVlanPortHCInDiscards,
dot1dTrafficClasses, dot1dTrafficClassPriority,
dot1qNextFreeLocalVlanIndex
Old objects deleted: Old objects deleted:
dot1qVlanId, dot1qVlanStaticVlanId, dot1qFramesReceived, dot1qOctetsReceived, dot1qForwardOutbound,
dot1dTrafficClassesResetToDefaults, dot1dPortGmrpOperStatus, dot1qDiscardInbound, dot1qDiscardNoBuffers,
dot1pPortGvrpOperStatus, dot1dGarpReset, dot1qTpFdbClear, dot1qDiscardTransitDelayExceeded, dot1qDiscardError,
dot1qFdbClear dot1qDiscardOnIngressFiltering, dot1qHCFramesReceived,
dot1qHCOctetsReceived, dot1qHCForwardOutbound,
dot1qHCDiscardInbound, dot1qHCDiscardNoBuffers,
dot1qHCDiscardTransitDelayExceeded, dot1qHCDiscardError,
dot1qHCDiscardOnIngressFiltering,
dot1qLearningConstraintsLastChange
Objects renamed/moved: Objects renamed/moved:
dot1qVlanIfIndex -> dot1qVlanIndex, dot1qTpGroupAllowedToGoTo -> dot1qTpGroupEgressPorts
dot1qServiceReqTable -> dot1qForwardAllTable dot1qVlanStaticUntagged -> dot1qVlanStaticUntaggedPorts
+ dot1qForwardUnregisteredTable, dot1dPortCapabilities.dot1qConfigurablePvidTagging
dot1qStaticTable -> dot1qStaticUnicastTable -> dot1dDeviceCapabilities.dot1qConfigurablePvidTagging
+ dot1qStaticMulticastTable,
dot1dPortGmrpAdminStatus -> dot1dPortGmrpStatus,
dot1qPortGvrpAdminStatus -> dot1qPortGvrpStatus,
dot1qTpGroupGmrp/Igmp merged -> dot1qTpGroupLearnt,
dot1qCanOverridePvidTagging -> dot1qConfigurablePvidTagging bit
in dot1dCapabilities,
dot1qVlanAdminUntaggedPorts -> dot1qVlanStaticUntaggedPorts,
dot1qVlanFixedPorts -> dot1qVlanStaticEgressPorts,
dot1qVlanForbiddenPorts -> dot1qVlanForbiddenEgressPorts,
dot1qVlanOperUntaggedPorts -> dot1qVlanCurrentUntaggedPorts,
dot1qVlanOperEgressPorts -> dot1qVlanCurrentEgressPorts,
dot1qStaticMulticastAllowedToGoTo ->
dot1qStaticMulticastStaticEgressPorts
+ dot1qStaticMulticastForbiddenEgressPorts
Object descriptions clarified: Object descriptions clarified:
dot1qVlanStaticEgressPorts, dot1qVlanForbiddenEgressPorts, dot1dPortDefaultUserPriority, dot1dUserPriorityRegenTable,
dot1qVlanStaticUntagged, dot1qForwardAllTable, dot1dTrafficClassTable, dot1qGvrpStatus, dot1qTpGroupEgressPorts,
dot1qForwardUnregisteredTable, dot1qForwardAllStaticPorts, dot1qForwardAllStaticPorts, dot1qStaticUnicastAllowedToGoTo,
dot1qForwardUnregisteredStaticPorts dot1qStaticMulticastStaticEgressPorts,
dot1qStaticMulticastForbiddenEgressPorts, dot1qVlanStatus,
dot1qVlanStaticName, dot1qVlanStaticUntaggedPorts,
dot1qPortAcceptableFrameTypes, dot1qPortIngressFiltering,
dot1qGvrpPortStatus
Updated compliance clauses: Updated compliance clauses:
qBridgeLearningConstraintsGroup, pBridgeDeviceGmrpGroup, pBridgeDevicePriorityGroup,
qBridgeLearningConstraintDefaultGroup, dot1qForwardAllPorts, pBridgeDefaultPriorityGroup, pBridgeRegenPriorityGroup,
dot1qForwardAllStaticPorts, dot1qForwardUnregisteredPorts, pBridgePriorityGroup, pBridgeAccessPriorityGroup,
dot1qForwardUnregisteredStaticPorts qBridgeFdbUnicastGroup, qBridgeVlanGroup, qBridgeVlanStaticGroup,
qBridgeVlanStatisticsGroup, qBridgeVlanHCStatisticsGroup,
Table indexing: qBridgeLearningConstraintsGroup
new indexing for all per-VLAN tables (see issue 3), for Service
Requirements tables, for dot1qTpGroupTable now by-VID not by-
FID.
New issues (29)-(54) added, other editorial changes.
5.2. To Do List
(1) Update boilerplate for appropriate new SNMP framework(s) (v3?) New issues: (62)-(77) added.
5.3. Open Issues
The following is a list of issues that were discussed at the Interim To Do List (1):
meeting in Cambridge, MA in June 1998. Suggested resolutions agreed Update boilerplate for appropriate new SNMP framework(s). - SNMP
at that meeting are supplied here and the changes have been made to Framework (section 1), Security (section 10) and References updated
the MIB text - they are listed here for comment: to comply with proposed new SNMPv3 guidelines.
(11) 802.1D has separate registrar and applicant controls per state Editorial:
machine (GVRP and GMRP): do we need per-VLAN and per-Group References updated to latest document versions, other editorial
Registrar controls? Agreement from interim meeting was: YES. changes.
This affects
dot1qVlanStaticEgressPorts/dot1qVlanForbiddenEgressPorts and
dot1dStaticAllowedToGoTo - added clarification to DESCRIPTION
clauses for the first two (but we cannot add to RFC1493). Do we
need per-VLAN and per-Group Applicant controls? Agreement from
interim meeting was: NEITHER - per-port is sufficient on
dot1qPortGvrpStatus and dot1pPortGmrpStatus.
(12) Should the per-port GARP admin controls apply to Registrar as 5.2. Open Issues
well as Applicant (dot1qPortGvrpStatus, dot1pPortGmrpStatus)?
Alternative would be to provide separate controls for Applicant
and Registrar. Agreement from interim meeting was: YES - No
change.
(29) dot1dTrafficClassesResetToDefaults - says that it resets stats The following issues were raised on the mailing list after the Plenary
too. What about userPriorityRegenTable? (AR): NUKE meeting in Chicago, IL in August 1998. These issues have not been
dot1dTrafficClassesResetToDefaults addressed in this draft.
(30) Trunk ports - should MIB support such a concept (802.1Q does (77) Should dot1qTpVlanPortInDiscards and dot1qTpVlanPortHCInDiscards
not)? NO count all frames discarded at receive by the VLAN layer? (AR) -
Assume NO for now.
(31) dot1qVlanBridgeUpTime: is this needed per-VLAN? ifLastChange 5.3. Issues closed in this draft
can do this function if we have ifTable entries per-VLAN: NO
(32) Timestamp-based indexing for some tables? dot1dTpFdbTable in The following issues were still open after the Plenary meeting in
RFC1493 - NO dot1qTpFdbTable - NO, TimeFilter not practical; Chicago, IL in August 1998. New issues raised on the mailing list after
lastChange not useful dot1qVlanCurrentTable - YES- added both the Chicago meeting are also included. Suggested resolutions discussed
dot1qVlanTimeMark and dot1qVlanNumDeletes. dot1qStaticTable? NO on the mailing list are noted here and the changes have been made to the
- cannot use TimeFilter on read-create tables text - they are listed here for comment:
dot1qLearningConstraintsTable? NO, add
dot1qLearningConstraintsLastChange. dot1qPortVlanTable? NO -
these are mostly management settable objects
(33) DEFVAL and MIN-ACCESS for dot1qForwardAllStaticPorts and
dot1qForwardUnregisteredStaticPorts? updated descriptions and
added MIN-ACCESS clauses of not-accessible for these objects.
(34) Should an agent instantiate a set of dot1qForwardAllTable and (5) ifStackTable usage - how to represent binding of IP interfaces to
dot1qForwardUnregisteredTable entries for each FDB that it could VLANs now that we do not necessarily have one ifEntry per VLAN. -
have or just a set for each FDB that is currently in use? The Not included due to lack of enthusiasm from the group.
latter - add clarification.
(35) Nuke dot1qStaticReceivePort? There are not any implementations (62) Remove support for multiple egress ports in static unicast FDB
of the RFC1493 equivalent are there? Yes there are - keep it. entries? (KK) - Not applicable. The entry indicates ports a
unicast address MAY be learnt on, not ports it MUST be forwarded
to. Description clarified.
(36) Should agent accept SETs to dot1qVlanStaticUntagged, (63) dot1dGmrpStatus is a member of a mandatory group and has a DEFVAL
dot1qVlanStaticEgressPorts, dot1qVlanForbiddenEgressPorts that of "enabled". This is inappropriate for devices which do not
it cannot actually implement? (ELB) NO - clarify description. support extended filtering services but do support priority
forwarding and therefore implement this MIB. (DM) - Similar
problem with dot1dTrafficClassesEnabled. Defined both of these in
separate groups, each group is mandatory only if that feature is
supported by the bridge. Capabilities bit added to indicate
support for traffic classes. Removed MIN-ACCESS for
dot1dTrafficClassesEnabled.
(37) Nuke dot1dPortGmrp/GvrpOperStatus? - YES. (64) dot1dPortCapabilities, dot1qPortIngressFiltering - tighten up the
text to read: "supports the discarding of any frame received on
that Port whose VLAN classification does not include that Port in
its Member set." (DM) - Done. Also changed the name of the
capability bit for this to dot1qIngressFiltering to resolve
duplicate name. Changed the description of
dot1qPortIngressFiltering object to match the above text.
(38) Nuke dot1qResetToDefaults? (KZM) - YES (65) dot1qConfigurablePvidTagging - According to 802.1Q it is a
requirement. Is there a reason to treat it as optional in the MIB?
(DM) - Reference is 12.10.1.1.3/b/2. The 802.1Q description is
"whether the implementation supports the ability to override the
default PVID setting and its egress status (VLAN-Tagged or
Untagged) on each port". Capability description modified with the
above quote from the standard.
(39) Nuke dot1dGarpReset? (KZM) YES, and update DESCRIPTIONs of (66) PVID tagging should be moved from dot1dPortCapabilities to
dot1dGmrpStatus, dot1qGvrpStatus, dot1dPortGmrpStatus, dot1dDeviceCapabilities. (AHS) - Done.
dot1qPortGvrpStatus,
(40) Make dot1dPortGarp timers per-device, not per-port? (KZM) saves (67) dot1dUserPriorityRegenTable - is not relevant for Ethernet LANs. A
NVRAM - assume leave it the same for now statement to this effect and a reference (ISO/IEC 15802-3 6.4) may
be helpful. (DM) - Done. Also put this in a separate conformance
group, mandatory for media which support native User Priority.
dot1dTrafficClassTable updated to be independent of this table.
(41) MIN-ACCESS read-only for dot1dTrafficClass, (68) What should the compliance be for dot1dPortDefaultUserPriority?
dot1dRegenUserPriority (KZM) - do it (AHS) - Put this in a separate conformance group, mandatory for
media which do not support native User Priority.
(42) dot1qTpGroupGmrp/Igmp (KZM) - merge these to dot1qTpGroupLearnt (69) There are no definitions for qBridgeFdbGroup or qBridgeTpFdbGroup -
remove references to these in qBridgeCompliance section. (AHS) -
Done.
(43) do we need 64-bit dot1qHC errors? (KZM) - Assume yes for now (70) Should we count the number of dynamic group address entries per
VLAN? (AHS) - This can be derived by counting rows in
dot1dTpGroupTable. Added it to the 'not included' list in section
3.2.1.
(45) do we need dot1qVersion? (KZM) - assume Yes (71) dot1qTpGroupAllowedToGoTo really means 'forward to'. (DM) - The
description has been clarified and the object renamed as
'dot1qTpGroupEgressPorts'.
(46) nuke dot1qTpFdbClear? dot1qFdbClear? (KZM) - assume Yes (802.1Q (72) Why provide a default value for dot1qStaticUnicastAllowedToGoTo?
"reset bridge" operation is not now supported). It should include only member ports of the frame's VLAN
classification. The phrase "a string of ones" is incorrect. Also
for dot1qStaticMulticastStaticEgressPorts. (DM) - Clarified the
description, this value only applies to ports also in the
dot1qVlanCurrentEgressPorts list for the VLAN. Also applied this
clarification to dot1qForwardAllStaticPorts.
(47) do we need dot1qFdbTable which now contains only dot1qFdbId? - (73) dot1qStaticUnicastAllowedToGoTo: why is the term "allowed" used
assume YES for now (it also now has dot1qFdbDynamicCount). here? Doesn't this object define exactly to which port(s) the
frame is to be forwarded? (DM) - No. The consensus from recent
discussions interpret this as 'may be dynamically learnt on'.
Clarified the description.
(48) should dot1qTpFdbTable be {FID,MAC} or {MAC,FID} - assume the (74) The Untagged Set for a VLAN is only modified statically by
former for now management and this object will always have the same value as the
(53) Should mention that VLAN entries in ifTable should have dot1qVlanStaticUntagged. If so, should it be eliminated. (DM) -
ifPhysAddress zero-length/filled (KK). No longer relevant since Untagged VLANs may also be dynamically learned. No change
we do not include such ifTable entries. required.
(54) dot1qVlanAdminUntaggedPorts - expand DESCRIPTION to include (75) The meaning of dot1qVlanStatus is confusing. (DM) - The description
meaning of 0 (KK). Changed description to talk about has been clarified.
include/exclude from the set of ports: refer to Portlist TC for
0/1 meaning.
Issues that are believed still to be open at close of June 1998 (76) dot1qVlanStatisticsTable potentially requires a very large number
interim meeting and have not been addressed in this draft. This also of counters and may not be achievable in many architectures. A
includes new issues that have arisen due to changes agreed at that control table which specifies for which VLANs the counters would be
meeting: maintained could limit the number of counters required. (DM) - Not
considered worthwhile. No change required.
(5) ifStackTable usage - how to represent binding of IP interfaces Issues that were closed at the August 1998 plenary meeting and have been
to VLANs now that we do not necessarily have one ifEntry per addressed in this draft:
VLAN.
(44) Clarification of dot1qHC counter descriptions - what does (44) Clarification of dot1qHC counter descriptions - what does inbound
inbound mean? What counts as errors? 2 separable issues: 1. It mean? What counts as errors? 2 separable issues:
was requested that the meaning of dot1qDiscardInbound be 1. It was requested that the meaning of dot1qDiscardInbound be
clarified to ensure it is distinct from other counters. clarified to ensure it is distinct from other counters.
(Specifically, why is it different from 1493?) (KZM) - this can (Specifically, why is it different from 1493?) (KZM) - this can be
be derived from other counters - NUKE IT! 2. Why are all of derived from other counters - NUKE IT!
these so different from RFC1493? e.g. do they refer to 2. Why are all of these so different from RFC1493? e.g. do they
Transparent-only? What about SRT or SR? refer to Transparent-only? What about SRT or SR? - Counters
limited to a set equivalent to RFC1493.
(49) Now that dot1qVlanStaticTable is indexed by VlanIndex/VlanId we (49) Now that dot1qVlanStaticTable is indexed by VlanIndex/VlanId we
need a "next free" variable since these values must be managed need a "next free" variable since these values must be managed by
by agent. agent. - Added dot1qVlanNextFreeIndex.
(50) dot1qVlanFdbId, dot1qMaxSupportedVlans, dot1qNumVlans should not (50) dot1qVlanFdbId, dot1qMaxSupportedVlans, dot1qNumVlans should not be
be range-limited. If they are then we need new objects to range-limited. If they are then we need new objects to represent
represent the number of non-802.1Q "VLANs" too. (AHS) the number of non-802.1Q "VLANs" too. (AHS) - Range restrictions
removed.
(51) dot1qConfigurablePvidTagging: does this also cover the "I can (51) dot1qConfigurablePvidTagging: does this also cover the "I can only
only set a single VLAN to be untagged on egress" implementation set a single VLAN to be untagged on egress" implementation option
option in 802.1Q? in 802.1Q? - Description of dot1qVlanStaticUntaggedPorts clarified
to cover this.
(52) Do we need an explicit "dot1dExtendedFilteringServicesStatus" (52) Do we need an explicit "dot1dExtendedFilteringServicesStatus"
enable/disable object? (AHS) enable/disable object? (AHS) - No.
(55) Need to split dot1qStaticAllowedToGoTo into two portmaps in
order to represent the 3 possible states from 802.1Q 8.11.2:
static, forbidden and allowed to be influenced by dynamic info.
Same issue for unicast table. (ELB) DONE for multicast - split (55) Need to split dot1qStaticAllowedToGoTo into two portmaps in order
dot1qStaticAllowedToGoTo into to represent the 3 possible states from 802.1Q 8.11.2: static,
forbidden and allowed to be influenced by dynamic info. (ELB) DONE
for multicast - split dot1qStaticAllowedToGoTo into
dot1qStaticMulticastStaticEgressPorts and dot1qStaticMulticastStaticEgressPorts and
dot1qStaticMulticastForbiddenEgressPorts. Issue still open for dot1qStaticMulticastForbiddenEgressPorts. Same issue for unicast
unicast. table. - Not required to split this for unicast.
(56) Should a value of 0 be allowed for dot1qTpFdbPort? This is (56) Should a value of 0 be allowed for dot1qTpFdbPort? This is
inherited from RFC1493 (ELB) inherited from RFC1493. (ELB) - Yes it is allowed. No change
required.
(57) Rename dot1qVlanStaticUntagged as dot1qVlanStaticUntaggedPorts (57) Rename dot1qVlanStaticUntagged as dot1qVlanStaticUntaggedPorts for
for consistency. (ELB) consistency. (ELB) - Done.
(58) If an empty string is used for dot1qVlanStaticName, does it have (58) If an empty string is used for dot1qVlanStaticName, does it have to
to be unique? The description implies it must be unique. (ELB) be unique? The description implies it must be unique. (ELB) NO -
NO - clarified this. clarified this.
(59) Should dot1qPvid have syntax VlanIndex (currently it is VlanId)? (59) Should dot1qPvid have syntax VlanIndex (currently it is VlanId)?
(ELB) (ELB) - Yes, done.
(60) Do dot1qPortAcceptableFrameTypes and dot1qPortIngressFiltering (60) Do dot1qPortAcceptableFrameTypes and dot1qPortIngressFiltering also
also apply to tagged GMRP packets? (ELB) apply to tagged GMRP packets? (ELB) - Yes, descriptions clarified.
(61) Do we need dot1qLearningContraintsLastChange? It just reminds (61) Do we need dot1qLearningContraintsLastChange? It just reminds the
the manager of changes that he or some other manager made. (ELB) manager of changes that he or some other manager made. (ELB) - No,
object removed.
5.4. Issues closed in this draft 5.4. Issues closed in previous drafts
(2) Indexing of tables by VlanId or by ifIndex? use VlanId with (1) Should this MIB offer support for SMIv1-only agents (Counter32/64)?
special semantics for values >=4096. This raises new issue 49. ADDED Counter32/Counter64 versions of the per-VLAN statistics.
ADDED Counter64 versions of the per-port statistics from RFC1493.
Added appropriate conformance clauses for all.
(2) Indexing of tables by VlanId or by ifIndex? use VlanId with special
semantics for values >=4096. This raises new issue 49.
(3) Indexing of FDB tables by MacAddress or by something else? Use (3) Indexing of FDB tables by MacAddress or by something else? Use
MacAddress. MacAddress.
(8) Learned entry discards counter per-VLAN or per-device? Per- (4) Include RFC1493 by value or reference? REFERENCE
device, already in RFC1493.
(6) Representations of filtering entry for "AllGroups" and
"AllUnregisteredGroups" DONE
(7) Should we represent all available FIDs up front or use a "next
free" object for the manager to create them as needed? NEITHER -
see issue 25 above.
(8) Learned entry discards counter per-VLAN or per-device? Per-device,
already in RFC1493.
(9) Do we need per-FID static/dynamic filtering entry counts? (9) Do we need per-FID static/dynamic filtering entry counts?
(12.7.1.1.3) YES - count for dynamic only added as (12.7.1.1.3) YES - count for dynamic only added as
dot1qFdbDynamicCount. dot1qFdbDynamicCount.
(20) Do we need "read filtering database (12.7.1.1): filtering (10) Separate config and status info for e.g. dot1dPortGmrpTable,
database size"? NO dot1qPortVlanTable? NO CHANGE
(21) Do we need "read permanent database (12.7.6.1): permanent (11) 802.1D has separate registrar and applicant controls per state
database size"? NO (this issue was wrongly recorded last time) machine (GVRP and GMRP): do we need per-VLAN and per-Group
(22) Do we need a 'next free ifIndex' object? NO - see issue 2. But Registrar controls? YES. Affects dot1qVlanStaticEgressPorts,
see new issue 49. dot1qVlanForbiddenEgressPorts and dot1dStaticAllowedToGoTo - added
clarification to DESCRIPTION clauses for the first two (but we
cannot add to RFC1493).
Do we need per-VLAN and per-Group Applicant controls? NEITHER -
per-port is sufficient on dot1qPortGvrpStatus and
dot1pPortGmrpStatus.
(23) Do we need default learning constraints? YES - mandatory if (12) Should the per-port GARP admin controls apply to Registrar as well
device is Hybrid-VLAN-Learning-capable (can do both IVL and as Applicant (dot1qPortGvrpStatus, dot1pPortGmrpStatus)?
SVL). Alternative would be to provide separate controls for Applicant and
Registrar. YES - No change.
(13) Learning constraints table seems clumsy - can we improve this? DONE
(14) Do we need to define a "notify vlan registration failure" trap? NO
(15) dot1qFdbAgingTime is currently per-FID: 802.1Q has it per-device.
PER DEVICE
(16) dot1pPortDefaultUserPriority - can this usefully be per-port, per-
VLAN? PER-PORT
(17) Both dot1qVlanCurrentTable and dot1qVlanStaticTable are indexed by
dot1qVlanIfIndex but that only appears in dot1qVlanStaticTable - is
this a problem? MOVED TO dot1qVlanCurrentTable.
(18) Should we choose same names (up/down) as IF-MIB for values of the
admin/oper status values, rather than defining our own new TC? Is
there an existing TC we can import? NO CHANGE.
(19) Should we have write-only "reset" objects or should these be read-
write to help MIB browsers (assume write-only)? READ-WRITE.
(20) Do we need "read filtering database (12.7.1.1): filtering database
size"? NO
(21) Do we need "read permanent database (12.7.6.1): permanent database
size"? NO (this issue was wrongly recorded last time)
(22) Do we need a 'next free ifIndex' object? NO - see issue 2. But see
new issue 49.
(23) Do we need default learning constraints? YES - mandatory if device
is Hybrid-VLAN-Learning-capable (can do both IVL and SVL).
(24) Can we remove separate GARP controls? YES. (24) Can we remove separate GARP controls? YES.
(25) Do we need to split dot1qStaticTable into (25) Do we need to split dot1qStaticTable into dot1qStaticUnicastTable
dot1qStaticUnicastTable and dot1qStaticMulticastTable? YES: and dot1qStaticMulticastTable? YES: dot1qStaticTable ->
dot1qStaticTable -> dot1qStaticUnicastTable, indexed by FID + dot1qStaticUnicastTable, indexed by FID +
dot1qStaticMulticastTable, indexed by VID. Also index dot1qStaticMulticastTable, indexed by VID. Also index
dot1qTpGroupTable by VID. This matches the indexing assumed by dot1qTpGroupTable by VID. This matches the indexing assumed by
802.1Q. 802.1Q.
(26) Should we have the different Service Requirements (AllGroups, (26) Should we have the different Service Requirements (AllGroups,
AllUnregisteredGroups) in dot1qServiceReqTable or should we AllUnregisteredGroups) in dot1qServiceReqTable or should we leave
leave with dot1qServiceRequirement as a 2nd index? Split into 2 with dot1qServiceRequirement as a 2nd index? Split into 2 tables,
tables, each indexed by VID. each indexed by VID.
(27) Do we want "capabilities" bitmap objects? YES - per-port (27) Do we want "capabilities" bitmap objects? YES - per-port
dot1dPortCapabilities and dot1dDeviceCapabilities. dot1dPortCapabilities and dot1dDeviceCapabilities.
(28) Should ifRcvAddressTable contain entries for e.g. spanning-tree, (28) Should ifRcvAddressTable contain entries for e.g. spanning-tree,
GMRP, GVRP addresses? NO - clarify in preface. GMRP, GVRP addresses? NO - clarify in preface.
5.5. Issues closed in previous drafts (29) dot1dTrafficClassesResetToDefaults - says that it resets stats too.
What about userPriorityRegenTable? (AR): NUKE
dot1dTrafficClassesResetToDefaults
(1) Should this MIB offer support for SMIv1-only agents (30) Trunk ports - should MIB support such a concept (802.1Q does not)?
(Counter32/64)? ADDED Counter32/Counter64 versions of the per- NO
VLAN statistics. ADDED Counter64 versions of the per-port
statistics from RFC1493. Added appropriate conformance clauses
for all.
(4) Include RFC1493 by value or reference? REFERENCE (31) dot1qVlanBridgeUpTime: is this needed per-VLAN? ifLastChange can
do this function if we have ifTable entries per-VLAN: NO
(6) Representations of filtering entry for "AllGroups" and (32) Timestamp-based indexing for some tables? dot1dTpFdbTable in
"AllUnregisteredGroups" DONE RFC1493 - NO dot1qTpFdbTable - NO, TimeFilter not practical;
lastChange not useful dot1qVlanCurrentTable - YES- added both
dot1qVlanTimeMark and dot1qVlanNumDeletes. dot1qStaticTable? NO -
cannot use TimeFilter on read-create tables.
dot1qLearningConstraintsTable? NO, add
dot1qLearningConstraintsLastChange. dot1qPortVlanTable? NO - these
are mostly management settable objects.
(7) Should we represent all available FIDs up front or use a "next (33) DEFVAL and MIN-ACCESS for dot1qForwardAllStaticPorts and
free" object for the manager to create them as needed? NEITHER dot1qForwardUnregisteredStaticPorts? updated descriptions and these
- see issue 25 above. objects are in an optional group, so MIN-ACCESS not-accessible is
not required.
(10) Separate config and status info for e.g. dot1dPortGmrpTable, (34) Should an agent instantiate a set of dot1qForwardAllTable and
dot1qPortVlanTable? NO CHANGE dot1qForwardUnregisteredTable entries for each FDB that it could
have or just a set for each FDB that is currently in use? The
latter - added clarification.
(13) Learning constraints table seems clumsy - can we improve this? (35) Nuke dot1qStaticReceivePort? There are not any implementations of
DONE the RFC1493 equivalent are there? Yes there are - keep it.
(14) Do we need to define a "notify vlan registration failure" trap? (36) Should agent accept SETs to dot1qVlanStaticUntaggedPorts,
NO dot1qVlanStaticEgressPorts, dot1qVlanForbiddenEgressPorts that it
cannot actually implement? (ELB) NO - clarify description.
(15) dot1qFdbAgingTime is currently per-FID: 802.1Q has it per- (37) Nuke dot1dPortGmrp/GvrpOperStatus? - YES.
device. PER DEVICE
(16) dot1pPortDefaultUserPriority - can this usefully be per-port, (38) Nuke dot1qResetToDefaults? (KZM) - YES
per-VLAN? PER-PORT
(17) Both dot1qVlanCurrentTable and dot1qVlanStaticTable are indexed (39) Nuke dot1dGarpReset? (KZM) YES, and update DESCRIPTIONs of
by dot1qVlanIfIndex but that only appears in dot1dGmrpStatus, dot1qGvrpStatus, dot1dPortGmrpStatus,
dot1qVlanStaticTable - is this a problem? MOVED TO dot1qPortGvrpStatus,
dot1qVlanCurrentTable.
(18) Should we choose same names (up/down) as IF-MIB for values of (40) Make dot1dPortGarp timers per-device, not per-port? (KZM) saves
the admin/oper status values, rather than defining our own new NVRAM - Leave it the same.
TC? Is there an existing TC we can import? NO CHANGE.
(19) Should we have write-only "reset" objects or should these be (41) MIN-ACCESS read-only for dot1dTrafficClass, dot1dRegenUserPriority
read-write to help MIB browsers (assume write-only)? READ-WRITE. (KZM) - done.
(42) dot1qTpGroupGmrp/Igmp (KZM) - merge these to dot1qTpGroupLearnt -
Yes.
(43) Do we need 64-bit dot1qHC errors? (KZM) - Yes.
(45) Do we need dot1qVersion? (KZM) - Yes.
(46) Nuke dot1qTpFdbClear? dot1qFdbClear? (KZM) - Yes (802.1Q "reset
bridge" operation is not now supported).
(47) Do we need dot1qFdbTable which now contains only dot1qFdbId? - YES
(it also now has dot1qFdbDynamicCount).
(48) Should dot1qTpFdbTable be {FID,MAC} or {MAC,FID} - the former.
(53) Should mention that VLAN entries in ifTable should have
ifPhysAddress zero-length/filled (KK). No longer relevant since we
do not include such ifTable entries.
(54) dot1qVlanAdminUntaggedPorts - expand DESCRIPTION to include meaning
of 0 (KK). Changed description to talk about include/exclude from
the set of ports: refer to Portlist TC for 0/1 meaning.
6. Definitions for Extended Bridge MIB 6. Definitions for Extended Bridge MIB
P-BRIDGE-MIB DEFINITIONS ::= BEGIN P-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- IEEE 802.1p MIB -- IEEE 802.1p MIB
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, TEXTUAL-CONVENTION TruthValue, TimeInterval, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
MacAddress, Timeout, dot1dTp, dot1dTpPort, MacAddress, dot1dTp, dot1dTpPort,
dot1dBridge, dot1dBasePortEntry, dot1dBasePort dot1dBridge, dot1dBasePortEntry, dot1dBasePort
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
pBridgeMIB MODULE-IDENTITY pBridgeMIB MODULE-IDENTITY
LAST-UPDATED "9804242200Z" LAST-UPDATED "9810070000Z"
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
skipping to change at page 26, line 9 skipping to change at page 29, line 9
Paul Langille Paul Langille
Postal: Acacia Networks, Inc. Postal: Acacia Networks, Inc.
650 Suffolk St. 650 Suffolk St.
Lowell, MA 01854 Lowell, MA 01854
USA USA
Phone: +1 (978) 275 0662 Phone: +1 (978) 275 0662
Email: plangille@acacianet.com Email: plangille@acacianet.com
Anil Rijhsinghani Anil Rijhsinghani
Postal: Cabletron Systems Postal: Cabletron Systems
550 King Street, LKG2-2/Y10 50 Minuteman Road
Littleton, MA 01460-1289 Andover MA 01810
USA USA
Phone: +1 (508) 486-6786 Phone: +1 (978) 684-1295
Email: Anil.Rijhsinghani@digital.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 "9807190000Z" REVISION "9810070000Z"
DESCRIPTION "Updated with revisions from June 1998 Interim DESCRIPTION "Updated with revisions from August 1998 Plenary
meeting." meeting."
::= { dot1dBridge 6 } ::= { dot1dBridge 6 }
pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 } pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 27, line 16 skipping to change at page 30, line 17
dot1dGarp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 3 } dot1dGarp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 3 }
dot1dGmrp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 4 } dot1dGmrp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 4 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- the dot1dExtBase group -- the dot1dExtBase group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dDeviceCapabilities OBJECT-TYPE dot1dDeviceCapabilities OBJECT-TYPE
SYNTAX BITS { SYNTAX BIT STRING {
dot1dExtendedFilteringServices(0), dot1dExtendedFilteringServices(0),
-- can perform filtering of -- can perform filtering of
-- individual multicast -- individual multicast addresses
-- addresses controlled by GMRP. -- controlled by GMRP.
dot1qStaticEntryIndividualPort(1), dot1dTrafficClasses(1),
-- can represent non-zero entries -- can map user priority to
-- in dot1qStaticUnicastReceivePort -- multiple traffic classes.
-- & dot1qStaticMulticastReceivePort. dot1qStaticEntryIndividualPort(2),
dot1qIVLCapable(2), -- Independent VLAN Learning -- dot1qStaticUnicastReceivePort &
dot1qSVLCapable(3), -- Shared VLAN Learning -- dot1qStaticMulticastReceivePort
dot1qHybridCapable(4) -- both of the above simultaneously -- can represent non-zero entries.
dot1qIVLCapable(3), -- Independent VLAN Learning.
dot1qSVLCapable(4), -- Shared VLAN Learning.
dot1qHybridCapable(5),
-- both IVL & SVL simultaneously.
dot1qConfigurablePvidTagging(6)
-- whether the implementation
-- supports the ability to
-- override the default PVID
-- setting and its egress status
-- (VLAN-Tagged or Untagged) on
-- each port.
} }
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 managable
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
"IEEE 802.1D/D16 5.2 and 802.1Q/D10 5.2" "ISO/IEC 15802-3 Section 5.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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value true(1) indicates that Traffic Classes are "The value true(1) indicates that Traffic Classes are
enabled on this bridge. When false(2), the bridge enabled on this bridge. When false(2), the bridge
operates with a single priority level for all traffic." operates with a single priority level for all traffic."
skipping to change at page 29, line 4 skipping to change at page 32, line 14
dot1dPortCapabilitiesEntry OBJECT-TYPE dot1dPortCapabilitiesEntry OBJECT-TYPE
SYNTAX Dot1dPortCapabilitiesEntry SYNTAX Dot1dPortCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of capabilities information about this port "A set of capabilities information about this port
indexed by dot1dBasePort." indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry } AUGMENTS { dot1dBasePortEntry }
::= { dot1dPortCapabilitiesTable 1 } ::= { dot1dPortCapabilitiesTable 1 }
Dot1dPortCapabilitiesEntry ::= Dot1dPortCapabilitiesEntry ::=
SEQUENCE { SEQUENCE {
dot1dPortCapabilities dot1dPortCapabilities
BITS BIT STRING
} }
dot1dPortCapabilities OBJECT-TYPE dot1dPortCapabilities OBJECT-TYPE
SYNTAX BITS { SYNTAX BIT STRING {
dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of
-- frames and GVRP. -- frames and GVRP.
dot1qConfigurableAcceptableFrameTypes(1), dot1qConfigurableAcceptableFrameTypes(1),
-- allows modification of the value -- allows modified values of
-- of dot1qPortAcceptableFrameTypes. -- dot1qPortAcceptableFrameTypes.
dot1qPortIngressFiltering(2), dot1qIngressFiltering(2)
-- supports filtering on ingress -- supports the discarding of any
-- of all VLANs not represented in -- frame received on a Port whose
-- an egress list. -- VLAN classification does not
dot1qConfigurablePvidTagging(3) -- include that Port in its Member
-- allows the VLAN which is the current -- set.
-- PVID to be tagged on egress.
} }
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 managable through this MIB."
REFERENCE REFERENCE
"IEEE 802.1D/D16 5.2 and 802.1Q/D10 5.2" "ISO/IEC 15802-3 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
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 30, line 31 skipping to change at page 33, line 41
INTEGER, INTEGER,
dot1dPortNumTrafficClasses dot1dPortNumTrafficClasses
INTEGER INTEGER
} }
dot1dPortDefaultUserPriority OBJECT-TYPE dot1dPortDefaultUserPriority OBJECT-TYPE
SYNTAX INTEGER (0..7) SYNTAX INTEGER (0..7)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The default ingress User Priority for this port." "The default ingress User Priority for this port. This
only has effect on media, such as Ethernet, that do not
support native User Priority."
::= { dot1dPortPriorityEntry 1 } ::= { dot1dPortPriorityEntry 1 }
dot1dPortNumTrafficClasses OBJECT-TYPE dot1dPortNumTrafficClasses OBJECT-TYPE
SYNTAX INTEGER (1..8) SYNTAX INTEGER (1..8)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of egress traffic classes supported on this "The number of egress traffic classes supported on this
port. This object may optionally be read-only." port. This object may optionally be read-only."
::= { dot1dPortPriorityEntry 2 } ::= { dot1dPortPriorityEntry 2 }
skipping to change at page 31, line 9 skipping to change at page 34, line 20
-- User Priority Regeneration Table -- User Priority Regeneration Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dUserPriorityRegenTable OBJECT-TYPE dot1dUserPriorityRegenTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dUserPriorityRegenEntry SYNTAX SEQUENCE OF Dot1dUserPriorityRegenEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of Regenerated User Priorities for each received "A list of Regenerated User Priorities for each received
User Priority on each port of a bridge. The Regenerated User Priority on each port of a bridge. The Regenerated
User Priority value is used to index the Traffic Class User Priority value may be used to index the Traffic
Table for each input port. The default values for Class Table for each input port. This only has effect
Regenerated User Priorities are the same as the User on media that support native User Priority. The default
Priorities." values for Regenerated User Priorities are the same as
the User Priorities."
REFERENCE
"ISO/IEC 15802-3 Section 6.4"
::= { dot1dPriority 2 } ::= { dot1dPriority 2 }
dot1dUserPriorityRegenEntry OBJECT-TYPE dot1dUserPriorityRegenEntry OBJECT-TYPE
SYNTAX Dot1dUserPriorityRegenEntry SYNTAX Dot1dUserPriorityRegenEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A mapping of incoming User Priority to a Regenerated "A mapping of incoming User Priority to a Regenerated
User Priority." User Priority."
INDEX { dot1dBasePort, dot1dUserPriority } INDEX { dot1dBasePort, dot1dUserPriority }
skipping to change at page 32, line 4 skipping to change at page 35, line 18
::= { dot1dUserPriorityRegenEntry 1 } ::= { dot1dUserPriorityRegenEntry 1 }
dot1dRegenUserPriority OBJECT-TYPE dot1dRegenUserPriority OBJECT-TYPE
SYNTAX INTEGER (0..7) SYNTAX INTEGER (0..7)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Regenerated User Priority the incoming User "The Regenerated User Priority the incoming User
Priority is mapped to for this port." Priority is mapped to for this port."
::= { dot1dUserPriorityRegenEntry 2 } ::= { dot1dUserPriorityRegenEntry 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Traffic Class Table -- Traffic Class Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dTrafficClassTable OBJECT-TYPE dot1dTrafficClassTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dTrafficClassEntry SYNTAX SEQUENCE OF Dot1dTrafficClassEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table mapping Regenerated User Priority to Traffic "A table mapping evaluated User Priority to Traffic
Class, for forwarding by the bridge. Traffic class is a Class, for forwarding by the bridge. Traffic class is a
number in the range (1..dot1dPortNumTrafficClasses)." number in the range (0..(dot1dPortNumTrafficClasses-1))."
REFERENCE REFERENCE
"IEEE 802.1D/D16 Table 7-2" "ISO/IEC 15802-3 Table 7-2"
::= { dot1dPriority 3 } ::= { dot1dPriority 3 }
dot1dTrafficClassEntry OBJECT-TYPE dot1dTrafficClassEntry OBJECT-TYPE
SYNTAX Dot1dTrafficClassEntry SYNTAX Dot1dTrafficClassEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"User Priority to Traffic Class mapping." "User Priority to Traffic Class mapping."
INDEX { dot1dBasePort, dot1dRegenUserPriority } INDEX { dot1dBasePort, dot1dTrafficClassPriority }
::= { dot1dTrafficClassTable 1 } ::= { dot1dTrafficClassTable 1 }
Dot1dTrafficClassEntry ::= Dot1dTrafficClassEntry ::=
SEQUENCE { SEQUENCE {
dot1dTrafficClassPriority
INTEGER,
dot1dTrafficClass dot1dTrafficClass
INTEGER INTEGER
} }
dot1dTrafficClassPriority OBJECT-TYPE
SYNTAX INTEGER (0..7)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Priority value determined for the received frame.
This value is equivalent to the priority indicated in
the tagged frame received, or one of the evaluated
priorities, determined according to the media-type.
For untagged frames received from Ethernet media, this
value is equal to the dot1dPortDefaultUserPriority value
for the ingress port.
For untagged frames received from non-Ethernet media,
this value is equal to the dot1dRegenUserPriority value
for the ingress port and media-specific user priority."
::= { dot1dTrafficClassEntry 1 }
dot1dTrafficClass OBJECT-TYPE dot1dTrafficClass OBJECT-TYPE
SYNTAX INTEGER (0..7) SYNTAX INTEGER (0..7)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Traffic Class the received frame is mapped to." "The Traffic Class the received frame is mapped to."
::= { dot1dTrafficClassEntry 1 } ::= { dot1dTrafficClassEntry 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Outbound Access Priority Table -- Outbound Access Priority Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dPortOutboundAccessPriorityTable OBJECT-TYPE dot1dPortOutboundAccessPriorityTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortOutboundAccessPriorityEntry SYNTAX SEQUENCE OF Dot1dPortOutboundAccessPriorityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table mapping Regenerated User Priority to Outbound "A table mapping Regenerated User Priority to Outbound
Access Priority. This is a fixed mapping for all port Access Priority. This is a fixed mapping for all port
types, with two options for 802.5 Token Ring." types, with two options for 802.5 Token Ring."
REFERENCE REFERENCE
"IEEE 802.1D/D16 Table 7-3" "ISO/IEC 15802-3 Table 7-3"
::= { dot1dPriority 4 } ::= { dot1dPriority 4 }
dot1dPortOutboundAccessPriorityEntry OBJECT-TYPE dot1dPortOutboundAccessPriorityEntry OBJECT-TYPE
SYNTAX Dot1dPortOutboundAccessPriorityEntry SYNTAX Dot1dPortOutboundAccessPriorityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Regenerated User Priority to Outbound Access Priority "Regenerated User Priority to Outbound Access Priority
mapping." mapping."
INDEX { dot1dBasePort, dot1dRegenUserPriority } INDEX { dot1dBasePort, dot1dRegenUserPriority }
skipping to change at page 34, line 23 skipping to change at page 38, line 13
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"GARP control information for a bridge port." "GARP control information for a bridge port."
AUGMENTS { dot1dBasePortEntry } AUGMENTS { dot1dBasePortEntry }
::= { dot1dPortGarpTable 1 } ::= { dot1dPortGarpTable 1 }
Dot1dPortGarpEntry ::= Dot1dPortGarpEntry ::=
SEQUENCE { SEQUENCE {
dot1dPortGarpJoinTime dot1dPortGarpJoinTime
Timeout, TimeInterval,
dot1dPortGarpLeaveTime dot1dPortGarpLeaveTime
Timeout, TimeInterval,
dot1dPortGarpLeaveAllTime dot1dPortGarpLeaveAllTime
Timeout TimeInterval
} }
dot1dPortGarpJoinTime OBJECT-TYPE dot1dPortGarpJoinTime OBJECT-TYPE
SYNTAX Timeout SYNTAX TimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The GARP Join time, in centiseconds." "The GARP Join time, in centiseconds."
DEFVAL { 20 } DEFVAL { 20 }
::= { dot1dPortGarpEntry 1 } ::= { dot1dPortGarpEntry 1 }
dot1dPortGarpLeaveTime OBJECT-TYPE dot1dPortGarpLeaveTime OBJECT-TYPE
SYNTAX Timeout SYNTAX TimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The GARP Leave time, in centiseconds." "The GARP Leave time, in centiseconds."
DEFVAL { 60 } DEFVAL { 60 }
::= { dot1dPortGarpEntry 2 } ::= { dot1dPortGarpEntry 2 }
dot1dPortGarpLeaveAllTime OBJECT-TYPE dot1dPortGarpLeaveAllTime OBJECT-TYPE
SYNTAX Timeout SYNTAX TimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The GARP LeaveAll time, in centiseconds." "The GARP LeaveAll time, in centiseconds."
DEFVAL { 1000 } DEFVAL { 1000 }
::= { dot1dPortGarpEntry 3 } ::= { dot1dPortGarpEntry 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The GMRP Port Configuration and Status Table -- The GMRP Port Configuration and Status Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dPortGmrpTable OBJECT-TYPE dot1dPortGmrpTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortGmrpEntry SYNTAX SEQUENCE OF Dot1dPortGmrpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of GMRP control and status information about "A table of GMRP control and status information about
every bridge port. Augments the dot1dBasePortTable." every bridge port. Augments the dot1dBasePortTable."
::= { dot1dGmrp 1 } ::= { dot1dGmrp 1 }
skipping to change at page 37, line 38 skipping to change at page 41, line 28
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that have been received by this "The number of frames that have been received by this
port from its segment. Note that a frame received on port from its segment. Note that a frame received on
the interface corresponding to this port is only counted the interface corresponding to this port is only counted
by this object if and only if it is for a protocol being by this object if and only if it is for a protocol being
processed by the local bridging function, including processed by the local bridging function, including
bridge management frames." bridge management frames."
REFERENCE REFERENCE
"IEEE 802.1D-1998: Section 14.6.1.1.3" "ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 1 } ::= { dot1dTpHCPortEntry 1 }
dot1dTpHCPortOutFrames OBJECT-TYPE dot1dTpHCPortOutFrames OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that have been transmitted by this "The number of frames that have been transmitted by this
port to its segment. Note that a frame transmitted on port to its segment. Note that a frame transmitted on
the interface corresponding to this port is only counted the interface corresponding to this port is only counted
by this object if and only if it is for a protocol being by this object if and only if it is for a protocol being
processed by the local bridging function, including processed by the local bridging function, including
bridge management frames." bridge management frames."
REFERENCE REFERENCE
"IEEE 802.1D-1998: Section 14.6.1.1.3" "ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 2 } ::= { dot1dTpHCPortEntry 2 }
dot1dTpHCPortInDiscards OBJECT-TYPE dot1dTpHCPortInDiscards OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of valid frames received which were discarded "Count of valid frames received which were discarded
(i.e., filtered) by the Forwarding Process." (i.e., filtered) by the Forwarding Process."
REFERENCE REFERENCE
"IEEE 802.1D-1998: Section 14.6.1.1.3" "ISO/IEC 15802-3 Section 14.6.1.1.3"
::= { dot1dTpHCPortEntry 3 } ::= { dot1dTpHCPortEntry 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- IEEE 802.1p MIB - Conformance Information -- IEEE 802.1p MIB - Conformance Information
-- ------------------------------------------------------------- -- -------------------------------------------------------------
pBridgeConformance OBJECT IDENTIFIER ::= { pBridgeMIB 2 } pBridgeConformance OBJECT IDENTIFIER ::= { pBridgeMIB 2 }
pBridgeGroups OBJECT IDENTIFIER ::= { pBridgeConformance 1 } pBridgeGroups OBJECT IDENTIFIER ::= { pBridgeConformance 1 }
skipping to change at page 39, line 4 skipping to change at page 42, line 37
pBridgeExtCapGroup OBJECT-GROUP pBridgeExtCapGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dDeviceCapabilities, dot1dDeviceCapabilities,
dot1dPortCapabilities dot1dPortCapabilities
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects indicating the optional "A collection of objects indicating the optional
capabilites of the device." capabilites of the device."
::= { pBridgeGroups 1 } ::= { pBridgeGroups 1 }
pBridgeExtBaseGroup OBJECT-GROUP
pBridgeDeviceGmrpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dTrafficClassesEnabled,
dot1dGmrpStatus dot1dGmrpStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing device-level control "A collection of objects providing device-level control
and status information for the Priority and Multicast for the Multicast Filtering extended bridge services."
Filtering extended bridge services."
::= { pBridgeGroups 2 } ::= { pBridgeGroups 2 }
pBridgePriorityGroup OBJECT-GROUP pBridgeDevicePriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortDefaultUserPriority, dot1dTrafficClassesEnabled
dot1dPortNumTrafficClasses,
dot1dRegenUserPriority,
dot1dTrafficClass
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the priorities "A collection of objects providing device-level control
applicable to each port and the traffic classes for the Priority services."
within a bridge." ::= { pBridgeGroups 3 }
pBridgeDefaultPriorityGroup OBJECT-GROUP
OBJECTS {
dot1dPortDefaultUserPriority
}
STATUS current
DESCRIPTION
"A collection of objects defining the User Priority
applicable to each port for media which do not support
native User Priority."
::= { pBridgeGroups 4 } ::= { pBridgeGroups 4 }
pBridgeAccessPriorityGroup OBJECT-GROUP pBridgeRegenPriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortOutboundAccessPriority dot1dRegenUserPriority
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the media dependent "A collection of objects defining the User Priorities
outbound access level for each priority." applicable to each port for media which support native
User Priority."
::= { pBridgeGroups 5 } ::= { pBridgeGroups 5 }
pBridgeConfigurablePriorityGroup OBJECT-GROUP pBridgePriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortDefaultUserPriority,
dot1dPortNumTrafficClasses, dot1dPortNumTrafficClasses,
dot1dRegenUserPriority,
dot1dTrafficClass dot1dTrafficClass
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects where write-access would "A collection of objects defining the traffic classes
provide the ability to configure the use of priority within a bridge for each evaluated User Priority."
in a bridge."
::= { pBridgeGroups 6 } ::= { pBridgeGroups 6 }
pBridgeAccessPriorityGroup OBJECT-GROUP
OBJECTS {
dot1dPortOutboundAccessPriority
}
STATUS current
DESCRIPTION
"A collection of objects defining the media dependent
outbound access level for each priority."
::= { pBridgeGroups 7 }
pBridgePortGarpGroup OBJECT-GROUP pBridgePortGarpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortGarpJoinTime, dot1dPortGarpJoinTime,
dot1dPortGarpLeaveTime, dot1dPortGarpLeaveTime,
dot1dPortGarpLeaveAllTime dot1dPortGarpLeaveAllTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing port level control "A collection of objects providing port level control
and status information for GARP operation." and status information for GARP operation."
::= { pBridgeGroups 7 } ::= { pBridgeGroups 8 }
pBridgePortGmrpGroup OBJECT-GROUP pBridgePortGmrpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortGmrpStatus, dot1dPortGmrpStatus,
dot1dPortGmrpFailedRegistrations, dot1dPortGmrpFailedRegistrations,
dot1dPortGmrpLastPduOrigin dot1dPortGmrpLastPduOrigin
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing port level control "A collection of objects providing port level control
and status information for GMRP operation." and status information for GMRP operation."
::= { pBridgeGroups 8 } ::= { pBridgeGroups 9 }
pBridgeHCPortGroup OBJECT-GROUP pBridgeHCPortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dTpHCPortInFrames, dot1dTpHCPortInFrames,
dot1dTpHCPortOutFrames, dot1dTpHCPortOutFrames,
dot1dTpHCPortInDiscards dot1dTpHCPortInDiscards
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing 64-bit statistics "A collection of objects providing 64-bit statistics
counters for high capacity bridge ports." counters for high capacity bridge ports."
::= { pBridgeGroups 9 } ::= { pBridgeGroups 10 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- compliance statements -- compliance statements
-- ------------------------------------------------------------- -- -------------------------------------------------------------
pBridgeCompliance MODULE-COMPLIANCE pBridgeCompliance MODULE-COMPLIANCE
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, pBridgeExtBaseGroup } MANDATORY-GROUPS { pBridgeExtCapGroup }
GROUP pBridgeDeviceGmrpGroup
DESCRIPTION
"This group is mandatory for devices supporting the
GMRP application, defined by the extended filtering
services."
GROUP pBridgeDevicePriorityGroup
DESCRIPTION
"This group is mandatory only for devices supporting
the priority forwarding operations defined by the
extended bridge services."
GROUP pBridgeDefaultPriorityGroup
DESCRIPTION
"This group is mandatory only for devices supporting
the priority forwarding operations defined by the
extended bridge services with media types, such as
Ethernet, that do not support native User Priority."
GROUP pBridgeRegenPriorityGroup
DESCRIPTION
"This group is mandatory only for devices supporting
the priority forwarding operations defined by the
extended bridge services with media types that also
support native User Priority."
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 the
extended bridge services." extended bridge services."
GROUP pBridgeAccessPriorityGroup GROUP pBridgeAccessPriorityGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
GROUP pBridgeConfigurablePriorityGroup
DESCRIPTION
"Write-access must be provided to all objects in
this group in order to manage priority in a switch
as specified by IEEE 802.1D. However, it is
optional to support management of priority."
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
skipping to change at page 42, line 6 skipping to change at page 46, line 27
GMRP application, defined by the extended filtering GMRP application, defined by the extended filtering
services." services."
GROUP pBridgeHCPortGroup GROUP pBridgeHCPortGroup
DESCRIPTION DESCRIPTION
"This group is mandatory if the network interface "This group is mandatory if the network interface
to which this bridge port is attached has the to which this bridge port is attached has 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."
OBJECT dot1dTrafficClassesEnabled
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
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."
skipping to change at page 43, line 14 skipping to change at page 47, line 15
7. Definitions for Virtual Bridge MIB 7. Definitions for Virtual Bridge MIB
Q-BRIDGE-MIB DEFINITIONS ::= BEGIN Q-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- IEEE 802.1Q MIB -- IEEE 802.1Q MIB
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Counter64 Counter32, Counter64, UInteger32
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, TruthValue, DisplayString, TEXTUAL-CONVENTION, RowStatus, TruthValue, DisplayString, TEXTUAL-CONVENTION
TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
MacAddress, dot1dBridge, dot1dBasePortEntry, dot1dBasePort MacAddress, 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 "9807190000Z" LAST-UPDATED "9810070000Z"
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
skipping to change at page 44, line 14 skipping to change at page 48, line 13
Paul Langille Paul Langille
Postal: Acacia Networks, Inc. Postal: Acacia Networks, Inc.
650 Suffolk St. 650 Suffolk St.
Lowell, MA 01854 Lowell, MA 01854
USA USA
Phone: +1 (978) 275 0662 Phone: +1 (978) 275 0662
Email: plangille@acacianet.com Email: plangille@acacianet.com
Anil Rijhsinghani Anil Rijhsinghani
Postal: Cabletron Systems Postal: Cabletron Systems
550 King Street, LKG2-2/Y10 50 Minuteman Road
Littleton, MA 01460-1289 Andover MA 01810
USA USA
Phone: +1 (508) 486-6786 Phone: +1 (978) 684-1295
Email: Anil.Rijhsinghani@digital.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 "9807170000Z" REVISION "9810070000Z"
DESCRIPTION "Updated with revisions from June 1998 Interim DESCRIPTION "Updated with revisions from August 1998 Plenary
meeting." meeting."
::= { dot1dBridge 7 } ::= { dot1dBridge 7 }
qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 } qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 45, line 24 skipping to change at page 49, line 22
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 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."
SYNTAX INTEGER SYNTAX UInteger32
VlanId ::= TEXTUAL-CONVENTION VlanId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The 12-bit VLAN ID used in the VLAN Tag header." "The 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
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 46, line 11 skipping to change at page 50, line 10
dot1qVlanVersionNumber OBJECT-TYPE dot1qVlanVersionNumber OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
version1(1) version1(1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The version number of IEEE 802.1Q that this device "The version number of IEEE 802.1Q that this device
supports." supports."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.1.1" "IEEE 802.1Q/D11 Section 12.10.1.1"
::= { dot1qBase 1 } ::= { dot1qBase 1 }
dot1qMaxVlanId OBJECT-TYPE dot1qMaxVlanId OBJECT-TYPE
SYNTAX VlanId SYNTAX VlanId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum IEEE 802.1Q VLAN ID that this device "The maximum IEEE 802.1Q VLAN ID that this device
supports." supports."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 9.3.2.3" "IEEE 802.1Q/D11 Section 9.3.2.3"
::= { dot1qBase 2 } ::= { dot1qBase 2 }
dot1qMaxSupportedVlans OBJECT-TYPE dot1qMaxSupportedVlans OBJECT-TYPE
SYNTAX INTEGER (1..4094) SYNTAX UInteger32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of IEEE 802.1Q VLANs that this "The maximum number of IEEE 802.1Q VLANs that this
device supports." device supports."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.1.1" "IEEE 802.1Q/D11 Section 12.10.1.1"
::= { dot1qBase 3 } ::= { dot1qBase 3 }
dot1qNumVlans OBJECT-TYPE dot1qNumVlans OBJECT-TYPE
SYNTAX INTEGER (1..4094) SYNTAX UInteger32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of IEEE 802.1Q VLANs that are "The current number of IEEE 802.1Q VLANs that are
configured in this device." configured in this device."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.7.1.1" "IEEE 802.1Q/D11 Section 12.7.1.1"
::= { dot1qBase 4 } ::= { dot1qBase 4 }
dot1qGvrpStatus OBJECT-TYPE dot1qGvrpStatus OBJECT-TYPE
SYNTAX EnabledStatus SYNTAX EnabledStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative status requested by management for "The administrative status requested by management for
GVRP. The value enabled(1) indicates that GVRP should GVRP. The value enabled(1) indicates that GVRP should
be enabled on this device, on all ports for which it has be enabled on this device, on all ports for which it has
skipping to change at page 48, line 4 skipping to change at page 51, line 47
::= { dot1qTp 2 } ::= { dot1qTp 2 }
dot1qFdbEntry OBJECT-TYPE dot1qFdbEntry OBJECT-TYPE
SYNTAX Dot1qFdbEntry SYNTAX Dot1qFdbEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a specific Filtering Database." "Information about a specific Filtering Database."
INDEX { dot1qFdbId } INDEX { dot1qFdbId }
::= { dot1qFdbTable 1 } ::= { dot1qFdbTable 1 }
Dot1qFdbEntry ::= Dot1qFdbEntry ::=
SEQUENCE { SEQUENCE {
dot1qFdbId dot1qFdbId
INTEGER, UInteger32,
dot1qFdbDynamicCount dot1qFdbDynamicCount
Counter32 Counter32
} }
dot1qFdbId OBJECT-TYPE dot1qFdbId OBJECT-TYPE
SYNTAX INTEGER SYNTAX UInteger32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identity of this Filtering Database." "The identity of this Filtering Database."
::= { dot1qFdbEntry 1 } ::= { dot1qFdbEntry 1 }
dot1qFdbDynamicCount OBJECT-TYPE dot1qFdbDynamicCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of dynamic entries in this "The current number of dynamic entries in this
Filtering Database." Filtering Database."
REFERENCE REFERENCE
"IEEE 802.1Q/D10: Section 12.7.1.1.3" "IEEE 802.1Q/D11 Section 12.7.1.1.3"
::= { dot1qFdbEntry 2 } ::= { dot1qFdbEntry 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Multiple Forwarding Databases for 802.1Q Transparent devices -- Multiple Forwarding Databases for 802.1Q Transparent devices
-- This table is an alternative to the dot1dTpFdbTable, -- This table is an alternative to the dot1dTpFdbTable,
-- previously defined for 802.1D devices which only support a -- previously defined for 802.1D devices which only support a
-- single Forwarding Database. -- single Forwarding Database.
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qTpFdbTable OBJECT-TYPE dot1qTpFdbTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qTpFdbEntry SYNTAX SEQUENCE OF Dot1qTpFdbEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains information about unicast entries "A table that contains information about unicast entries
for which the device has forwarding and/or filtering for which the device has forwarding and/or filtering
information. This information is used by the information. This information is used by the
transparent bridging function in determining how to transparent bridging function in determining how to
propagate a received frame." propagate a received frame."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.7.7" "IEEE 802.1Q/D11 Section 12.7.7"
::= { dot1qTp 3 } ::= { dot1qTp 3 }
dot1qTpFdbEntry OBJECT-TYPE dot1qTpFdbEntry OBJECT-TYPE
SYNTAX Dot1qTpFdbEntry SYNTAX Dot1qTpFdbEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a specific unicast MAC address for "Information about a specific unicast MAC address for
which the device has some forwarding and/or filtering which the device has some forwarding and/or filtering
information." information."
skipping to change at page 51, line 35 skipping to change at page 55, line 34
a specific Group destination address, are allowed to be a specific Group destination address, are allowed to be
forwarded. The subset of these ports learnt dynamically forwarded. The subset of these ports learnt dynamically
is also provided." is also provided."
INDEX { dot1qVlanIndex, dot1qTpGroupAddress } INDEX { dot1qVlanIndex, dot1qTpGroupAddress }
::= { dot1qTpGroupTable 1 } ::= { dot1qTpGroupTable 1 }
Dot1qTpGroupEntry ::= Dot1qTpGroupEntry ::=
SEQUENCE { SEQUENCE {
dot1qTpGroupAddress dot1qTpGroupAddress
MacAddress, MacAddress,
dot1qTpGroupAllowedToGoTo dot1qTpGroupEgressPorts
PortList, PortList,
dot1qTpGroupLearnt dot1qTpGroupLearnt
PortList PortList
} }
dot1qTpGroupAddress OBJECT-TYPE dot1qTpGroupAddress OBJECT-TYPE
SYNTAX MacAddress SYNTAX MacAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination Group MAC address in a frame to which "The destination Group MAC address in a frame to which
this entry's filtering information applies." this entry's filtering information applies."
::= { dot1qTpGroupEntry 1 } ::= { dot1qTpGroupEntry 1 }
dot1qTpGroupAllowedToGoTo OBJECT-TYPE
dot1qTpGroupEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The complete set of ports, in this Filtering Database, "The complete set of ports, in this Filtering Database,
to which frames destined for this Group MAC address are to which frames destined for this Group MAC address are
allowed to be forwarded." currently being explicitly forwarded. This does not
include ports for which this address is only implicitly
forwarded, in the dot1qForwardAllPorts list."
::= { dot1qTpGroupEntry 2 } ::= { dot1qTpGroupEntry 2 }
dot1qTpGroupLearnt OBJECT-TYPE dot1qTpGroupLearnt OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subset of ports in dot1qTpGroupAllowedToGoTo which "The subset of ports in dot1qTpGroupEgressPorts which
were learnt by GMRP or some other dynamic mechanism, in were learnt by GMRP or some other dynamic mechanism, in
this Filtering database." this Filtering database."
::= { dot1qTpGroupEntry 3 } ::= { dot1qTpGroupEntry 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Service Requirements Group -- Service Requirements Group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qForwardAllTable OBJECT-TYPE dot1qForwardAllTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qForwardAllEntry SYNTAX SEQUENCE OF Dot1qForwardAllEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing forwarding information for each "A table containing forwarding information for each
VLAN, specifying the set of ports to which forwarding of VLAN, specifying the set of ports to which forwarding of
all multicasts applies, configured statically by all multicasts applies, configured statically by
management or dynamically by GMRP. An entry appears in management or dynamically by GMRP. An entry appears in
this table for all VLANs that are currently this table for all VLANs that are currently
instantiated." instantiated."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.7.2, 12.7.7" "IEEE 802.1Q/D11 Section 12.7.2, 12.7.7"
::= { dot1qTp 5 } ::= { dot1qTp 5 }
dot1qForwardAllEntry OBJECT-TYPE dot1qForwardAllEntry OBJECT-TYPE
SYNTAX Dot1qForwardAllEntry SYNTAX Dot1qForwardAllEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Forwarding information for a VLAN, specifying the set "Forwarding information for a VLAN, specifying the set
of ports to which all multicasts should be forwarded, of ports to which all multicasts should be forwarded,
configured statically by management or dynamically by configured statically by management or dynamically by
skipping to change at page 53, line 40 skipping to change at page 57, line 42
dot1qForwardAllStaticPorts OBJECT-TYPE dot1qForwardAllStaticPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports configured by management in this VLAN "The set of ports configured by management in this VLAN
to which all multicast group-addressed frames are to be to which all multicast group-addressed frames are to be
forwarded. Ports entered in this list will also appear forwarded. Ports entered in this list will also appear
in the complete set shown by dot1qForwardAllPorts. This in the complete set shown by dot1qForwardAllPorts. This
value will be restored after the device is reset. value will be restored after the device is reset.
The default value is a string of ones of appropriate This only applies to ports that are members of the VLAN,
length, to indicate standard non-EFS behaviour, i.e. defined by dot1qVlanCurrentEgressPorts. The default
forward all multicasts to all ports." value is a string of ones of appropriate length, to
indicate standard non-EFS behaviour, i.e. forward all
multicasts to all ports."
::= { dot1qForwardAllEntry 2 } ::= { dot1qForwardAllEntry 2 }
dot1qForwardUnregisteredTable OBJECT-TYPE dot1qForwardUnregisteredTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qForwardUnregisteredEntry SYNTAX SEQUENCE OF Dot1qForwardUnregisteredEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing forwarding information for each "A table containing forwarding information for each
VLAN, specifying the set of ports to which forwarding of VLAN, specifying the set of ports to which forwarding of
multicast group-addressed frames for which there is no multicast group-addressed frames for which there is no
more specific forwarding information applies. This is more specific forwarding information applies. This is
configured statically by management and determined configured statically by management and determined
dynamically by GMRP. An entry appears in this table for dynamically by GMRP. An entry appears in this table for
all VLANs that are currently instantiated." all VLANs that are currently instantiated."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.7.2, 12.7.7" "IEEE 802.1Q/D11 Section 12.7.2, 12.7.7"
::= { dot1qTp 6 } ::= { dot1qTp 6 }
dot1qForwardUnregisteredEntry OBJECT-TYPE dot1qForwardUnregisteredEntry OBJECT-TYPE
SYNTAX Dot1qForwardUnregisteredEntry SYNTAX Dot1qForwardUnregisteredEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Forwarding information for a VLAN, specifying the set "Forwarding information for a VLAN, specifying the set
of ports to which all multicasts for which there is no of ports to which all multicasts for which there is no
more specific forwarding information shall be forwarded. more specific forwarding information shall be forwarded.
skipping to change at page 55, line 43 skipping to change at page 59, line 49
specifying the set of ports to which frames received specifying the set of ports to which frames received
from specific ports and containing specific unicast from specific ports and containing specific unicast
destination addresses are allowed to be forwarded. A destination addresses are allowed to be forwarded. A
value of zero in this table as the port number from value of zero in this table as the port number from
which frames with a specific destination address are which frames with a specific destination address are
received, is used to specify all ports for which there received, is used to specify all ports for which there
is no specific entry in this table for that particular is no specific entry in this table for that particular
destination address. Entries are valid for unicast destination address. Entries are valid for unicast
addresses only." addresses only."
REFERENCE REFERENCE
"IEEE 802.1Q/D10 12.7.7, 802.1D/D16 7.9.1" "IEEE 802.1Q/D11 Section 12.7.7,
ISO/IEC 15802-3 Section 7.9.1"
::= { dot1qStatic 1 } ::= { dot1qStatic 1 }
dot1qStaticUnicastEntry OBJECT-TYPE dot1qStaticUnicastEntry OBJECT-TYPE
SYNTAX Dot1qStaticUnicastEntry SYNTAX Dot1qStaticUnicastEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Filtering information configured into the device by "Filtering information configured into the device by
(local or network) management specifying the set of (local or network) management specifying the set of
ports to which frames received from a specific port and ports to which frames received from a specific port and
skipping to change at page 57, line 13 skipping to change at page 61, line 18
entry's filtering information to apply. A value of zero entry's filtering information to apply. A value of zero
indicates that this entry applies on all ports of the indicates that this entry applies on all ports of the
device for which there is no other applicable entry." device for which there is no other applicable entry."
::= { dot1qStaticUnicastEntry 2 } ::= { dot1qStaticUnicastEntry 2 }
dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports to which frames received from a "The set of ports a specific unicast address may be
specific port and destined for a specific unicast MAC dynamically learnt on. The dot1qTpFdbTable will have an
address are allowed to be forwarded. The default value equivalent entry with a dot1qTpFdbPort value of '0'
of this object is a string of ones of appropriate until this address has been learnt, when it will be
updated with the port the address has been seen on.
This only applies to ports that are members of the VLAN,
defined by dot1qVlanCurrentEgressPorts. The default
value of this object is a string of ones of appropriate
length." length."
::= { dot1qStaticUnicastEntry 3 } ::= { dot1qStaticUnicastEntry 3 }
dot1qStaticUnicastStatus OBJECT-TYPE dot1qStaticUnicastStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
invalid(2), invalid(2),
permanent(3), permanent(3),
deleteOnReset(4), deleteOnReset(4),
deleteOnTimeout(5) deleteOnTimeout(5)
skipping to change at page 58, line 21 skipping to change at page 62, line 31
specifying the set of ports to which frames received specifying the set of ports to which frames received
from specific ports and containing specific Multicast from specific ports and containing specific Multicast
and Broadcast destination addresses are allowed to be and Broadcast destination addresses are allowed to be
forwarded. A value of zero in this table as the port forwarded. A value of zero in this table as the port
number from which frames with a specific destination number from which frames with a specific destination
address are received, is used to specify all ports for address are received, is used to specify all ports for
which there is no specific entry in this table for that which there is no specific entry in this table for that
particular destination address. Entries are valid for particular destination address. Entries are valid for
Multicast and Broadcast addresses only." Multicast and Broadcast addresses only."
REFERENCE REFERENCE
"IEEE 802.1Q/D10 12.7.7, 802.1D/D16 7.9.1" "IEEE 802.1Q/D11 Section 12.7.7,
ISO/IEC 15802-3 Section 7.9.1"
::= { dot1qStatic 2 } ::= { dot1qStatic 2 }
dot1qStaticMulticastEntry OBJECT-TYPE dot1qStaticMulticastEntry OBJECT-TYPE
SYNTAX Dot1qStaticMulticastEntry SYNTAX Dot1qStaticMulticastEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Filtering information configured into the device by "Filtering information configured into the device by
(local or network) management specifying the set of (local or network) management specifying the set of
ports to which frames received from this specific port ports to which frames received from this specific port
skipping to change at page 61, line 44 skipping to change at page 66, line 9
INDEX { dot1qVlanTimeMark, dot1qVlanIndex } INDEX { dot1qVlanTimeMark, dot1qVlanIndex }
::= { dot1qVlanCurrentTable 1 } ::= { dot1qVlanCurrentTable 1 }
Dot1qVlanEntry ::= Dot1qVlanEntry ::=
SEQUENCE { SEQUENCE {
dot1qVlanTimeMark dot1qVlanTimeMark
TimeFilter, TimeFilter,
dot1qVlanIndex dot1qVlanIndex
VlanIndex, VlanIndex,
dot1qVlanFdbId dot1qVlanFdbId
INTEGER, UInteger32,
dot1qVlanCurrentEgressPorts dot1qVlanCurrentEgressPorts
PortList, PortList,
dot1qVlanCurrentUntaggedPorts dot1qVlanCurrentUntaggedPorts
PortList, PortList,
dot1qVlanStatus dot1qVlanStatus
INTEGER INTEGER
} }
dot1qVlanTimeMark OBJECT-TYPE dot1qVlanTimeMark OBJECT-TYPE
SYNTAX TimeFilter SYNTAX TimeFilter
skipping to change at page 62, line 26 skipping to change at page 66, line 36
dot1qVlanIndex OBJECT-TYPE dot1qVlanIndex OBJECT-TYPE
SYNTAX VlanIndex SYNTAX VlanIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VLAN-ID or other identifier refering to this VLAN." "The VLAN-ID or other identifier refering to this VLAN."
::= { dot1qVlanEntry 2 } ::= { dot1qVlanEntry 2 }
dot1qVlanFdbId OBJECT-TYPE dot1qVlanFdbId OBJECT-TYPE
SYNTAX INTEGER (1..4095) SYNTAX UInteger32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Filtering Database used by this VLAN. This is one "The Filtering Database used by this VLAN. This is one
of the dot1qFdbId values in the dot1qFdbTable. This of the dot1qFdbId values in the dot1qFdbTable. This
value is allocated automatically by the device whenever value is allocated automatically by the device whenever
the VLAN is created: either dynamically by GVRP, or by the VLAN is created: either dynamically by GVRP, or by
management, in dot1qVlanStaticTable. Allocation of this management, in dot1qVlanStaticTable. Allocation of this
value follows the learning constraints defined for this value follows the learning constraints defined for this
VLAN in dot1qLearningConstraintsTable." VLAN in dot1qLearningConstraintsTable."
::= { dot1qVlanEntry 3 } ::= { dot1qVlanEntry 3 }
dot1qVlanCurrentEgressPorts OBJECT-TYPE dot1qVlanCurrentEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are transmitting traffic for "The set of ports which are transmitting traffic for
this VLAN as either tagged or untagged frames." this VLAN as either tagged or untagged frames."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanEntry 4 } ::= { dot1qVlanEntry 4 }
dot1qVlanCurrentUntaggedPorts OBJECT-TYPE dot1qVlanCurrentUntaggedPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are transmitting traffic for "The set of ports which are transmitting traffic for
this VLAN as untagged frames." this VLAN as untagged frames."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanEntry 5 } ::= { dot1qVlanEntry 5 }
dot1qVlanStatus OBJECT-TYPE dot1qVlanStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
permanent(2), permanent(2),
dynamicGvrp(3) dynamicGvrp(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the status of this entry. "This object indicates the status of this entry.
other(1) - this entry is currently in use but other(1) - this entry is currently in use but the
the conditions under which it will remain conditions under which it will remain so differ
so differ from the following values. from the following values.
permanent(2) - this entry, corresponding to an permanent(2) - this entry, corresponding to an entry
entry in dot1qVlanStaticTable, is currently in dot1qVlanStaticTable, is currently in use and
in use and will remain so after the next will remain so after the next reset of the
reset of the device. device. The port lists for this entry include
ports from the equivalent dot1qVlanStaticTable
entry and ports learnt dynamically.
dynamicGvrp(3) - this entry is currently in use dynamicGvrp(3) - this entry is currently in use
and will remain so until removed by GVRP." and will remain so until removed by GVRP. There
is no static entry for this VLAN and it will be
removed when the last port leaves the VLAN."
::= { dot1qVlanEntry 6 } ::= { dot1qVlanEntry 6 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The Static VLAN Database -- The Static VLAN Database
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qVlanStaticTable OBJECT-TYPE dot1qVlanStaticTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qVlanStaticEntry SYNTAX SEQUENCE OF Dot1qVlanStaticEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 64, line 24 skipping to change at page 68, line 39
::= { dot1qVlanStaticTable 1 } ::= { dot1qVlanStaticTable 1 }
Dot1qVlanStaticEntry ::= Dot1qVlanStaticEntry ::=
SEQUENCE { SEQUENCE {
dot1qVlanStaticName dot1qVlanStaticName
DisplayString, DisplayString,
dot1qVlanStaticEgressPorts dot1qVlanStaticEgressPorts
PortList, PortList,
dot1qVlanForbiddenEgressPorts dot1qVlanForbiddenEgressPorts
PortList, PortList,
dot1qVlanStaticUntagged dot1qVlanStaticUntaggedPorts
PortList, PortList,
dot1qVlanStaticRowStatus dot1qVlanStaticRowStatus
RowStatus RowStatus
} }
dot1qVlanStaticName OBJECT-TYPE dot1qVlanStaticName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..32)) SYNTAX DisplayString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
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/D9 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 1 } ::= { dot1qVlanStaticEntry 1 }
dot1qVlanStaticEgressPorts OBJECT-TYPE dot1qVlanStaticEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are permanently assigned to the "The set of ports which are permanently assigned to the
egress list for this VLAN by management. Changes to a egress list for this VLAN by management. Changes to a
bit in this object affect the per-port per-VLAN bit in this object affect the per-port per-VLAN
Registrar control for Registration Fixed for the Registrar control for Registration Fixed for the
relevant GVRP state machine on each port. The default relevant GVRP state machine on each port. The default
value of this object is a string of zeros of appropriate value of this object is a string of zeros of appropriate
length, indicating not fixed." length, indicating not fixed."
REFERENCE REFERENCE
"IEEE 802.1Q/D10 12.7.7.3, 11.2.3.2.3" "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 2 } ::= { dot1qVlanStaticEntry 2 }
dot1qVlanForbiddenEgressPorts OBJECT-TYPE dot1qVlanForbiddenEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are prohibited by management "The set of ports which are prohibited by management
from being included in the egress list for this VLAN. from being included in the egress list for this VLAN.
Changes to this object that cause a port to be included Changes to this object that cause a port to be included
or excluded affect the per-port per-VLAN Registrar or excluded affect the per-port per-VLAN Registrar
control for Registration Forbidden for the relevant control for Registration Forbidden for the relevant
GVRP state machine on each port. The default value of GVRP state machine on each port. The default value of
this object is a string of zeros of appropriate length, this object is a string of zeros of appropriate length,
excluding all ports from the forbidden set." excluding all ports from the forbidden set."
REFERENCE REFERENCE
"IEEE 802.1Q/D10 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 }
dot1qVlanStaticUntagged OBJECT-TYPE dot1qVlanStaticUntaggedPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
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 (VlanId 001) 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 cannot
support a value being set then its agent will reject the support a value being set then its agent will reject the
set operation." set operation. Attempts to set more than one VLAN to be
untagged on egress may be rejected by devices which do
not support this option."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 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-write MAX-ACCESS read-write
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
SYNTAX VlanIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The next available value for dot1qVlanIndex of a local
VLAN entry in dot1qVlanStaticTable. This will always
report values >=4096. A row creation operation in this
table for an entry with a local VlanIndex value may fail
if this value is not used as the index. This value will
automatically change when the current value is used."
::= { 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 4 } ::= { dot1qVlan 5 }
dot1qPortVlanEntry OBJECT-TYPE dot1qPortVlanEntry OBJECT-TYPE
SYNTAX Dot1qPortVlanEntry SYNTAX Dot1qPortVlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information controlling VLAN configuration for a port "Information controlling VLAN configuration for a port
on the device. This is indexed by dot1dBasePort." on the device. This is indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry } AUGMENTS { dot1dBasePortEntry }
::= { dot1qPortVlanTable 1 } ::= { dot1qPortVlanTable 1 }
Dot1qPortVlanEntry ::= Dot1qPortVlanEntry ::=
SEQUENCE { SEQUENCE {
dot1qPvid dot1qPvid
VlanId, VlanIndex,
dot1qPortAcceptableFrameTypes dot1qPortAcceptableFrameTypes
INTEGER, INTEGER,
dot1qPortIngressFiltering dot1qPortIngressFiltering
TruthValue, TruthValue,
dot1qPortGvrpStatus dot1qPortGvrpStatus
EnabledStatus, EnabledStatus,
dot1qPortGvrpFailedRegistrations dot1qPortGvrpFailedRegistrations
Counter32, Counter32,
dot1qPortGvrpLastPduOrigin dot1qPortGvrpLastPduOrigin
MacAddress MacAddress
} }
dot1qPvid OBJECT-TYPE dot1qPvid OBJECT-TYPE
SYNTAX VlanId 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." Prority-Tagged frames received on this port."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 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 Prority-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 Prority-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 incoming BPDU frames, such This control does not affect VLAN independent BPDU
as GARP and STP." frames, such as GVRP and STP. It does affect VLAN
dependent BPDU frames, such as GMRP."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.1.3" "IEEE 802.1Q/D11 Section 12.10.1.3"
DEFVAL { admitAll } DEFVAL { admitAll }
::= { dot1qPortVlanEntry 2 } ::= { dot1qPortVlanEntry 2 }
dot1qPortIngressFiltering OBJECT-TYPE dot1qPortIngressFiltering OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this is true(1) the device will discard incoming "When this is true(1) the device will discard incoming
frames for VLANs not in the port egress filters. When frames for VLANs which do not include this Port in its
false(2), the port will accept all incoming frames. Member set. When false(2), the port will accept all
incoming frames.
This control does not affect incoming BPDU frames, such This control does not affect VLAN independent BPDU
as GARP and STP." frames, such as GVRP and STP. It does affect VLAN
dependent BPDU frames, such as GMRP."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.1.4" "IEEE 802.1Q/D11 Section 12.10.1.4"
DEFVAL { false } DEFVAL { false }
::= { dot1qPortVlanEntry 3 } ::= { dot1qPortVlanEntry 3 }
dot1qPortGvrpStatus OBJECT-TYPE dot1qPortGvrpStatus OBJECT-TYPE
SYNTAX EnabledStatus SYNTAX EnabledStatus
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of GVRP operation on this port. The value "The state of GVRP operation on this port. The value
enabled(1) indicates that GVRP is enabled on this port, enabled(1) indicates that GVRP is enabled on this port,
skipping to change at page 69, line 10 skipping to change at page 73, line 44
-- 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."
REFERENCE ::= { dot1qVlan 6 }
"IEEE 802.1Q/D9: Section 12.6.1"
::= { dot1qVlan 5 }
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 }
Dot1qPortVlanStatisticsEntry ::= Dot1qPortVlanStatisticsEntry ::=
SEQUENCE { SEQUENCE {
dot1qFramesReceived dot1qTpVlanPortInFrames
Counter32,
dot1qOctetsReceived
Counter32,
dot1qForwardOutbound
Counter32,
dot1qDiscardInbound
Counter32,
dot1qDiscardNoBuffers
Counter32,
dot1qDiscardTransitDelayExceeded
Counter32, Counter32,
dot1qDiscardError dot1qTpVlanPortOutFrames
Counter32, Counter32,
dot1qDiscardOnIngressFiltering dot1qTpVlanPortInDiscards
Counter32 Counter32
} }
dot1qFramesReceived OBJECT-TYPE dot1qTpVlanPortInFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames received on this port and VLAN." "The number of valid frames received by this port from
its segment which were classified as belonging to this
VLAN. Note that a frame received on this port is
counted by this object if and only if it is for a
protocol being processed by the local forwarding process
for this VLAN. This object includes received bridge
management frames classified as belonging to this VLAN
(e.g. GMRP, but not GVRP or STP)."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(a)"
::= { dot1qPortVlanStatisticsEntry 1 } ::= { dot1qPortVlanStatisticsEntry 1 }
dot1qOctetsReceived 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 octets received on this port and VLAN." "The number of valid frames transmitted by this port to
its segment from the local forwarding process for this
VLAN. This includes bridge management frames originated
by this device whach are classified as belonging to this
VLAN (e.g. GMRP, but not GVRP or STP)."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanStatisticsEntry 2 } ::= { dot1qPortVlanStatisticsEntry 2 }
dot1qForwardOutbound OBJECT-TYPE dot1qTpVlanPortInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames forwarded from this port and "The number of valid frames received by this port from
VLAN." its segment which were classified as belonging to this
VLAN and which were discarded by the local forwarding
process for this VLAN due to filtering database
decisions. Note that this does not include frames
discarded due to ingress filtering."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(c)"
::= { dot1qPortVlanStatisticsEntry 3 } ::= { dot1qPortVlanStatisticsEntry 3 }
dot1qDiscardInbound OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of inbound frames discarded on this port and
VLAN."
::= { dot1qPortVlanStatisticsEntry 4 }
dot1qDiscardNoBuffers OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames discarded due to lack of buffers
for this port and VLAN."
::= { dot1qPortVlanStatisticsEntry 5 }
dot1qDiscardTransitDelayExceeded OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames discarded by this port and VLAN
due to excessive transit delay through the device."
::= { dot1qPortVlanStatisticsEntry 6 }
dot1qDiscardError OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames discarded by this port and VLAN
due to other errors."
::= { dot1qPortVlanStatisticsEntry 7 }
dot1qDiscardOnIngressFiltering OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames discarded by this port and VLAN
due to ingress filtering."
::= { dot1qPortVlanStatisticsEntry 8 }
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 received on high capacity interfaces."
REFERENCE ::= { dot1qVlan 7 }
"IEEE 802.1Q/D9: Section 12.6.1"
::= { dot1qVlan 6 }
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 }
::= { dot1qPortVlanHCStatisticsTable 1 } ::= { dot1qPortVlanHCStatisticsTable 1 }
Dot1qPortVlanHCStatisticsEntry ::= Dot1qPortVlanHCStatisticsEntry ::=
SEQUENCE { SEQUENCE {
dot1qHCFramesReceived dot1qTpVlanPortHCInFrames
Counter64,
dot1qHCOctetsReceived
Counter64,
dot1qHCForwardOutbound
Counter64,
dot1qHCDiscardInbound
Counter64,
dot1qHCDiscardNoBuffers
Counter64,
dot1qHCDiscardTransitDelayExceeded
Counter64, Counter64,
dot1qHCDiscardError dot1qTpVlanPortHCOutFrames
Counter64, Counter64,
dot1qHCDiscardOnIngressFiltering dot1qTpVlanPortHCInDiscards
Counter64 Counter64
} }
dot1qHCFramesReceived OBJECT-TYPE dot1qTpVlanPortHCInFrames OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames received on this port and VLAN." "The number of valid frames received by this port from
its segment which were classified as belonging to this
VLAN. Note that a frame received on this port is
counted by this object if and only if it is for a
protocol being processed by the local forwarding process
for this VLAN. This object includes received bridge
management frames classified as belonging to this VLAN
(e.g. GMRP, but not GVRP or STP)."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(a)"
::= { dot1qPortVlanHCStatisticsEntry 1 } ::= { dot1qPortVlanHCStatisticsEntry 1 }
dot1qHCOctetsReceived 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 octets received on this port and VLAN." "The number of valid frames transmitted by this port to
its segment from the local forwarding process for this
VLAN. This includes bridge management frames originated
by this device whach are classified as belonging to this
VLAN (e.g. GMRP, but not GVRP or STP)."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanHCStatisticsEntry 2 } ::= { dot1qPortVlanHCStatisticsEntry 2 }
dot1qHCForwardOutbound OBJECT-TYPE dot1qTpVlanPortHCInDiscards OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames forwarded from this port and "The number of valid frames received by this port from
VLAN." its segment which were classified as belonging to this
VLAN and which were discarded by the local forwarding
process for this VLAN due to filtering database
decisions. Note that this does not include frames
discarded due to ingress filtering."
REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(c)"
::= { dot1qPortVlanHCStatisticsEntry 3 } ::= { dot1qPortVlanHCStatisticsEntry 3 }
dot1qHCDiscardInbound OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of inbound frames discarded on this port
and VLAN."
::= { dot1qPortVlanHCStatisticsEntry 4 }
dot1qHCDiscardNoBuffers OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames discarded due to lack of buffers
for this port and VLAN."
::= { dot1qPortVlanHCStatisticsEntry 5 }
dot1qHCDiscardTransitDelayExceeded OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames discarded by this port and VLAN
due to excessive transit delay through the device."
::= { dot1qPortVlanHCStatisticsEntry 6 }
dot1qHCDiscardError OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames discarded by this port and VLAN
due to other errors."
::= { dot1qPortVlanHCStatisticsEntry 7 }
dot1qHCDiscardOnIngressFiltering OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames discarded by this port and VLAN
due to ingress filtering."
::= { dot1qPortVlanHCStatisticsEntry 8 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The VLAN Learning Constraints Table -- The VLAN Learning Constraints Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qLearningConstraintsLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the
dot1qLearningConstraintsTable was last modified,
either through insertions or deletions, or through
modifications of either the dot1qConstraintType or
dot1qConstraintStatus values."
::= { dot1qVlan 7 }
dot1qLearningConstraintsTable OBJECT-TYPE dot1qLearningConstraintsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qLearningConstraintsEntry SYNTAX SEQUENCE OF Dot1qLearningConstraintsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing learning constraints for sets of "A table containing learning constraints for sets of
Shared and Independendent VLANs." Shared and Independendent VLANs."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.3.1" "IEEE 802.1Q/D11 Section 12.10.3.1"
::= { dot1qVlan 8 } ::= { dot1qVlan 8 }
dot1qLearningConstraintsEntry OBJECT-TYPE dot1qLearningConstraintsEntry OBJECT-TYPE
SYNTAX Dot1qLearningConstraintsEntry SYNTAX Dot1qLearningConstraintsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A learning constraint defined for a VLAN." "A learning constraint defined for a VLAN."
INDEX { dot1qConstraintVlan, dot1qConstraintSet } INDEX { dot1qConstraintVlan, dot1qConstraintSet }
::= { dot1qLearningConstraintsTable 1 } ::= { dot1qLearningConstraintsTable 1 }
skipping to change at page 77, line 12 skipping to change at page 80, line 5
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing device level control "A collection of objects providing device level control
and status information for the Virtual LAN bridge and status information for the Virtual LAN bridge
services." services."
::= { qBridgeGroups 1 } ::= { qBridgeGroups 1 }
qBridgeFdbUnicastGroup OBJECT-GROUP qBridgeFdbUnicastGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qFdbDynamicCount,
dot1qTpFdbPort, dot1qTpFdbPort,
dot1qTpFdbStatus dot1qTpFdbStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about all "A collection of objects providing information about all
unicast addresses, learnt dynamically or statically unicast addresses, learnt dynamically or statically
configured by management, in each Filtering Database." configured by management, in each Filtering Database."
::= { qBridgeGroups 2 } ::= { qBridgeGroups 2 }
qBridgeFdbMulticastGroup OBJECT-GROUP qBridgeFdbMulticastGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qTpGroupAllowedToGoTo, dot1qTpGroupEgressPorts,
dot1qTpGroupLearnt dot1qTpGroupLearnt
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about all "A collection of objects providing information about all
multicast addresses, learnt dynamically or statically multicast addresses, learnt dynamically or statically
configured by management, in each Filtering Database." configured by management, in each Filtering Database."
::= { qBridgeGroups 3 } ::= { qBridgeGroups 3 }
qBridgeServiceRequirementsGroup OBJECT-GROUP qBridgeServiceRequirementsGroup OBJECT-GROUP
skipping to change at page 78, line 20 skipping to change at page 81, line 14
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
unicast and multicast addresses statically configured by unicast and multicast addresses statically configured by
management, in each Filtering Database or VLAN." management, in each Filtering Database or VLAN."
::= { qBridgeGroups 5 } ::= { qBridgeGroups 5 }
qBridgeVlanGroup OBJECT-GROUP qBridgeVlanGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qVlanNumDeletes,
dot1qVlanFdbId, dot1qVlanFdbId,
dot1qVlanCurrentEgressPorts, dot1qVlanCurrentEgressPorts,
dot1qVlanCurrentUntaggedPorts, dot1qVlanCurrentUntaggedPorts,
dot1qVlanStatus dot1qVlanStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
all VLANs currently configured on this device." all VLANs currently configured on this device."
::= { qBridgeGroups 6 } ::= { qBridgeGroups 6 }
qBridgeVlanStaticGroup OBJECT-GROUP qBridgeVlanStaticGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qVlanStaticName, dot1qVlanStaticName,
dot1qVlanStaticEgressPorts, dot1qVlanStaticEgressPorts,
dot1qVlanForbiddenEgressPorts, dot1qVlanForbiddenEgressPorts,
dot1qVlanStaticUntagged, dot1qVlanStaticUntaggedPorts,
dot1qVlanStaticRowStatus dot1qVlanStaticRowStatus,
dot1qNextFreeLocalVlanIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
VLANs statically configured by management." VLANs statically configured by management."
::= { qBridgeGroups 7 } ::= { qBridgeGroups 7 }
qBridgePortGroup OBJECT-GROUP qBridgePortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qPvid, dot1qPvid,
skipping to change at page 79, line 17 skipping to change at page 82, line 13
dot1qPortGvrpLastPduOrigin dot1qPortGvrpLastPduOrigin
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing port level VLAN "A collection of objects providing port level VLAN
control and status information for all ports." control and status information for all ports."
::= { qBridgeGroups 8 } ::= { qBridgeGroups 8 }
qBridgeVlanStatisticsGroup OBJECT-GROUP qBridgeVlanStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qOctetsReceived dot1qTpVlanPortInFrames,
} dot1qTpVlanPortOutFrames,
STATUS current dot1qTpVlanPortInDiscards
DESCRIPTION
"A collection of objects providing per-port octet
statistics for all VLANs currently configured on
this device."
::= { qBridgeGroups 9 }
qBridgeVlanPacketStatisticsGroup OBJECT-GROUP
OBJECTS {
dot1qFramesReceived,
dot1qForwardOutbound,
dot1qDiscardInbound,
dot1qDiscardNoBuffers,
dot1qDiscardTransitDelayExceeded,
dot1qDiscardError,
dot1qDiscardOnIngressFiltering
} }
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." device."
::= { qBridgeGroups 10 } ::= { qBridgeGroups 9 }
qBridgeVlanHCStatisticsGroup OBJECT-GROUP qBridgeVlanHCStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qHCOctetsReceived dot1qTpVlanPortHCInFrames,
} dot1qTpVlanPortHCOutFrames,
STATUS current dot1qTpVlanPortHCInDiscards
DESCRIPTION
"A collection of objects providing per-port octet count
statistics for all VLANs currently configured on this
device for high capacity interfaces."
::= { qBridgeGroups 11 }
qBridgeVlanHCPacketStatisticsGroup OBJECT-GROUP
OBJECTS {
dot1qHCFramesReceived,
dot1qHCForwardOutbound,
dot1qHCDiscardInbound,
dot1qHCDiscardNoBuffers,
dot1qHCDiscardTransitDelayExceeded,
dot1qHCDiscardError,
dot1qHCDiscardOnIngressFiltering
} }
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."
::= { qBridgeGroups 12 } ::= { qBridgeGroups 10 }
qBridgeLearningConstraintsGroup OBJECT-GROUP qBridgeLearningConstraintsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qConstraintType, dot1qConstraintType,
dot1qConstraintStatus, dot1qConstraintStatus
dot1qLearningConstraintsLastChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the Filtering Database "A collection of objects defining the Filtering Database
constraints all VLANs have with each other." constraints all VLANs have with each other."
::= { qBridgeGroups 13 } ::= { qBridgeGroups 11 }
qBridgeLearningConstraintDefaultGroup OBJECT-GROUP qBridgeLearningConstraintDefaultGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qConstraintSetDefault, dot1qConstraintSetDefault,
dot1qConstraintTypeDefault dot1qConstraintTypeDefault
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the default Filtering "A collection of objects defining the default Filtering
Database constraints for VLANs which have no specific Database constraints for VLANs which have no specific
constraints defined." constraints defined."
::= { qBridgeGroups 14 } ::= { qBridgeGroups 12 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- compliance statements -- compliance statements
-- ------------------------------------------------------------- -- -------------------------------------------------------------
qBridgeCompliance MODULE-COMPLIANCE qBridgeCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for device support of Virtual "The compliance statement for device support of Virtual
LAN Bridge services." LAN Bridge services."
MODULE MODULE
MANDATORY-GROUPS { MANDATORY-GROUPS {
qBridgeBaseGroup, qBridgeBaseGroup,
qBridgeVlanGroup, qBridgeVlanGroup,
qBridgeVlanStaticGroup, qBridgeVlanStaticGroup,
qBridgePortGroup qBridgePortGroup
} }
GROUP qBridgeFdbGroup
DESCRIPTION
"This group is optional."
GROUP qBridgeTpFdbGroup
DESCRIPTION
"This group is optional."
GROUP qBridgeFdbUnicastGroup GROUP qBridgeFdbUnicastGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for bridges that implement "This group is mandatory for bridges that implement
802.1Q transparent bridging." 802.1Q transparent bridging."
GROUP qBridgeFdbMulticastGroup GROUP qBridgeFdbMulticastGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for bridges that implement "This group is mandatory for bridges that implement
802.1Q transparent bridging." 802.1Q transparent bridging."
skipping to change at page 81, line 46 skipping to change at page 84, line 4
DESCRIPTION DESCRIPTION
"This group is mandatory for bridges that implement "This group is mandatory for bridges that implement
802.1Q transparent bridging." 802.1Q transparent bridging."
GROUP qBridgeServiceRequirementsGroup GROUP qBridgeServiceRequirementsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for bridges that implement "This group is mandatory for bridges that implement
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."
GROUP qBridgeVlanPacketStatisticsGroup
DESCRIPTION
"This group is optional but should be implemented if
qBridgeVlanStatisticsGroup is implemented."
GROUP qBridgeVlanHCStatisticsGroup GROUP qBridgeVlanHCStatisticsGroup
DESCRIPTION DESCRIPTION
"This group is optional. It should be implemented "This group is optional."
if qBridgeVlanStatisticsGroup is implemented and if
the network interface to which this bridge port is
attached has the value of the corresponding instance
of ifSpeed greater than 20,000,000 bits/second."
GROUP qBridgeVlanHCPacketStatisticsGroup
DESCRIPTION
"This group is optional. It should be implemented
if qBridgeVlanPacketStatisticsGroup is implemented
and if the network interface to which this bridge
port is attached has the value of the corresponding
instance of ifSpeed greater than 650,000,000
bits/second."
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."
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."
OBJECT dot1qForwardAllPorts
MIN-ACCESS not-accessible
DESCRIPTION
"Access is only required if extended filtering
services are supported."
OBJECT dot1qForwardAllStaticPorts
MIN-ACCESS not-accessible
DESCRIPTION
"Access is only required if extended filtering
services are supported."
OBJECT dot1qForwardUnregisteredPorts
MIN-ACCESS not-accessible
DESCRIPTION
"Access is only required if extended filtering
services are supported."
OBJECT dot1qForwardUnregisteredStaticPorts
MIN-ACCESS not-accessible
DESCRIPTION
"Access is only required if extended filtering
services are supported."
OBJECT dot1qPortAcceptableFrameTypes OBJECT dot1qPortAcceptableFrameTypes
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dot1qPortIngressFiltering OBJECT dot1qPortIngressFiltering
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 83, line 44 skipping to change at page 85, line 4
OBJECT dot1qConstraintSetDefault OBJECT dot1qConstraintSetDefault
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dot1qConstraintTypeDefault OBJECT dot1qConstraintTypeDefault
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { qBridgeCompliances 1 } ::= { qBridgeCompliances 1 }
END END
8. Acknowledgments 8. Acknowledgments
This document expands upon previous work which resulted in RFC1493. This document expands upon previous work which resulted in RFC1493.
Much of the groundwork for this document was performed by the IEEE Much of the groundwork for this document was performed by the IEEE 802.1
802.1 working group during the definition of the IEEE 802.1D updates working group during the definition of the IEEE 802.1D updates [19] and
[12] and IEEE 802.1Q [13]. Some ideas were also taken from an IEEE 802.1Q [20].
earlier Internet Draft for a VLAN MIB [16] from I. Jeyasubramanian.
The authors wish to thank the members of the Bridge Working Group for The authors wish to thank the members of the Bridge Working Group for
their many comments and suggestions which improved this effort. their many comments and suggestions which improved this effort.
9. References 9. References
[1] Cerf, V., "IAB Recommendations for the Development of Internet [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Network Management Standards", RFC 1052, April 1988. Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998
[2] Cerf, V., "Report of the Second Ad Hoc Network Management Review [2] Rose, M., and K. McCloghrie, "Structure and Identification of
Group", RFC 1109, August 1989. Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990
[3] Rose M., and K. McCloghrie, "Structure and Identification of [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
Management Information for TCP/IP-based internets", STD 16, RFC Performance Systems International, Hughes LAN Systems, March 1991
1155, May 1990.
[4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
Network Management Protocol", STD 15, RFC 1157, May 1990. RFC 1215, Performance Systems International, March 1991
[5] McCloghrie K., and M. Rose, Editors, "Management Information [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
Base for Network Management of TCP/IP-based internets", STD 17, of Management Information for Version 2 of the Simple Network
RFC 1213, March 1991. Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[6] Information processing systems - Open Systems Interconnection - [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
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
Statements for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2274, IBM T. J. Watson Research, January 1998.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998
[16] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1), Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization, International International Organization for Standardization, International
Standard 8824, December 1987. Standard 8824, December 1987.
[7] Information processing systems - Open Systems Interconnection - [17] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation One Specification of Basic Encoding Rules for Abstract Notation One
(ASN.1), International Organization for Standardization, (ASN.1), International Organization for Standardization,
International Standard 8825, December 1987. International Standard 8825, December 1987.
[8] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions", [18] ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges".
STD 16, RFC 1212, March 1991.
[9] Rose, M., Editor, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[10] ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges".
[11] ISO/IEC Final CD 15802-3, ANSI/IEEE Std 802.1D-1998 "Information [19] ISO/IEC Final CD 15802-3, ANSI/IEEE Std 802.1D-1998 "Information
technology - Telecommunications and information exchange between technology - Telecommunications and information exchange between
systems - Local and metropolitan area networks - Common systems - Local and metropolitan area networks - Common
specifications - Part 3: Media Access Control (MAC) Bridges: specifications - Part 3: Media Access Control (MAC) Bridges:
Revision (Incorporating IEEE P802.1p: Traffic Class Expediting Revision (Incorporating IEEE P802.1p: Traffic Class Expediting and
and Dynamic Multicast Filtering)", March 1998. Dynamic Multicast Filtering)", May 1998.
[12] ANSI/IEEE Draft Standard P802.1Q/D10, "IEEE Standards for Local [20] ANSI/IEEE Draft Standard P802.1Q/D11, "IEEE Standards for Local and
and Metropolitan Area Networks: Virtual Bridged Local Area Metropolitan Area Networks: Virtual Bridged Local Area Networks",
Networks", March 1998. July 1998.
[13] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K., [21] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K.,
"Definitions of Managed Objects for Bridges", RFC 1493, July "Definitions of Managed Objects for Bridges", RFC 1493, cisco
1993. Systems, Digital Equipment, Hughes LAN Systems, July 1993.
[14] McCloghrie, K., Kastenholz, F. "Evolution of the Interfaces [22] McCloghrie, K., Kastenholz, F. "Evolution of the Interfaces Group
Group of MIB-II", RFC 1573, January 1994. of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, January
1994.
[15] Decker, E., McCloghrie, K., Langille, P., Rijsinghani, A. [23] Decker, E., McCloghrie, K., Langille, P., Rijsinghani, A.
"Definitions of Managed Objects for Source Routing Bridges", RFC "Definitions of Managed Objects for Source Routing Bridges", RFC
1525, September 1993 1525, cisco Systems, Hughes LAN Systems, Digital Equipment,
September 1993
[16] Jeyasubramanian, I., "Definitions of Managed Objects for IEEE
802.1Q Virtual LAN Bridges", draft-jeya-vlan-8021q-mib-01.txt,
June 1997
[17] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[18] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [24] McCloghrie K., and M. Rose, Editors, "Management Information Base
Waldbusser, "Structure of Management Information for version 2 for Network Management of TCP/IP-based internets", STD 17, RFC
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1213, Hughes LAN Systems, Performance Systems International, March
January 1996. 1991.
[19] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 10. Security Considerations
Waldbusser, "Textual Conventions for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[20] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. There are a number of management objects defined in this MIB that have a
Waldbusser, "Conformance Statements for version 2 of the Simple MAX-ACCESS clause of read-write and/or read-create. Such objects may be
Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 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.
10. Security Considerations SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB.
Certain management information defined in this MIB may be considered It is recommended that the implementers consider the security features
sensitive in some network environments. Therefore, authentication of as provided by the SNMPv3 framework. Specifically, the use of the
received SNMP requests and controlled access to management User-based Security Model RFC 2274 [12] and the View-based Access
information should be employed in such environments. The method for Control Model RFC 2275 [15] is recommended.
this authentication is a function of the SNMP Administrative
Framework, and has not been expanded by this MIB.
Several objects in this MIB allow write access. Setting these It is then a customer/user responsibility to ensure that the SNMP entity
objects can have a serious effect on the operation of the network, giving access to an instance of this MIB, is properly configured to give
including enabling or disabling forwarding of data. It is access to the objects only to those principals (users) that have
recommended that implementers seriously consider whether set legitimate rights to indeed GET or SET (change/create/delete) them.
operations should be allowed without providing, at a minimum,
authentication of request origin.
11. Authors' Addresses 11. Authors' Addresses
Les Bell Les Bell
3Com Europe Limited 3Com Europe Limited
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
+44 (1442) 438025 +44 (1442) 438025
skipping to change at page 88, line 34 skipping to change at page 91, line 34
Paul Langille Paul Langille
Acacia Networks, Inc. Acacia Networks, Inc.
650 Suffolk St. 650 Suffolk St.
Lowell, MA 01854 Lowell, MA 01854
USA USA
+1 (978) 275 0662 +1 (978) 275 0662
plangille@acacianet.com plangille@acacianet.com
Anil Rijhsinghani Anil Rijhsinghani
Cabletron Systems Cabletron Systems
550 King Street, LKG2-2/Y10 50 Minuteman Road
Littleton, MA 01460-1289 Andover MA 01810
USA USA
+1 (508) 486-6786 +1 (978) 684-1295
Anil.Rijhsinghani@digital.com anil@cabletron.com
Keith McCloghrie Keith McCloghrie
cisco Systems, Inc. cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
USA USA
+1 (408) 526 5260 +1 (408) 526 5260
kzm@cisco.com kzm@cisco.com
Table of Contents Table of Contents
1 The SNMP Network Management Framework ........................ 2 1 The SNMP Management Framework ................................... 2
1.1 Object Definitions ......................................... 2 2 Overview ........................................................ 4
2 Overview ..................................................... 3 2.1 Scope ......................................................... 4
2.1 Scope ...................................................... 3 3 Structure of MIBs ............................................... 5
3 Structure of MIBs ............................................ 4 3.1 Structure of Extended Bridge MIB module ....................... 5
3.1 Structure of Extended Bridge MIB module .................... 5 3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ......... 6
3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ...... 5 3.1.2 Relationship to IEEE 802.1Q Manageable Objects .............. 7
3.1.2 The dot1dExtBase Group ................................... 6 3.1.3 The dot1dExtBase Group ...................................... 8
3.1.3 The dot1dPriority Group .................................. 6 3.1.4 The dot1dPriority Group ..................................... 8
3.1.4 The dot1dGarp Group ...................................... 7 3.1.5 The dot1dGarp Group ......................................... 8
3.1.5 The dot1dGmrp Group ...................................... 7 3.1.6 The dot1dGmrp Group ......................................... 8
3.1.6 The dot1dHCPort Group .................................... 7 3.1.7 The dot1dHCPortTable ........................................ 8
3.2 Structure of Virtual Bridge MIB module ..................... 7 3.2 Structure of Virtual Bridge MIB module ........................ 9
3.2.1 Relationship to IEEE 802.1Q Manageable Objects ........... 7 3.2.1 Relationship to IEEE 802.1Q Manageable Objects .............. 9
3.2.2 The dot1qBase Group ...................................... 11 3.2.2 The dot1qBase Group ......................................... 12
3.2.3 The dot1qTp Group ........................................ 11 3.2.3 The dot1qTp Group ........................................... 12
3.2.4 The dot1qStatic Group .................................... 11 3.2.4 The dot1qStatic Group ....................................... 12
3.2.5 The dot1qVlan Group ...................................... 12 3.2.5 The dot1qVlan Group ......................................... 13
3.3 Textual Conventions ........................................ 12 3.3 Textual Conventions ........................................... 13
3.4 Relationship to Other MIBs ................................. 12 3.4 Relationship to Other MIBs .................................... 13
3.4.1 Relationship to the 'system' group ....................... 12 3.4.1 Relationship to the 'system' group .......................... 13
3.4.2 Relation to Interfaces MIB ............................... 13 3.4.2 Relation to Interfaces MIB .................................. 14
3.4.2.1 Layering Model ......................................... 14 3.4.2.1 Layering Model ............................................ 15
3.4.2.2 ifStackTable ........................................... 14 3.4.2.2 ifStackTable .............................................. 15
3.4.2.3 ifRcvAddressTable ...................................... 15 3.4.2.3 ifRcvAddressTable ......................................... 15
3.4.3 Relation to Basic Bridge MIB ............................. 15 3.4.3 Relation to Basic Bridge MIB ................................ 16
3.4.3.1 The dot1dBase Group .................................... 15 3.4.3.1 The dot1dBase Group ....................................... 16
3.4.3.2 The dot1dStp Group ..................................... 15 3.4.3.2 The dot1dStp Group ........................................ 16
3.4.3.3 The dot1dTp Group ...................................... 15 3.4.3.3 The dot1dTp Group ......................................... 16
3.4.3.4 The dot1dStatic Group .................................. 16 3.4.3.4 The dot1dStatic Group ..................................... 17
4 Extensions to RFC 1493 ....................................... 17 4 Extensions to RFC 1493 .......................................... 18
5 Change Log and Editorial Stuff ............................... 17 5 Change Log and Editorial Stuff .................................. 18
5.1 Changes since draft-ietf-bridge-bridgemib-00.txt ........... 17 5.1 Changes since draft-ietf-bridge-bridgemib-01.txt .............. 18
5.2 To Do List ................................................. 18 5.2 Open Issues ................................................... 20
5.3 Open Issues ................................................ 19 5.3 Issues closed in this draft ................................... 20
5.4 Issues closed in this draft ................................ 22 5.4 Issues closed in previous drafts .............................. 23
5.5 Issues closed in previous drafts ........................... 23 6 Definitions for Extended Bridge MIB ............................. 28
6 Definitions for Extended Bridge MIB .......................... 25 7 Definitions for Virtual Bridge MIB .............................. 47
7 Definitions for Virtual Bridge MIB ........................... 43 8 Acknowledgments ................................................. 86
8 Acknowledgments .............................................. 84 9 References ...................................................... 87
9 References ................................................... 85 10 Security Considerations ........................................ 90
10 Security Considerations ..................................... 87 11 Authors' Addresses ............................................. 91
11 Authors' Addresses .......................................... 88
Copyright (C) The Internet Society (date). All Rights Reserved. Copyright (C) The Internet Society (date). 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 others, and derivative works that comment on or otherwise to others, and derivative works that comment on or otherwise
explain it or assist in its implmentation may be prepared, copied, explain it or assist in its implmentation may be prepared, copied,
published and distributed, in whole or in part, without published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the way, such as by removing the copyright notice or references to the
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/