draft-ietf-bridge-bridgemib-00.txt   draft-ietf-bridge-bridgemib-01.txt 
Internet Draft Les Bell Internet Draft E.L. Bell
Expires October 1998 3Com Corp. Expires February 1999 3Com Corp.
draft-ietf-bridge-bridgemib-00.txt Andrew Smith draft-ietf-bridge-bridgemib-01.txt A. Smith
Extreme Networks Standards Track Extreme Networks
Paul Langille P. Langille
Acacia Networks Acacia Networks
Anil Rijsinghani A. Rijhsinghani
Cabletron Systems Cabletron Systems
Keith McCloghrie K. McCloghrie
cisco Systems cisco Systems
April 1998 August 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 its Working Groups. Note that other groups may also distribute and its Working Groups. Note that other groups may also distribute
working documents as Internet Drafts. working 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. Internet Drafts may be updated, replaced, or obsoleted by months. Internet Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet other documents at any time. It is not appropriate to use Internet
Drafts as reference material or to cite them other than as a "working Drafts as reference material or to cite them other than as a "working
draft" or "work in progress." draft" or "work in progress."
To view the entire list of current Internet-Drafts, please check To learn the current status of any Internet-Draft, please check the
the "1id-abstracts.txt" listing contained in the Internet-Drafts "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net Directories on ds.internic.net (US East Coast), nic.nordu.net
(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu Rim).
(US West Coast).
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.
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 use with network management protocols in TCP/IP based internets. for use with network management protocols in TCP/IP based internets.
In particular it defines objects for managing MAC bridges based on In particular it defines objects for managing MAC bridges based on
the IEEE 802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN the IEEE 802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN
(VLAN) standards for bridging between Local Area Network (LAN) (VLAN) standards for bridging between Local Area Network (LAN)
segments. Provisions are made for support of transparent bridging. segments. Provisions are made for support of transparent bridging.
Provisions are also made so that these objects apply to bridges Provisions are also made so that these objects apply to bridges
skipping to change at page 3, line 39 skipping to change at page 3, line 39
bridging entity operating in the transparent mode, as well as some bridging entity operating in the transparent mode, as well as some
objects applicable to all types of bridges. Managed objects for objects applicable to all types of bridges. Managed objects for
Source-Routing are defined in [15]. Source-Routing are defined in [15].
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 to match the set defined in IEEE 802.1D and IEEE 802.1Q. attempts to match the set defined in IEEE 802.1D and IEEE 802.1Q.
However, to be consistent with the spirit of the SNMP Framework, a However, to be consistent with the spirit of the SNMP Framework, a
subjective judgement was made to omit the objects from those subjective judgement was made to omit the objects from those
standards most 'costly' to implement in an agent and least omissions standards most 'costly' to implement in an agent and least
'essential' for fault and configuration 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 object in the BRIDGE-MIB module: an object in the BRIDGE-MIB module:
(1) Start with a small set of essential objects and add only as (1) Start with a small set of essential objects and add only as
further objects are needed. further objects are needed.
skipping to change at page 4, line 22 skipping to change at page 4, line 25
(5) Exclude objects which are simply derivable from others in this (5) Exclude objects which are simply derivable from others in this
or other MIBs. or 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 layer. per layer.
3. Structure of MIBs 3. Structure of MIBs
This document defines additional objects, on top of those existing in This document defines additional objects, on top of those existing in
the base BRIDGE-MIB module from defined in RFC1493: that MIB module the base BRIDGE-MIB module defined in RFC1493: that MIB module is
is maintained unchanged for backwards compatibility. Section 3.4.3 maintained unchanged for backwards compatibility. Section 3.4.3 of
of the present document contains some recommendations regarding usage the present document contains some recommendations regarding usage of
of objects in RFC1493 by devices implementing the enhancements objects in RFC1493 by devices implementing the enhancements defined
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 the traffic class and multicast filtering enhancements for the traffic class and multicast filtering enhancements
defined by IEEE 802.1D-1998. defined by IEEE 802.1D-1998.
(2) Managed objects for a virtual bridge MIB modeul 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 as a set of related objects. The overall structure and organized as a set of related objects. The overall structure and
assignment of objects to their groups is shown below. assignment of objects to their groups is shown below.
3.1.1. Relationship to IEEE 802.1D-1998 Manageable Objects 3.1.1. Relationship to IEEE 802.1D-1998 Manageable Objects
This section contains a cross-reference to the objects defined in This section contains a cross-reference to the objects defined in
IEEE 802.1D-1998 [11]. It also details those objects that are not IEEE 802.1D-1998 [11]. It also details those objects that are not
considered necessary in this MIB module. considered necessary in this MIB module.
Some objects defined by [11] have been included in the virtual bridge Some objects defined by [11] have been included in the virtual bridge
MIB module rather than this one: dot1qTpGroupTable and MIB module rather than this one: entries in dot1qTpGroupTable,
dot1qServiceReqTable are required for virtual bridged LANs with dot1qForwardAllTable and dot1qForwardUnregisteredTable are required
additional indexing e.g. per-VLAN, per-FDB and so are not defined for virtual bridged LANs with additional indexing (e.g. per-VLAN,
here. Instead, devices which do not implement virtual bridged LANs, per-FDB) and so are not defined here. Instead, devices which do not
should implement these tables with a fixed value for dot1qFdbId (the implement virtual bridged LANs, should implement these tables with a
value 1 is recommended). Devices which support dynamic learning of fixed value for dot1qFdbId (the value 1 is recommended) or
Multicast Group Addresses in the Filtering Database should support dot1qVlanIndex (the value 1 is recommended). Devices which support
dot1qTpGroupTable. Devices which support static or dynamic learning Extended Filtering Services (dynamic learning of Multicast Group
of Multicast Group Service Requirements should support Addresses and Group Service Requirements in the Filtering Database)
dot1qServiceReqTable. should support dot1qTpGroupTable, dot1qForwardAllTable and
dot1qForwardUnregisteredTable.
Extended Bridge MIB Name IEEE 802.1D Name Extended Bridge MIB Name IEEE 802.1D Name
dot1dExtended Bridge dot1dExtended Bridge
dot1dExtBase dot1dExtBase
dot1dDeviceCapabilities
dot1dTrafficClassesEnabled dot1dTrafficClassesEnabled
dot1dTrafficClassesResetToDefaults dot1dGmrpStatus
dot1dGmrpAdminStatus .ApplicantAdministrativeControl .ApplicantAdministrativeControl
dot1dGarpReset dot1dPortCapabilitiesTable
dot1dPortCapabilities
dot1dPriority dot1dPriority
dot1dPortPriorityTable dot1dPortPriorityTable
dot1dPortDefaultUserPriority .UserPriority dot1dPortDefaultUserPriority .UserPriority
dot1dPortNumTrafficClasses dot1dPortNumTrafficClasses
dot1dUserPriorityRegenTable .UserPriorityRegenerationTable dot1dUserPriorityRegenTable .UserPriorityRegenerationTable
dot1dUserPriority dot1dUserPriority
dot1dRegenUserPriority dot1dRegenUserPriority
dot1dTrafficClassTable .TrafficClassTable dot1dTrafficClassTable .TrafficClassTable
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
dot1dPortGmrpAdminStatus .ApplicantAdministrativeControl dot1dPortGmrpStatus
.ApplicantAdministrativeControl
dot1dPortGmrpFailedRegistrations dot1dPortGmrpFailedRegistrations
.FailedRegistrations .FailedRegistrations
dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU
The following IEEE 802.1D management objects have not been The following IEEE 802.1D management objects have not been included
included in the Bridge MIB for the indicated reasons. in 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 per-{device,port,application} Only
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. 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.
skipping to change at page 7, line 28 skipping to change at page 7, line 33
organized as a set of related objects. The overall structure and organized as a set of related objects. The overall structure and
assignment of objects to their groups is shown below. Some of the assignment of objects to their groups is shown below. Some of the
original objects from RFC1493 need to be indexed differently when original objects from RFC1493 need to be indexed differently when
extended in a VLAN environment so some objects in that module extended in a VLAN environment so some objects in that module
effectively duplicate new objects defined here: this is necessary for effectively duplicate new 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
[12]. It also details those objects that are not considered necessary [12]. It also details those objects that are not considered
in this MIB module. necessary in this MIB module.
Note: unlike IEEE 802.1D, [12] chose not to define a new set of Note: unlike IEEE 802.1D, [12] chose not to define a new set of
managed object names so those following are referenced from the managed object names so those following are referenced from the
descriptions of management operations with section numbering from descriptions of management operations with section numbering from
clause 12 in that document. clause 12 in that 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 config dot1qVlanVersionNumber 12.10.1.1 read bridge vlan
dot1qMaxVlanId 12.10.1.1 read bridge vlan config config
dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan config dot1qMaxVlanId 12.10.1.1 read bridge vlan
dot1qCanOverridePvidTagging 12.10.1.1 read bridge vlan config config
dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan
config
dot1qNumVlans dot1qNumVlans
dot1qResetToDefaults 12.10.1.5 reset vlan bridge dot1dGvrpStatus 12.9.2.1/2 read/set garp
dot1dGvrpAdminStatus 12.9.2.1/2 read/set garp
applicant controls applicant controls
dot1qTp dot1qTp
dot1qTpFdbClear 12.4.1.4 reset bridge
dot1qFdbTable dot1qFdbTable
dot1qFdbId dot1qFdbId
dot1qFdbClear 12.4.1.4 reset bridge 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 dot1qTpGroupAllowedToGoTo
dot1qTpGroupGmrp dot1qTpGroupLearnt
dot1qTpGroupIgmp dot1qForwardAllTable 12.7.7.1 read filtering entry
dot1qServiceReqTable 12.7.7.1 read filtering entry dot1qForwardAllPorts
dot1qServiceRequirement dot1qForwardAllStaticPorts
dot1qServiceReqPorts dot1qForwardUnregisteredTable 12.7.7.1 read filtering entry
dot1qServiceReqStaticPorts dot1qForwardUnregisteredPorts
dot1qForwardUnregisteredStaticPorts
dot1qStatic dot1qStatic
dot1qStaticTable 12.7.7.1 create/delete/read dot1qStaticUnicastTable 12.7.7.1 create/delete/read
filtering entry filtering entry
12.7.6.1 read permanent database 12.7.6.1 read permanent database
dot1qStaticAddress dot1qStaticUnicastAddress
dot1qStaticReceivePort dot1qStaticUnicastReceivePort
dot1qStaticAllowedToGoTo dot1qStaticUnicastAllowedToGoTo
dot1qStaticStatus dot1qStaticUnicastStatus
dot1qStaticMulticastTable 12.7.7.1 create/delete/read
filtering entry
12.7.6.1 read permanent database
dot1qStaticMulticastAddress
dot1qStaticMulticastReceivePort
dot1qStaticMulticastStaticEgressPorts
dot1qStaticMulticastForbiddenEgressPorts
dot1qStaticMulticastStatus
dot1qVlan dot1qVlan
dot1qVlanTable 12.10.2.1 read vlan configuration dot1qVlanNumDeletes
dot1qVlanCurrentTable 12.10.2.1 read vlan
configuration
12.10.3.5 read VID to FID 12.10.3.5 read VID to FID
allocations allocations
12.10.3.6 read FID allocation 12.10.3.6 read FID allocation
for VID for
VID
12.10.3.7 read VIDs allocated to 12.10.3.7 read VIDs allocated to
FID FID
dot1qVlanIfIndex dot1qVlanTimeMark
dot1qVlanId dot1qVlanIndex
dot1qVlanFdbId dot1qVlanFdbId
dot1qVlanOperEgressPorts dot1qVlanCurrentEgressPorts
dot1qVlanOperUntaggedPorts dot1qVlanCurrentUntaggedPorts
dot1qVlanBridgeUpTime 12.4.1.2.3 read bridge
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
dot1qVlanStaticVlanId
dot1qVlanStaticName 12.4.1.3 set bridge name dot1qVlanStaticName 12.4.1.3 set bridge name
dot1qVlanFixedPorts dot1qVlanStaticEgressPorts
dot1qVlanForbiddenPorts dot1qVlanForbiddenEgressPorts
dot1qVlanAdminUntaggedPorts dot1qVlanStaticUntagged
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
dot1qPortGvrpAdminStatus 12.9.2.2 set garp applicant dot1qPortGvrpStatus 12.9.2.2 read/set garp applicant
controls
dot1qPortGvrpOperStatus 12.9.2.1 read 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 dot1qFramesReceived
dot1qOctetsReceived (optional) dot1qOctetsReceived (optional)
dot1qForwardOutbound dot1qForwardOutbound
dot1qDiscardInbound dot1qDiscardInbound
dot1qDiscardNoBuffers dot1qDiscardNoBuffers
skipping to change at page 9, line 46 skipping to change at page 10, line 22
dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port
counters counters
dot1qHCFramesReceived dot1qHCFramesReceived
dot1qHCOctetsReceived (optional) dot1qHCOctetsReceived (optional)
dot1qHCForwardOutbound dot1qHCForwardOutbound
dot1qHCDiscardInbound dot1qHCDiscardInbound
dot1qHCDiscardNoBuffers dot1qHCDiscardNoBuffers
dot1qHCDiscardTransitDelayExceeded dot1qHCDiscardTransitDelayExceeded
dot1qHCDiscardError dot1qHCDiscardError
dot1qHCDiscardOnIngressFiltering (optional) 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 constraints vlan learning
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 The following IEEE 802.1Q management objects have not been included
included in the Bridge MIB for the indicated reasons. in the Bridge MIB for the indicated reasons.
IEEE 802.1Q Object Disposition IEEE 802.1Q Object Disposition
reset bridge (12.4.1.4) use dot1qTpFdbClear or reset bridge (12.4.1.4) not considered useful[Issue
dot1qFdbClear to clear FDB. 46]
reset vlan bridge (12.10.1.5) not considered useful[Issue
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 [Issue 21] permanent database size not considered useful
number of static filtering entries number of static filtering entries
count rows in dot1qStaticTable count rows in dot1qStaticTable
[Issue 9].
number of static VLAN count rows in number of static VLAN count rows in
registration entries dot1qVlanStaticTable [Issue 9]. 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 [Issue 20] filtering database size not considered useful
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 Filtering Databases for both unicast and multicast dynamic Filtering Databases for both unicast and multicast
skipping to change at page 11, line 37 skipping to change at page 12, line 18
status of the Virtual LANs known to a bridge. This includes status of the Virtual LANs known to a bridge. This includes
management of the statically configured VLANs as well as reporting management of the statically configured VLANs as well as reporting
VLANs discovered by other means e.g. GVRP. It also controls VLANs discovered by other means e.g. GVRP. It also controls
configuration and reports status of per-port objects relating to configuration and reports status of per-port objects relating to
VLANs and reports traffic statistics. It also provides for VLANs and reports traffic statistics. It also provides for
management of the VLAN Learning Constraints. management of the VLAN Learning Constraints.
3.3. Textual Conventions 3.3. Textual Conventions
The datatypes MacAddress, BridgeId, Timeout, EnabledStatus, PortList, The datatypes MacAddress, BridgeId, Timeout, EnabledStatus, PortList,
VlanIfIndex and VlanId are used as textual conventions in this VlanIndex and VlanId are used as textual conventions in this
document. These textual conventions have NO effect on either the document. These textual conventions have NO effect on either the
syntax nor the semantics of any managed object. Objects defined syntax nor the semantics of any managed object. Objects defined
using these conventions are always encoded by means of the rules that using these conventions are always encoded by means of the rules that
define their primitive type. Hence, no changes to the SMI or the define their primitive type. Hence, no changes to the SMI or the
SNMP are necessary to accommodate these textual conventions which are SNMP are necessary to accommodate these textual conventions which are
adopted merely for the convenience of readers. adopted merely for the convenience of readers.
3.4. Relationship to Other MIBs 3.4. Relationship to Other MIBs
As described above, some IEEE 802.1D management objects have not been As described above, some IEEE 802.1D management objects have not been
skipping to change at page 13, line 44 skipping to change at page 14, line 19
bridged. All such data is sent/received via the ports of the bridge. bridged. All such data is sent/received via the ports of the bridge.
3.4.2.1. Layering Model 3.4.2.1. Layering Model
This memo assumes the interpretation of the Interfaces Group to be in This memo assumes the interpretation of the Interfaces Group to be in
accordance with [14] which states that the interfaces table (ifTable) accordance with [14] 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 sub-layer below the internetwork layer of a network interface is each sub-layer below the internetwork layer of a network interface is
considered an interface. considered an interface.
This memo recommends that, within an entity, each VLAN which is This memo recommends that, within an entity, VLANs which are
instantiated as an entry in dot1qVlanTable by either management instantiated as an entry in dot1qVlanCurrentTable by either
configuration through dot1qVlanStaticTable or by dynamic means (e.g. management configuration through dot1qVlanStaticTable or by dynamic
through GVRP protocol), also be represented by an entry in ifTable. means (e.g. through GVRP), are NOT also represented by an entry in
ifTable.
3.4.2.2. Interpretations of ifTable for VLANs
Some specific interpretations of ifTable for VLAN entries follow.
ifTable Object Use for VLAN Layer
============== ==================
ifIndex Each VLAN is represented by an entry
in the ifTable.
ifDescr Description of the VLAN e.g. VLAN
name. It is recommended that this
bear some resemblance to
dot1qVlanStaticName.
ifType propVirtual(53)
ifMtu 0 or smallest MTU of all of the
ports in the VLAN.
ifSpeed 0
ifPhysAddress zero-filled
ifAdminStatus up(1) whenever there are active ports
ifOperStatus in the VLAN which are ready to send
and/or receive traffic. See [14] for
other defined usage which applies.
ifLastChange see interfaces MIB [14].
ifName Textual name (unique on this system)
of the VLAN or an octet string of zero
length.
ifLinkUpDownTrapEnable Default is disabled (2).
ifConnectorPresent Set to false (2).
ifPromiscuousMode Set to false (2).
ifHighSpeed 0
ifHCPacketGroup 64-bit counters: must be supported if
ifVHCPacketGroup required by the compliance
statements in [14].
ifHCFixedLengthGroup Not to be implemented for these Where an entity contains higher-layer protocol entities e.g. IP-layer
entries. interfaces, that transmit and receive traffic to/from a VLAN, these
should be represented in the ifTable as interfaces of type
propVirtual(53).
3.4.2.3. ifStackTable 3.4.2.2. ifStackTable
In addition, [14] defines a table 'ifStackTable' for describing the In addition, [14] 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 VLANs and then onto physical ports. binding of e.g. IP interfaces to physical ports, although the
However, it cannot represent the full capability of the 802.1Q VLAN presence of VLANs makes the representation less than perfect for
bridging standard since that makes a distinction between VLAN showing connectivity: the ifStackTable cannot represent the full
bindings on 'ingress' to and 'egress' from a port: these capability of the 802.1Q VLAN bridging standard since that makes a
relationships may or may not be symmetrical whereas [14] assumes a distinction between VLAN bindings on 'ingress' to and 'egress' from a
symmetrical binding for transmit and receive. This makes it port: these relationships may or may not be symmetrical whereas [14]
necessary to define other manageable objects for configuring which assumes a symmetrical binding for transmit and receive. This makes
it necessary to define other manageable objects for configuring which
ports are members of which VLANs. ports are members of which VLANs.
3.4.2.4. 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 up to a higher layer entity for local consumption. The format them up to a higher layer entity for local consumption. Note that
of the address, contained in ifRcvAddressAddress, is the same as for this does not include addresses for data-link layer control protocols
ifPhysAddress. such as 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 be represented for devices which implement the extensions: should be represented for devices which implement the extensions:
skipping to change at page 16, line 28 skipping to change at page 16, line 9
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 of this group is unchanged. interpretation of this group is unchanged.
In a device supporting multiple Filtering Databases, this group is In a device supporting multiple Filtering Databases, this group is
interpreted as follows: interpreted as follows:
dot1dTpLearnedEntryDiscards dot1dTpLearnedEntryDiscards
The sum of the counters for each of the individual Filtering The number of times that *any* of the FDBs became full.
Databases.
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 once. If an address has been learnt in multiple databases only once. If an address has been learnt in multiple databases
on more than one port, report the entry on any one of the valid on more 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 Databases or multiple VLANs. The counters should Filtering Databases or multiple VLANs. The counters should
include frames received or transmitted for all VLANs. Note that include frames received or transmitted for all VLANs. Note
equivalent 64-bit port statistics counters are defined in this that equivalent 64-bit port statistics counters are defined in
document for high-capacity network interfaces. this document for high-capacity network interfaces with
conformance statements to indicate for which speeds of
interface they are required.
3.4.3.4. The dot1dStatic Group 3.4.3.4. The dot1dStatic Group
This optional group contains objects that describe the configuration This optional group contains objects that describe the configuration
of destination-address filtering. of destination-address filtering.
In a device operating with a single Filtering Database, In a device operating with a single Filtering Database,
interpretation of this group is unchanged. interpretation of this group is unchanged.
In a device supporting multiple Filtering Databases, this group is In a device supporting multiple Filtering Databases, this group is
interpreted as follows: interpreted as follows:
dot1dStaticTable dot1dStaticTable
Entries read from this table include all static entries from Entries read from this table include all static entries from
all of the Filtering Databases. Entries for the same MAC all of the Filtering Databases. Entries for the same MAC
address and receive port in more than one Filtering Database address and receive port in more than one Filtering Database
must appear only once since these are the indices of this must appear only once since these are the indices of this
table. This table should be implemented as read-only in table. This table should be implemented as read-only in
devices that support multiple Forwarding Databases - instead, devices that support multiple Forwarding Databases - instead,
write access should be provided through dot1qStaticTable, as write access should be provided through dot1qStaticUnicastTable
defined in this document. and dot1qStaticMulticastTable, as 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-bell-bridgemib-00.txt 5.1. Changes since draft-ietf-bridge-bridgemib-00.txt
[To Do (2)] VLAN tables indexed by VlanIndex, not ifIndex
SMIv2 conversion has been done. - same as VlanId for < 4095 and of local scope if >= 4096.
[To Do (3)] New objects added:
Conformance Groups and clauses have been defined. dot1qFdbDynamicCount, dot1dPortCapabilitiesTable,
dot1dDeviceCapabilities, dot1qVlanTimeMark, dot1qVlanNumDeletes,
dot1qLearningConstraintsLastChange
[To Do (4)] Old objects deleted:
Done. See also Issue (1). dot1qVlanId, dot1qVlanStaticVlanId,
dot1dTrafficClassesResetToDefaults, dot1dPortGmrpOperStatus,
dot1pPortGvrpOperStatus, dot1dGarpReset, dot1qTpFdbClear,
dot1qFdbClear
[To Do (5)] Objects renamed/moved:
Section 3.4.3 updated with recommendations on interpretation of dot1qVlanIfIndex -> dot1qVlanIndex,
the BRIDGE-MIB from RFC 1493. dot1qServiceReqTable -> dot1qForwardAllTable
+ dot1qForwardUnregisteredTable,
dot1qStaticTable -> dot1qStaticUnicastTable
+ 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
[Issue (1)] Object descriptions clarified:
Counter32 versions of the statistics have been provided, with dot1qVlanStaticEgressPorts, dot1qVlanForbiddenEgressPorts,
appropriate conformance clauses. dot1qVlanStaticUntagged, dot1qForwardAllTable,
dot1qForwardUnregisteredTable, dot1qForwardAllStaticPorts,
dot1qForwardUnregisteredStaticPorts
[Issue (4)] Updated compliance clauses:
RFC 1493 should be included by reference, as we are not qBridgeLearningConstraintsGroup,
modifying it in any way, and it should be progressed to a full qBridgeLearningConstraintDefaultGroup, dot1qForwardAllPorts,
standard. dot1qForwardAllStaticPorts, dot1qForwardUnregisteredPorts,
dot1qForwardUnregisteredStaticPorts
[Issue (6)] Table indexing:
dot1qServiceReqTable has been added to support static and new indexing for all per-VLAN tables (see issue 3), for Service
dynamic configuration of the "Forward All Groups" and "Forward Requirements tables, for dot1qTpGroupTable now by-VID not by-
Unregistered Groups" Service Requirements. This has been added FID.
to the dot1q MIB, rather than the dot1p MIB, as it is applied to
each Filtering Database separately.
[Issue (7)] New issues (29)-(54) added, other editorial changes.
The allocation of Filtering Database ID must be done
automatically for GVRP, and is potentially a source of conflict
with dot1qLearningConstraintsTable, if the user is allowed to
allocate it manually. The user only needs to know the FDB ID to
determine the VLAN(s) referred to by the Filtering Databases, in
dot1qTpFdbTable, etc. For these reasons, dot1qVlanStaticFdb has
been removed from dot1qVlanStaticTable, and the user cannot
manually allocate an FDB ID. The automatically allocated value
is still reported by dot1qVlanFdbId, in dot1qVlanTable. The
next free FDB ID value, dot1qNextFreeFdbId, is therefore not
required and has been removed.
[Issue (10)] 5.2. To Do List
No action required.
[Issue (13)] (1) Update boilerplate for appropriate new SNMP framework(s) (v3?)
No action required. This version is simpler than 802.1Q. 5.3. Open Issues
[Issue (14)] The following is a list of issues that were discussed at the Interim
No action required. meeting in Cambridge, MA in June 1998. Suggested resolutions agreed
at that meeting are supplied here and the changes have been made to
the MIB text - they are listed here for comment:
[Issue (15)] (11) 802.1D has separate registrar and applicant controls per state
Removed the per FDB Aging Time, dot1qFdbAgingTime. machine (GVRP and GMRP): do we need per-VLAN and per-Group
Registrar controls? Agreement from interim meeting was: YES.
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.
[Issue (16)] (12) Should the per-port GARP admin controls apply to Registrar as
No action required. Per-port is sufficient. well as Applicant (dot1qPortGvrpStatus, dot1pPortGmrpStatus)?
Alternative would be to provide separate controls for Applicant
and Registrar. Agreement from interim meeting was: YES - No
change.
[Issue (17)] (29) dot1dTrafficClassesResetToDefaults - says that it resets stats
Put dot1qVlanTable before dot1qVlanStaticTable, and moved the too. What about userPriorityRegenTable? (AR): NUKE
definition of dot1qVlanIfIndex to dot1qVlanTable. As dot1dTrafficClassesResetToDefaults
dot1qVlanTable has equivalents to all of the dot1qVlanStatic
entries, there should not be any issue with the indexing of
either of these tables.
[Issue (18)] (30) Trunk ports - should MIB support such a concept (802.1Q does
No action required. Do not think (up|down) are appropriate, as not)? NO
the controls using (enabled|disabled) are not for interfaces.
There are many examples of (enabled|disabled) used as control
status values (including RFC1493), but don't know of a textual
convention for this.
[Issue (19)] (31) dot1qVlanBridgeUpTime: is this needed per-VLAN? ifLastChange
All write-only items have been changed to read-write, with a can do this function if we have ifTable entries per-VLAN: NO
definition of the value to be returned when they are read.
[Issue (23)] (32) Timestamp-based indexing for some tables? dot1dTpFdbTable in
Added dot1qConstraintSetDefault and dot1qConstraintTypeDefault, RFC1493 - NO dot1qTpFdbTable - NO, TimeFilter not practical;
allowing a default constraint set to be defined for unspecified lastChange not useful dot1qVlanCurrentTable - YES- added both
VLANs. This allows a shared VLAN set, or independent VLAN set dot1qVlanTimeMark and dot1qVlanNumDeletes. dot1qStaticTable? NO
constraints to be used as defaults. - cannot use TimeFilter on read-create tables
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.
[Issue (24)] (34) Should an agent instantiate a set of dot1qForwardAllTable and
Separate controls to enable and disable GARP have been removed. dot1qForwardUnregisteredTable entries for each FDB that it could
They were an unnecessary complication. GMRP and GVRP controls have or just a set for each FDB that is currently in use? The
have been simplified as a result of this. latter - add clarification.
Other changes (35) Nuke dot1qStaticReceivePort? There are not any implementations
The items in dot1qPortVlanTable have been re-ordered, to put all of the RFC1493 equivalent are there? Yes there are - keep it.
GVRP items together.
Additional notes have been provided in section 3.1.1, explaining (36) Should agent accept SETs to dot1qVlanStaticUntagged,
why Multicast Group and Service Requirements are defined only in dot1qVlanStaticEgressPorts, dot1qVlanForbiddenEgressPorts that
the Q-BRIDGE-MIB. it cannot actually implement? (ELB) NO - clarify description.
New issues added, closed issues moved to a new section; minor (37) Nuke dot1dPortGmrp/GvrpOperStatus? - YES.
editorial changes.
5.2. To Do List (38) Nuke dot1qResetToDefaults? (KZM) - YES
(1) Update boilerplate for appropriate new SNMP framework(s) (v3?) (39) Nuke dot1dGarpReset? (KZM) YES, and update DESCRIPTIONs of
dot1dGmrpStatus, dot1qGvrpStatus, dot1dPortGmrpStatus,
dot1qPortGvrpStatus,
5.3. Open Issues (40) Make dot1dPortGarp timers per-device, not per-port? (KZM) saves
NVRAM - assume leave it the same for now
(2) Indexing of tables by VlanId or by ifIndex? (assume ifIndex) (41) MIN-ACCESS read-only for dot1dTrafficClass,
dot1dRegenUserPriority (KZM) - do it
(3) Indexing of FDB tables by MacAddress or by something else? (42) dot1qTpGroupGmrp/Igmp (KZM) - merge these to dot1qTpGroupLearnt
(assume MacAddress)
(5) ifStackTable usage (43) do we need 64-bit dot1qHC errors? (KZM) - Assume yes for now
(8) Learned entry discards counter - per-VLAN? per-device? this (45) do we need dot1qVersion? (KZM) - assume Yes
object is not in 802.1D.
(9) Do we need per-FID static/dynamic filtering entry counts? (46) nuke dot1qTpFdbClear? dot1qFdbClear? (KZM) - assume Yes (802.1Q
(12.7.1.1.3) "reset bridge" operation is not now supported).
(11) 802.1D has separate registrar and applicant controls per state (47) do we need dot1qFdbTable which now contains only dot1qFdbId? -
machine (GVRP and GMRP): do we need per-VLAN and per-Group assume YES for now (it also now has dot1qFdbDynamicCount).
Registrar controls? (assume YES:
dot1qVlanFixedPorts/dot1qVlanForbiddenPorts,
dot1dStaticAllowedToGoTo). Do we need per-VLAN and per-Group
Applicant controls? (assume NO - per-port is sufficient:
dot1qPortGvrpAdminStatus, dot1pPortGmrpAdminStatus).
(12) Should the per-port GARP admin controls apply to Registrar as (48) should dot1qTpFdbTable be {FID,MAC} or {MAC,FID} - assume the
well as Applicant? (dot1qPortGvrpAdminStatus, former for now
dot1pPortGmrpAdminStatus). (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.
(20) Do we need "read filtering database (12.7.1.1): filtering (54) dot1qVlanAdminUntaggedPorts - expand DESCRIPTION to include
database size"? meaning of 0 (KK). Changed description to talk about
include/exclude from the set of ports: refer to Portlist TC for
0/1 meaning.
(21) Do we need "read forwarding port counters (12.6.1.1): permanent Issues that are believed still to be open at close of June 1998
database size"? interim meeting and have not been addressed in this draft. This also
includes new issues that have arisen due to changes agreed at that
meeting:
(22) Do we need a 'next free ifIndex' object? (5) ifStackTable usage - how to represent binding of IP interfaces
to VLANs now that we do not necessarily have one ifEntry per
VLAN.
(23) Do we need default learning constraints? (assume yes) (44) Clarification of dot1qHC counter descriptions - what does
inbound mean? What counts as errors? 2 separable issues: 1. It
was requested that the meaning of dot1qDiscardInbound be
clarified to ensure it is distinct from other counters.
(Specifically, why is it different from 1493?) (KZM) - this can
be derived from other counters - NUKE IT! 2. Why are all of
these so different from RFC1493? e.g. do they refer to
Transparent-only? What about SRT or SR?
(24) Can we remove separate GARP controls? (assume yes) (49) Now that dot1qVlanStaticTable is indexed by VlanIndex/VlanId we
need a "next free" variable since these values must be managed
by agent.
(50) dot1qVlanFdbId, dot1qMaxSupportedVlans, dot1qNumVlans should not
be range-limited. If they are then we need new objects to
represent the number of non-802.1Q "VLANs" too. (AHS)
(51) dot1qConfigurablePvidTagging: does this also cover the "I can
only set a single VLAN to be untagged on egress" implementation
option in 802.1Q?
(52) Do we need an explicit "dot1dExtendedFilteringServicesStatus"
enable/disable object? (AHS)
(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
dot1qStaticAllowedToGoTo into
dot1qStaticMulticastStaticEgressPorts and
dot1qStaticMulticastForbiddenEgressPorts. Issue still open for
unicast.
(56) Should a value of 0 be allowed for dot1qTpFdbPort? This is
inherited from RFC1493 (ELB)
(57) Rename dot1qVlanStaticUntagged as dot1qVlanStaticUntaggedPorts
for consistency. (ELB)
(58) If an empty string is used for dot1qVlanStaticName, does it have
to be unique? The description implies it must be unique. (ELB)
NO - clarified this.
(59) Should dot1qPvid have syntax VlanIndex (currently it is VlanId)?
(ELB)
(60) Do dot1qPortAcceptableFrameTypes and dot1qPortIngressFiltering
also apply to tagged GMRP packets? (ELB)
(61) Do we need dot1qLearningContraintsLastChange? It just reminds
the manager of changes that he or some other manager made. (ELB)
5.4. Issues closed in this draft
(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
MacAddress.
(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?
(12.7.1.1.3) YES - count for dynamic only added as
dot1qFdbDynamicCount.
(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.
(25) Do we need to split dot1qStaticTable into (25) Do we need to split dot1qStaticTable into
dot1qStaticUnicastTable and dot1qStaticMulticastTable? dot1qStaticUnicastTable and dot1qStaticMulticastTable? YES:
dot1qStaticTable -> dot1qStaticUnicastTable, indexed by FID +
dot1qStaticMulticastTable, indexed by VID. Also index
dot1qTpGroupTable by VID. This matches the indexing assumed by
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 with dot1qServiceRequirement as a 2nd index? (assume the leave with dot1qServiceRequirement as a 2nd index? Split into 2
former for now). tables, each indexed by VID.
(27) Do we want "capabilities" bitmap objects? (27) Do we want "capabilities" bitmap objects? YES - per-port
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? GMRP, GVRP addresses? NO - clarify in preface.
5.4. Closed Issues in his Draft 5.5. Issues closed in previous drafts
(1) Should this MIB offer support for SMIv1-only agents (1) Should this MIB offer support for SMIv1-only agents
(Counter32/64)? ADDED Counter32/Counter64 versions of the per- (Counter32/64)? ADDED Counter32/Counter64 versions of the per-
VLAN statistics. ADDED Counter64 versions of the per-port VLAN statistics. ADDED Counter64 versions of the per-port
statistics from RFC1493. Added appropriate conformance clauses statistics from RFC1493. Added appropriate conformance clauses
for all. for all.
(4) Include RFC1493 by value or reference? REFERENCE (4) Include RFC1493 by value or reference? REFERENCE
(6) Representations of filtering entry for "AllGroups" and (6) Representations of filtering entry for "AllGroups" and
skipping to change at page 22, line 21 skipping to change at page 24, line 20
(14) Do we need to define a "notify vlan registration failure" trap? (14) Do we need to define a "notify vlan registration failure" trap?
NO NO
(15) dot1qFdbAgingTime is currently per-FID: 802.1Q has it per- (15) dot1qFdbAgingTime is currently per-FID: 802.1Q has it per-
device. PER DEVICE device. PER DEVICE
(16) dot1pPortDefaultUserPriority - can this usefully be per-port, (16) dot1pPortDefaultUserPriority - can this usefully be per-port,
per-VLAN? PER-PORT per-VLAN? PER-PORT
(17) Both dot1qVlanTable and dot1qVlanStaticTable are indexed by (17) Both dot1qVlanCurrentTable and dot1qVlanStaticTable are indexed
dot1qVlanIfIndex but that only appears in dot1qVlanStaticTable - by dot1qVlanIfIndex but that only appears in
is this a problem? MOVED TO dot1qVlanTable. dot1qVlanStaticTable - is this a problem? MOVED TO
dot1qVlanCurrentTable.
(18) Should we choose same names (up/down) as IF-MIB for values of (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 the admin/oper status values, rather than defining our own new
TC? Is there an existing TC we can import? NO CHANGE. TC? Is there an existing TC we can import? NO CHANGE.
(19) Should we have write-only "reset" objects or should these be (19) Should we have write-only "reset" objects or should these be
read-write to help MIB browsers (assume write-only)? READ-WRITE. read-write to help MIB browsers (assume write-only)? READ-WRITE.
6. Definitions for Extended Bridge MIB 6. Definitions for Extended Bridge MIB
skipping to change at page 24, line 7 skipping to change at page 26, line 7
Email: andrew@extremenetworks.com Email: andrew@extremenetworks.com
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 Rijsinghani Anil Rijhsinghani
Postal: Cabletron Systems Postal: Cabletron Systems
550 King Street, LKG2-2/Y10 550 King Street, LKG2-2/Y10
Littleton, MA 01460-1289 Littleton, MA 01460-1289
USA USA
Phone: +1 (508) 486-6786 Phone: +1 (508) 486-6786
Email: anil@lkg.dec.com Email: Anil.Rijhsinghani@digital.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"
DESCRIPTION "Updated with revisions from June 1998 Interim
meeting."
::= { dot1dBridge 6 } ::= { dot1dBridge 6 }
pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 } pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
EnabledStatus ::= TEXTUAL-CONVENTION EnabledStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 24, line 44 skipping to change at page 27, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A simple status value for the object." "A simple status value for the object."
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX INTEGER { enabled(1), disabled(2) }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- groups in the P-BRIDGE MIB -- groups in the P-BRIDGE MIB
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dExtBase OBJECT IDENTIFIER ::= { pBridgeMIBObjects 1 } dot1dExtBase OBJECT IDENTIFIER ::= { pBridgeMIBObjects 1 }
dot1dPriority OBJECT IDENTIFIER ::= { pBridgeMIBObjects 2 } dot1dPriority OBJECT IDENTIFIER ::= { pBridgeMIBObjects 2 }
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
SYNTAX BITS {
dot1dExtendedFilteringServices(0),
-- can perform filtering of
-- individual multicast
-- addresses controlled by GMRP.
dot1qStaticEntryIndividualPort(1),
-- can represent non-zero entries
-- in dot1qStaticUnicastReceivePort
-- & dot1qStaticMulticastReceivePort.
dot1qIVLCapable(2), -- Independent VLAN Learning
dot1qSVLCapable(3), -- Shared VLAN Learning
dot1qHybridCapable(4) -- both of the above simultaneously
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the optional parts of IEEE 802.1D and 802.1Q
that are implemented by this device and are managable
through this MIB. Capabilities that are allowed on a
per-port basis are indicated in dot1dPortCapabilities."
REFERENCE
"IEEE 802.1D/D16 5.2 and 802.1Q/D10 5.2"
::= { 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."
DEFVAL { true } DEFVAL { true }
::= { dot1dExtBase 1 }
dot1dTrafficClassesResetToDefaults OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When the value true(1) is written to this object, all
traffic class values are reset to their defaults and
traffic class statistics are cleared. This object
always returns false(2) when read."
::= { dot1dExtBase 2 } ::= { dot1dExtBase 2 }
dot1dGmrpAdminStatus OBJECT-TYPE dot1dGmrpStatus 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
GMRP. The value enabled(1) indicates that GMRP should GMRP. The value enabled(1) indicates that GMRP should
be enabled on this device, in all VLANs, on all ports be enabled on this device, in all VLANs, on all ports
for which it has not been specifically disabled. When for which it has not been specifically disabled. When
disabled(2), GMRP is disabled, in all VLANs, on all disabled(2), GMRP is disabled, in all VLANs, on all
ports." ports and all GMRP packets will be forwarded
transparently. This object affects both Applicant and
Registrar state machines. A transition from disabled(2)
to enabled(1) will cause a reset of all GMRP state
machines on all ports and zeroing of all related
counters."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1dExtBase 3 } ::= { dot1dExtBase 3 }
dot1dGarpReset OBJECT-TYPE -- -------------------------------------------------------------
SYNTAX TruthValue -- Port Capabilities Table
MAX-ACCESS read-write -- -------------------------------------------------------------
dot1dPortCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When the value true(1) is written to this object, all "A table that contains capabilities information about
GARP parameters are reset to their power-on values and every port that is associated with this bridge."
all GARP statistics are cleared. This applies to all
GARP applications, on all ports, in all VLANs. This
object always returns false(2) when read."
::= { dot1dExtBase 4 } ::= { dot1dExtBase 4 }
dot1dPortCapabilitiesEntry OBJECT-TYPE
SYNTAX Dot1dPortCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of capabilities information about this port
indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry }
::= { dot1dPortCapabilitiesTable 1 }
Dot1dPortCapabilitiesEntry ::=
SEQUENCE {
dot1dPortCapabilities
BITS
}
dot1dPortCapabilities OBJECT-TYPE
SYNTAX BITS {
dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of
-- frames and GVRP.
dot1qConfigurableAcceptableFrameTypes(1),
-- allows modification of the value
-- of dot1qPortAcceptableFrameTypes.
dot1qPortIngressFiltering(2),
-- supports filtering on ingress
-- of all VLANs not represented in
-- an egress list.
dot1qConfigurablePvidTagging(3)
-- allows the VLAN which is the current
-- PVID to be tagged on egress.
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the parts of IEEE 802.1D and 802.1Q that are
optional on a per-port basis that are implemented by
this device and are managable through this MIB."
REFERENCE
"IEEE 802.1D/D16 5.2 and 802.1Q/D10 5.2"
::= { dot1dPortCapabilitiesEntry 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- the dot1dPriority group -- the dot1dPriority group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Port Priority Table -- Port Priority Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dPortPriorityTable OBJECT-TYPE dot1dPortPriorityTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortPriorityEntry SYNTAX SEQUENCE OF Dot1dPortPriorityEntry
skipping to change at page 29, line 18 skipping to change at page 32, line 40
SEQUENCE { SEQUENCE {
dot1dTrafficClass dot1dTrafficClass
INTEGER INTEGER
} }
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."
It is optional to support writing to this object."
::= { dot1dTrafficClassEntry 1 } ::= { dot1dTrafficClassEntry 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- 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
skipping to change at page 32, line 15 skipping to change at page 35, line 36
SYNTAX Dot1dPortGmrpEntry SYNTAX Dot1dPortGmrpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"GMRP control and status information for a bridge port." "GMRP control and status information for a bridge port."
AUGMENTS { dot1dBasePortEntry } AUGMENTS { dot1dBasePortEntry }
::= { dot1dPortGmrpTable 1 } ::= { dot1dPortGmrpTable 1 }
Dot1dPortGmrpEntry ::= Dot1dPortGmrpEntry ::=
SEQUENCE { SEQUENCE {
dot1dPortGmrpAdminStatus dot1dPortGmrpStatus
EnabledStatus,
dot1dPortGmrpOperStatus
EnabledStatus, EnabledStatus,
dot1dPortGmrpFailedRegistrations dot1dPortGmrpFailedRegistrations
Counter32, Counter32,
dot1dPortGmrpLastPduOrigin dot1dPortGmrpLastPduOrigin
MacAddress MacAddress
} }
dot1dPortGmrpAdminStatus OBJECT-TYPE dot1dPortGmrpStatus 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 state of GMRP operation on this port. The value
GMRP, on this port. The value enabled(1) indicates that enabled(1) indicates that GMRP is enabled on this port,
GMRP should be enabled on this port, in all VLANs, if in all VLANs, as long as dot1dGmrpStatus is also enabled
GMRP is also enabled for this device. When disabled(2), for this device. When disabled(2) but dot1dGmrpStatus
GMRP is disabled on this port, in all VLANs." is still enabled for the device, GMRP is disabled on
this port in all VLANs: any GMRP packets received will
be silently discarded and no GMRP registrations will be
propagated from other ports. This object affects all
GMRP Applicant and Registrar state machines on this
port. A transition from disabled(2) to enabled(1) will
cause a reset of all GMRP state machines on this port
and zeroing of all related counters."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1dPortGmrpEntry 1 } ::= { dot1dPortGmrpEntry 1 }
dot1dPortGmrpOperStatus OBJECT-TYPE
SYNTAX EnabledStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current operational status of GMRP on this port."
::= { dot1dPortGmrpEntry 2 }
dot1dPortGmrpFailedRegistrations OBJECT-TYPE dot1dPortGmrpFailedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of failed GMRP registrations, for any "The total number of failed GMRP registrations, for any
reason, in all VLANs, on this port." reason, in all VLANs, on this port."
::= { dot1dPortGmrpEntry 3 } ::= { dot1dPortGmrpEntry 2 }
dot1dPortGmrpLastPduOrigin OBJECT-TYPE dot1dPortGmrpLastPduOrigin OBJECT-TYPE
SYNTAX MacAddress SYNTAX MacAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Source MAC Address of the last GMRP message "The Source MAC Address of the last GMRP message
received on this port." received on this port."
::= { dot1dPortGmrpEntry 4 } ::= { dot1dPortGmrpEntry 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- High Capacity Port Table for Transparent Bridges -- High Capacity Port Table for Transparent Bridges
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dTpHCPortTable OBJECT-TYPE dot1dTpHCPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dTpHCPortEntry SYNTAX SEQUENCE OF Dot1dTpHCPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 34, line 14 skipping to change at page 37, line 32
dot1dTpHCPortInDiscards dot1dTpHCPortInDiscards
Counter64 Counter64
} }
dot1dTpHCPortInFrames OBJECT-TYPE dot1dTpHCPortInFrames 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 received by this "The number of frames that have been received by this
port from its segment. Note that a frame received on the port from its segment. Note that a frame received on
interface corresponding to this port is only counted by the interface corresponding to this port is only counted
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" "IEEE 802.1D-1998: 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
skipping to change at page 35, line 19 skipping to change at page 38, line 37
pBridgeGroups OBJECT IDENTIFIER ::= { pBridgeConformance 1 } pBridgeGroups OBJECT IDENTIFIER ::= { pBridgeConformance 1 }
pBridgeCompliances OBJECT IDENTIFIER pBridgeCompliances OBJECT IDENTIFIER
::= { pBridgeConformance 2 } ::= { pBridgeConformance 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- units of conformance -- units of conformance
-- ------------------------------------------------------------- -- -------------------------------------------------------------
pBridgeExtBaseGroup OBJECT-GROUP pBridgeExtCapGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dTrafficClassesEnabled, dot1dDeviceCapabilities,
dot1dGmrpAdminStatus, dot1dPortCapabilities
dot1dGarpReset
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing device level control "A collection of objects indicating the optional
and status information for the Priority and Multicast capabilites of the device."
Filtering extended bridge services."
::= { pBridgeGroups 1 } ::= { pBridgeGroups 1 }
pBridgeExtBaseGroup OBJECT-GROUP
pBridgeExtBaseOptionalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dTrafficClassesResetToDefaults dot1dTrafficClassesEnabled,
dot1dGmrpStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing device level control "A collection of objects providing device-level control
for bridge Priority services." and status information for the Priority and Multicast
Filtering extended bridge services."
::= { pBridgeGroups 2 } ::= { pBridgeGroups 2 }
pBridgePriorityGroup OBJECT-GROUP pBridgePriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortDefaultUserPriority, dot1dPortDefaultUserPriority,
dot1dPortNumTrafficClasses, dot1dPortNumTrafficClasses,
dot1dRegenUserPriority, dot1dRegenUserPriority,
dot1dTrafficClass dot1dTrafficClass
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the priorities "A collection of objects defining the priorities
applicable to each port and the traffic classes applicable to each port and the traffic classes
within a bridge." within a bridge."
::= { pBridgeGroups 3 } ::= { pBridgeGroups 4 }
pBridgeAccessPriorityGroup OBJECT-GROUP pBridgeAccessPriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortOutboundAccessPriority dot1dPortOutboundAccessPriority
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects defining the media dependent "A collection of objects defining the media dependent
outbound access level for each priority." outbound access level for each priority."
::= { pBridgeGroups 4 } ::= { pBridgeGroups 5 }
pBridgeConfigurablePriorityGroup OBJECT-GROUP pBridgeConfigurablePriorityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortDefaultUserPriority, dot1dPortDefaultUserPriority,
dot1dPortNumTrafficClasses, dot1dPortNumTrafficClasses,
dot1dRegenUserPriority, dot1dRegenUserPriority,
dot1dTrafficClass dot1dTrafficClass
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects where write-access would "A collection of objects where write-access would
provide the ability to configure the use of priority provide the ability to configure the use of priority
in a bridge." in a bridge."
::= { pBridgeGroups 5 } ::= { pBridgeGroups 6 }
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 6 } ::= { pBridgeGroups 7 }
pBridgePortGmrpGroup OBJECT-GROUP pBridgePortGmrpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dPortGmrpAdminStatus, dot1dPortGmrpStatus,
dot1dPortGmrpOperStatus,
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 7 } ::= { pBridgeGroups 8 }
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 8 } ::= { pBridgeGroups 9 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- 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 bridge services." and Multicast Filtering extended bridging services."
MODULE MODULE
MANDATORY-GROUPS { pBridgeExtBaseGroup } MANDATORY-GROUPS { pBridgeExtCapGroup, pBridgeExtBaseGroup }
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."
skipping to change at page 38, line 14 skipping to change at page 41, line 33
GROUP pBridgeConfigurablePriorityGroup GROUP pBridgeConfigurablePriorityGroup
DESCRIPTION DESCRIPTION
"Write-access must be provided to all objects in "Write-access must be provided to all objects in
this group in order to manage priority in a switch this group in order to manage priority in a switch
as specified by IEEE 802.1D. However, it is as specified by IEEE 802.1D. However, it is
optional to support management of priority." 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: GMRP, defined by the of the GARP applications: e.g. GMRP, defined by the
extended bridge services of 802.1D; or GVRP, defined extended filtering services of 802.1D; or GVRP,
by 802.1Q (refer to the Q-BRIDGE-MIB for conformance defined by 802.1Q (refer to the Q-BRIDGE-MIB for
statements for GVRP)." conformance statements for GVRP)."
GROUP pBridgePortGmrpGroup GROUP pBridgePortGmrpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices supporting the "This group is mandatory for devices supporting the
GMRP application, defined by the extended bridge 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 OBJECT dot1dTrafficClassesEnabled
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "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
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT dot1dRegenUserPriority
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { pBridgeCompliances 1 } ::= { pBridgeCompliances 1 }
END END
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, TimeTicks Counter32, Counter64
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
InterfaceIndex
FROM IF-MIB
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
FROM RMON2-MIB;
qBridgeMIB MODULE-IDENTITY qBridgeMIB MODULE-IDENTITY
LAST-UPDATED "9804242200Z" LAST-UPDATED "9807190000Z"
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 39, line 46 skipping to change at page 44, line 4
Phone: +44 1442 438025 Phone: +44 1442 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
Andrew Smith Andrew Smith
Postal: Extreme Networks Postal: Extreme Networks
10460 Bandley Drive 10460 Bandley Drive
Cupertino CA 95014 Cupertino CA 95014
USA USA
Phone: +1 (408) 342 0999 Phone: +1 (408) 342 0999
Email: andrew@extremenetworks.com Email: andrew@extremenetworks.com
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 Rijsinghani Anil Rijhsinghani
Postal: Cabletron Systems Postal: Cabletron Systems
550 King Street, LKG2-2/Y10 550 King Street, LKG2-2/Y10
Littleton, MA 01460-1289 Littleton, MA 01460-1289
USA USA
Phone: +1 (508) 486-6786 Phone: +1 (508) 486-6786
Email: anil@lkg.dec.com Email: Anil.Rijhsinghani@digital.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"
DESCRIPTION "Updated with revisions from June 1998 Interim
meeting."
::= { dot1dBridge 7 } ::= { dot1dBridge 7 }
qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 } qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
PortList ::= TEXTUAL-CONVENTION PortList ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 40, line 43 skipping to change at page 45, line 4
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
PortList ::= TEXTUAL-CONVENTION PortList ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each octet within this value specifies a set of eight "Each octet within this value specifies a set of eight
ports, with the first octet specifying ports 1 through ports, with the first octet specifying ports 1 through
8, the second octet specifying ports 9 through 16, etc. 8, the second octet specifying ports 9 through 16, etc.
Within each octet, the most significant bit represents Within each octet, the most significant bit represents
the lowest numbered port, and the least significant bit the lowest numbered port, and the least significant bit
represents the highest numbered port. Thus, each port represents the highest numbered port. Thus, each port
of the bridge is represented by a single bit within the of the bridge is represented by a single bit within the
value of this object. If that bit has a value of '1' value of this object. If that bit has a value of '1'
then that port is included in the set of ports; the port then that port is included in the set of ports; the port
is not included if its bit has a value of '0'." is not included if its bit has a value of '0'."
SYNTAX OCTET STRING SYNTAX OCTET STRING
VlanIfIndex ::= TEXTUAL-CONVENTION VlanIndex ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the instance of the ifIndex object, "A value used to index per-VLAN tables: values of 0 and
defined by IF-MIB, for the interface corresponding to a 4095 are not permitted; if the value is between 1 and
given VLAN." 4094 inclusive, it represents an 802.1Q VLAN-ID with
SYNTAX InterfaceIndex global scope within a given bridged domain (see VlanId
textual convention). If the value is greater than 4095
then it represents a VLAN with scope local to the
particular agent."
SYNTAX INTEGER
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 42, line 37 skipping to change at page 46, line 47
SYNTAX INTEGER (1..4094) SYNTAX INTEGER (1..4094)
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/D9 12.7.1.1"
::= { dot1qBase 4 } ::= { dot1qBase 4 }
dot1qResetToDefaults OBJECT-TYPE dot1qGvrpStatus OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Writing the value true(1) causes this device to reset
its 802.1Q parameters to their power-on initial values.
Writing the value false(2) has no effect. This object
always returns false(2) if read."
REFERENCE
"IEEE 802.1Q/D9 12.10.1.5"
::= { dot1qBase 5 }
dot1qGvrpAdminStatus 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
not been specifically disabled. When disabled(2), GVRP not been specifically disabled. When disabled(2), GVRP
is disabled, on all ports." is disabled on all ports and all GVRP packets will be
forwarded transparently. This object affects all GVRP
Applicant and Registrar state machines. A transition
from disabled(2) to enabled(1) will cause a reset of all
GVRP state machines on all ports and zeroing of all
related counters."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1qBase 6 } ::= { dot1qBase 5 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- the dot1qTp group -- the dot1qTp group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qTpFdbClear OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Writing true(1) to this object discards all MAC
addresses learnt in all Filtering Databases on this
device. Writing the value false(2) has no effect.
This object always returns false(2) if read."
REFERENCE
"IEEE 802.1Q/D9: Section 12.4.1.4"
::= { dot1qTp 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- the current Filtering Database Table -- the current Filtering Database Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qFdbTable OBJECT-TYPE dot1qFdbTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qFdbEntry SYNTAX SEQUENCE OF Dot1qFdbEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains configuration and control "A table that contains configuration and control
information for each Filtering Database currently information for each Filtering Database currently
operating on this device. Entries in this table appear operating on this device. Entries in this table appear
automatically when VLANs are assigned FDB IDs in the automatically when VLANs are assigned FDB IDs in the
dot1qVlanTable." dot1qVlanCurrentTable."
::= { 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, INTEGER,
dot1qFdbClear dot1qFdbDynamicCount
TruthValue Counter32
} }
dot1qFdbId OBJECT-TYPE dot1qFdbId OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
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 }
dot1qFdbClear OBJECT-TYPE dot1qFdbDynamicCount OBJECT-TYPE
SYNTAX TruthValue SYNTAX Counter32
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Writing true(1) to this object discards all MAC "The current number of dynamic entries in this
addresses learnt in this Filtering Database. Filtering Database."
Writing the value false(2) has no effect.
This object always returns false(2) if read."
REFERENCE REFERENCE
"IEEE 802.1Q/D9: Section 12.4.1.4" "IEEE 802.1Q/D10: 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."
skipping to change at page 46, line 14 skipping to change at page 49, line 48
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Either the value '0', or the port number of the port on "Either the value '0', or the port number of the port on
which a frame having a source address equal to the value which a frame having a source address equal to the value
of the corresponding instance of dot1qTpFdbAddress has of the corresponding instance of dot1qTpFdbAddress has
been seen. A value of '0' indicates that the port been seen. A value of '0' indicates that the port
number has not been learned but that the device does number has not been learned but that the device does
have some forwarding/filtering information about this have some forwarding/filtering information about this
address (e.g. in the dot1qStaticTable). Implementors address (e.g. in the dot1qStaticUnicastTable).
are encouraged to assign the port value to this object
whenever it is learned even for addresses for which the Implementors are encouraged to assign the port value to
corresponding value of dot1qTpFdbStatus is not this object whenever it is learned even for addresses
learned(3)." for which the corresponding value of dot1qTpFdbStatus is
not learned(3)."
::= { dot1qTpFdbEntry 2 } ::= { dot1qTpFdbEntry 2 }
dot1qTpFdbStatus OBJECT-TYPE dot1qTpFdbStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
invalid(2), invalid(2),
learned(3), learned(3),
self(4), self(4),
mgmt(5) mgmt(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this entry. The meanings of the values "The status of this entry. The meanings of the values
are: are:
other(1) - none of the following. This may include other(1) - none of the following. This may include
the case where some other MIB object (not the the case where some other MIB object (not the
corresponding instance of dot1qTpFdbPort, nor an corresponding instance of dot1qTpFdbPort, nor an
entry in the dot1qStaticTable) is being used to entry in the dot1qStaticUnicastTable) is being
determine if and how frames addressed to the used to determine if and how frames addressed to
value of the corresponding instance of the value of the corresponding instance of
dot1qTpFdbAddress are being forwarded. dot1qTpFdbAddress are being forwarded.
invalid(2) - this entry is no longer valid (e.g., it invalid(2) - this entry is no longer valid (e.g., it
was learned but has since aged out), but has not was learned but has since aged out), but has not
yet been flushed from the table. yet been flushed from the table.
learned(3) - the value of the corresponding instance learned(3) - the value of the corresponding instance
of dot1qTpFdbPort was learned and is being used. of dot1qTpFdbPort was learned and is being used.
self(4) - the value of the corresponding instance of self(4) - the value of the corresponding instance of
dot1qTpFdbAddress represents one of the device's dot1qTpFdbAddress represents one of the device's
addresses. The corresponding instance of addresses. The corresponding instance of
dot1qTpFdbPort indicates which of the device's dot1qTpFdbPort indicates which of the device's
skipping to change at page 47, line 14 skipping to change at page 51, line 4
dot1qTpFdbPort indicates which of the device's dot1qTpFdbPort indicates which of the device's
ports has this address. ports has this address.
mgmt(5) - the value of the corresponding instance of mgmt(5) - the value of the corresponding instance of
dot1qTpFdbAddress is also the value of an dot1qTpFdbAddress is also the value of an
existing instance of dot1qStaticAddress." existing instance of dot1qStaticAddress."
::= { dot1qTpFdbEntry 3 } ::= { dot1qTpFdbEntry 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Dynamic Group Registration Table -- Dynamic Group Registration Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qTpGroupTable OBJECT-TYPE dot1qTpGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qTpGroupEntry SYNTAX SEQUENCE OF Dot1qTpGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing filtering information for each FDB, "A table containing filtering information for VLANs
for VLANs configured into the bridge by (local or configured into the bridge by (local or network)
network) management, or learnt dynamically, specifying management, or learnt dynamically, specifying the set of
the set of ports to which frames received on a VLAN for ports to which frames received on a VLAN for this FDB
this FDB and containing a specific Group destination and containing a specific Group destination address are
address are allowed to be forwarded." allowed to be forwarded."
::= { dot1qTp 4 } ::= { dot1qTp 4 }
dot1qTpGroupEntry OBJECT-TYPE dot1qTpGroupEntry OBJECT-TYPE
SYNTAX Dot1qTpGroupEntry SYNTAX Dot1qTpGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Filtering information configured into the bridge by "Filtering information configured into the bridge by
management, or learnt dynamically, specifying the set of management, or learnt dynamically, specifying the set of
ports to which frames received on a VLAN for this FDB ports to which frames received on a VLAN and containing
and containing a specific Group destination address, are a specific Group destination address, are allowed to be
allowed to be forwarded. The subsets of these ports forwarded. The subset of these ports learnt dynamically
learnt dynamically are also given." is also provided."
INDEX { dot1qFdbId, dot1qTpGroupAddress } INDEX { dot1qVlanIndex, dot1qTpGroupAddress }
::= { dot1qTpGroupTable 1 } ::= { dot1qTpGroupTable 1 }
Dot1qTpGroupEntry ::= Dot1qTpGroupEntry ::=
SEQUENCE { SEQUENCE {
dot1qTpGroupAddress dot1qTpGroupAddress
MacAddress, MacAddress,
dot1qTpGroupAllowedToGoTo dot1qTpGroupAllowedToGoTo
PortList, PortList,
dot1qTpGroupGmrp dot1qTpGroupLearnt
PortList,
dot1qTpGroupIgmp
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."
skipping to change at page 48, line 28 skipping to change at page 52, line 14
dot1qTpGroupAllowedToGoTo OBJECT-TYPE dot1qTpGroupAllowedToGoTo 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." allowed to be forwarded."
::= { dot1qTpGroupEntry 2 } ::= { dot1qTpGroupEntry 2 }
dot1qTpGroupGmrp 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 dot1qTpGroupAllowedToGoTo which
were learnt by GMRP, in this Filtering database." were learnt by GMRP or some other dynamic mechanism, in
this Filtering database."
::= { dot1qTpGroupEntry 3 } ::= { dot1qTpGroupEntry 3 }
dot1qTpGroupIgmp OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The subset of ports in dot1qTpGroupAllowedToGoTo which
were learnt by IGMP, in this Filtering database."
::= { dot1qTpGroupEntry 4 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Service Requirements Group -- Service Requirements Group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qServiceReqTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qServiceReqEntry dot1qForwardAllTable OBJECT-TYPE
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 FDB, "A table containing forwarding information for each
configured in the bridge, specifying the set of ports to VLAN, specifying the set of ports to which forwarding of
which each Service Requirement applies, configured all multicasts applies, configured statically by
statically by management, or dynamically by GMRP." management or dynamically by GMRP. An entry appears in
this table for all VLANs that are currently
instantiated."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.7.2, 12.7.7" "IEEE 802.1Q/D9 12.7.2, 12.7.7"
::= { dot1qTp 5 } ::= { dot1qTp 5 }
dot1qServiceReqEntry OBJECT-TYPE dot1qForwardAllEntry OBJECT-TYPE
SYNTAX Dot1qServiceReqEntry SYNTAX Dot1qForwardAllEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Forwarding information for a Service Requiremant "Forwarding information for a VLAN, specifying the set
within an FDB, specifying the set of ports to which that of ports to which all multicasts should be forwarded,
Service Requirement applies, configured statically by configured statically by management or dynamically by
management, or dynamically by GMRP." GMRP."
INDEX { dot1qFdbId, dot1qServiceRequirement } INDEX { dot1qVlanIndex }
::= { dot1qServiceReqTable 1 } ::= { dot1qForwardAllTable 1 }
Dot1qServiceReqEntry ::= Dot1qForwardAllEntry ::=
SEQUENCE { SEQUENCE {
dot1qServiceRequirement dot1qForwardAllPorts
INTEGER,
dot1qServiceReqPorts
PortList, PortList,
dot1qServiceReqStaticPorts dot1qForwardAllStaticPorts
PortList PortList
} }
dot1qServiceRequirement OBJECT-TYPE dot1qForwardAllPorts OBJECT-TYPE
SYNTAX INTEGER { SYNTAX PortList
forwardAllGroups(1), MAX-ACCESS read-only
forwardUnknownGroups(2) STATUS current
} DESCRIPTION
"The complete set of ports in this VLAN to which all
multicast group-addressed frames are to be forwarded.
This includes ports for which this need has been
determined dynamically by GMRP, or configured statically
by management."
::= { dot1qForwardAllEntry 1 }
dot1qForwardAllStaticPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports configured by management in this VLAN
to which all multicast group-addressed frames are to be
forwarded. Ports entered in this list will also appear
in the complete set shown by dot1qForwardAllPorts. This
value will be restored after the device is reset.
The default value is a string of ones of appropriate
length, to indicate standard non-EFS behaviour, i.e.
forward all multicasts to all ports."
::= { dot1qForwardAllEntry 2 }
dot1qForwardUnregisteredTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qForwardUnregisteredEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Service Requirement to which this entry's "A table containing forwarding information for each
forwarding information applies. A port may be included VLAN, specifying the set of ports to which forwarding of
in the Service Requirements for both forwardAllGroups(1) multicast group-addressed frames for which there is no
and forwardUnknownGroups(2), in which case more specific forwarding information applies. This is
forwardAllGroups(1) will apply. The Service Requirement configured statically by management and determined
meanings are: dynamically by GMRP. An entry appears in this table for
forwardAllGroups(1) - Traffic for all multicast all VLANs that are currently instantiated."
groups will be forwarded to the ports in the REFERENCE
list, dot1qServiceReqPorts. "IEEE 802.1Q/D9 12.7.2, 12.7.7"
forwardUnknownGroups(2) - Traffic for multicast ::= { dot1qTp 6 }
groups for which there is no more specific
forwarding information, will be forwarded to the
ports in the list, dot1qServiceReqPorts."
::= { dot1qServiceReqEntry 1 }
dot1qServiceReqPorts OBJECT-TYPE dot1qForwardUnregisteredEntry OBJECT-TYPE
SYNTAX Dot1qForwardUnregisteredEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Forwarding information for a VLAN, specifying the set
of ports to which all multicasts for which there is no
more specific forwarding information shall be forwarded.
This is configured statically by management or
dynamically by GMRP."
INDEX { dot1qVlanIndex }
::= { dot1qForwardUnregisteredTable 1 }
Dot1qForwardUnregisteredEntry ::=
SEQUENCE {
dot1qForwardUnregisteredPorts
PortList,
dot1qForwardUnregisteredStaticPorts
PortList
}
dot1qForwardUnregisteredPorts 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 VLAN to which
to which frames destined for this Service Requirement multicast group-addressed frames for which there is no
are allowed to be forwarded. This includes ports for more specific forwarding information will be forwarded.
which the Service Requirement has been learnt This includes ports for which this need has been
dynamically, by GMRP, or configured statically by determined dynamically by GMRP, or configured statically
management." by management."
::= { dot1qServiceReqEntry 2 } ::= { dot1qForwardUnregisteredEntry 1 }
dot1qForwardUnregisteredStaticPorts OBJECT-TYPE
dot1qServiceReqStaticPorts 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 "The set of ports configured by management, in this
Filtering Database, to which frames destined for this VLAN, to which multicast group-addressed frames for
Service Requirement are allowed to be forwarded. Ports which there is no more specific forwarding information
entered in this list will also appear in the complete are to be forwarded. Ports entered in this list will
set shown by dot1qServiceReqPorts. This value will be also appear in the complete set shown by
restored after the device is reset." dot1qForwardUnregisteredPorts. This value will be
::= { dot1qServiceReqEntry 3 } restored after the device is reset. The default value
is a string of zeros of appropriate length, although
this has no effect with the default value of
dot1qForwardAllStaticPorts."
::= { dot1qForwardUnregisteredEntry 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The Static (Destination-Address Filtering) Database -- The Static (Destination-Address Filtering) Database
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qStaticTable OBJECT-TYPE dot1qStaticUnicastTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qStaticEntry SYNTAX SEQUENCE OF Dot1qStaticUnicastEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing filtering information for each "A table containing filtering information for Unicast
Filtering Database, configured into the device by (local MAC addresses for each Filtering Database, configured
or network) management specifying the set of ports to into the device by (local or network) management
which frames received from specific ports and containing specifying the set of ports to which frames received
specific destination addresses are allowed to be from specific ports and containing specific unicast
forwarded. The value of zero in this table as the port destination addresses are allowed to be forwarded. A
number from which frames with a specific destination value of zero in this table as the port number from
address are received, is used to specify all ports for which frames with a specific destination address are
which there is no specific entry in this table for that received, is used to specify all ports for which there
particular destination address. Entries are valid for is no specific entry in this table for that particular
unicast and for group/broadcast addresses." destination address. Entries are valid for unicast
addresses only."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.7.7" "IEEE 802.1Q/D10 12.7.7, 802.1D/D16 7.9.1"
::= { dot1qStatic 1 } ::= { dot1qStatic 1 }
dot1qStaticEntry OBJECT-TYPE dot1qStaticUnicastEntry OBJECT-TYPE
SYNTAX Dot1qStaticEntry 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
containing a specific destination address are allowed to containing a specific unicast destination address are
be forwarded." allowed to be forwarded."
INDEX { INDEX {
dot1qFdbId, dot1qFdbId,
dot1qStaticAddress, dot1qStaticUnicastAddress,
dot1qStaticReceivePort dot1qStaticUnicastReceivePort
} }
::= { dot1qStaticTable 1 } ::= { dot1qStaticUnicastTable 1 }
Dot1qStaticEntry ::= Dot1qStaticUnicastEntry ::=
SEQUENCE { SEQUENCE {
dot1qStaticAddress dot1qStaticUnicastAddress
MacAddress, MacAddress,
dot1qStaticReceivePort dot1qStaticUnicastReceivePort
INTEGER, INTEGER,
dot1qStaticAllowedToGoTo dot1qStaticUnicastAllowedToGoTo
PortList, PortList,
dot1qStaticStatus dot1qStaticUnicastStatus
INTEGER INTEGER
} }
dot1qStaticAddress OBJECT-TYPE dot1qStaticUnicastAddress OBJECT-TYPE
SYNTAX MacAddress SYNTAX MacAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination MAC address in a frame to which this "The destination MAC address in a frame to which this
entry's filtering information applies. This object can entry's filtering information applies. This object must
take the value of a unicast address, a group address or take the value of a unicast address."
the broadcast address." ::= { dot1qStaticUnicastEntry 1 }
::= { dot1qStaticEntry 1 }
-- ------------------------------------------------------------- dot1qStaticUnicastReceivePort OBJECT-TYPE
-- This is not defined in 802.1Q/D9 - see section 12.7.7. SYNTAX INTEGER (0..65535)
-- Do we need it? MAX-ACCESS not-accessible
-- ------------------------------------------------------------- STATUS current
DESCRIPTION
"Either the value '0', or the port number of the port
from which a frame must be received in order for this
entry's filtering information to apply. A value of zero
indicates that this entry applies on all ports of the
device for which there is no other applicable entry."
::= { dot1qStaticUnicastEntry 2 }
dot1qStaticReceivePort OBJECT-TYPE dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports to which frames received from a
specific port and destined for a specific unicast MAC
address are allowed to be forwarded. The default value
of this object is a string of ones of appropriate
length."
::= { dot1qStaticUnicastEntry 3 }
dot1qStaticUnicastStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
invalid(2),
permanent(3),
deleteOnReset(4),
deleteOnTimeout(5)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the status of this entry.
other(1) - this entry is currently in use but
the conditions under which it will remain
so differ from the following values.
invalid(2) - writing this value to the object
removes the corresponding entry.
permanent(3) - this entry is currently in use
and will remain so after the next reset of
the bridge.
deleteOnReset(4) - this entry is currently in
use and will remain so until the next
reset of the bridge.
deleteOnTimeout(5) - this entry is currently in
use and will remain so until it is aged out."
DEFVAL { permanent }
::= { dot1qStaticUnicastEntry 4 }
dot1qStaticMulticastTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qStaticMulticastEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing filtering information for Multicast
and Broadcast MAC addresses for each VLAN, configured
into the device by (local or network) management
specifying the set of ports to which frames received
from specific ports and containing specific Multicast
and Broadcast destination addresses are allowed to be
forwarded. A value of zero in this table as the port
number from which frames with a specific destination
address are received, is used to specify all ports for
which there is no specific entry in this table for that
particular destination address. Entries are valid for
Multicast and Broadcast addresses only."
REFERENCE
"IEEE 802.1Q/D10 12.7.7, 802.1D/D16 7.9.1"
::= { dot1qStatic 2 }
dot1qStaticMulticastEntry OBJECT-TYPE
SYNTAX Dot1qStaticMulticastEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Filtering information configured into the device by
(local or network) management specifying the set of
ports to which frames received from this specific port
for this VLAN and containing this Multicast or Broadcast
destination address are allowed to be forwarded."
INDEX {
dot1qVlanIndex,
dot1qStaticMulticastAddress,
dot1qStaticMulticastReceivePort
}
::= { dot1qStaticMulticastTable 1 }
Dot1qStaticMulticastEntry ::=
SEQUENCE {
dot1qStaticMulticastAddress
MacAddress,
dot1qStaticMulticastReceivePort
INTEGER,
dot1qStaticMulticastStaticEgressPorts
PortList,
dot1qStaticMulticastForbiddenEgressPorts
PortList,
dot1qStaticMulticastStatus
INTEGER
}
dot1qStaticMulticastAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The destination MAC address in a frame to which this
entry's filtering information applies. This object must
take the value of a Multicast or Broadcast address."
::= { dot1qStaticMulticastEntry 1 }
dot1qStaticMulticastReceivePort OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Either the value '0', or the port number of the port "Either the value '0', or the port number of the port
from which a frame must be received in order for this from which a frame must be received in order for this
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."
::= { dot1qStaticEntry 2 } ::= { dot1qStaticMulticastEntry 2 }
dot1qStaticAllowedToGoTo OBJECT-TYPE dot1qStaticMulticastStaticEgressPorts 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 to which frames received from a
specific port and destined for a specific MAC address, specific port and destined for a specific Multicast or
are allowed to be forwarded. The default value of this Broadcast MAC address must be forwarded, regardless of
object is a string of ones of appropriate length." any dynamic information e.g. from GMRP. A port may not
::= { dot1qStaticEntry 3 } be added in this set if it is already a member of the
set of ports in dot1qStaticMulticastForbiddenEgressPorts.
The default value of this object is a string of ones of
appropriate length."
::= { dot1qStaticMulticastEntry 3 }
dot1qStaticStatus OBJECT-TYPE dot1qStaticMulticastForbiddenEgressPorts OBJECT-TYPE
SYNTAX PortList
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The set of ports to which frames received from a
specific port and destined for a specific Multicast or
Broadcast MAC address must not be forwarded, regardless
of any dynamic information e.g. from GMRP. A port may
not be added in this set if it is already a member of the
set of ports in dot1qStaticMulticastStaticEgressPorts.
The default value of this object is a string of zeros of
appropriate length."
::= { dot1qStaticMulticastEntry 4 }
dot1qStaticMulticastStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
invalid(2), invalid(2),
permanent(3), permanent(3),
deleteOnReset(4), deleteOnReset(4),
deleteOnTimeout(5) deleteOnTimeout(5)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 53, line 26 skipping to change at page 60, line 43
removes the corresponding entry. removes the corresponding entry.
permanent(3) - this entry is currently in use permanent(3) - this entry is currently in use
and will remain so after the next reset of and will remain so after the next reset of
the bridge. the bridge.
deleteOnReset(4) - this entry is currently in deleteOnReset(4) - this entry is currently in
use and will remain so until the next use and will remain so until the next
reset of the bridge. reset of the bridge.
deleteOnTimeout(5) - this entry is currently in deleteOnTimeout(5) - this entry is currently in
use and will remain so until it is aged out." use and will remain so until it is aged out."
DEFVAL { permanent } DEFVAL { permanent }
::= { dot1qStaticEntry 4 } ::= { dot1qStaticMulticastEntry 5 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The Current VLAN Database -- The Current VLAN Database
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qVlanNumDeletes OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times a VLAN entry has been deleted from
the dot1qVlanCurrentTable (for any reason). If an entry
is deleted, then inserted, and then deleted, this
counter will be incremented by 2."
::= { dot1qVlan 1 }
dot1qVlanTable OBJECT-TYPE dot1qVlanCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qVlanEntry SYNTAX SEQUENCE OF Dot1qVlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing current configuration information "A table containing current configuration information
for each VLAN currently configured into the device by for each VLAN currently configured into the device by
(local or network) management, or dynamically created (local or network) management, or dynamically created
as a result of GVRP requests received." as a result of GVRP requests received."
::= { dot1qVlan 1 } ::= { dot1qVlan 2 }
dot1qVlanEntry OBJECT-TYPE dot1qVlanEntry OBJECT-TYPE
SYNTAX Dot1qVlanEntry SYNTAX Dot1qVlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information for a VLAN configured into the device by "Information for a VLAN configured into the device by
(local or network) management, or dynamically created (local or network) management, or dynamically created
as a result of GVRP requests received." as a result of GVRP requests received."
INDEX { dot1qVlanIfIndex } INDEX { dot1qVlanTimeMark, dot1qVlanIndex }
::= { dot1qVlanTable 1 } ::= { dot1qVlanCurrentTable 1 }
Dot1qVlanEntry ::= Dot1qVlanEntry ::=
SEQUENCE { SEQUENCE {
dot1qVlanIfIndex dot1qVlanTimeMark
VlanIfIndex, TimeFilter,
dot1qVlanId dot1qVlanIndex
INTEGER, VlanIndex,
dot1qVlanFdbId dot1qVlanFdbId
INTEGER, INTEGER,
dot1qVlanOperEgressPorts dot1qVlanCurrentEgressPorts
PortList, PortList,
dot1qVlanOperUntaggedPorts dot1qVlanCurrentUntaggedPorts
PortList, PortList,
dot1qVlanBridgeUpTime
TimeTicks,
dot1qVlanStatus dot1qVlanStatus
INTEGER INTEGER
} }
dot1qVlanIfIndex OBJECT-TYPE dot1qVlanTimeMark OBJECT-TYPE
SYNTAX VlanIfIndex SYNTAX TimeFilter
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value refering to the ifTable entry for "A TimeFilter for this entry. See the TimeFilter
the virtual interface presented by this VLAN." textual convention to see how this works."
::= { dot1qVlanEntry 1 } ::= { dot1qVlanEntry 1 }
dot1qVlanId OBJECT-TYPE dot1qVlanIndex OBJECT-TYPE
SYNTAX INTEGER (0|1..4094) SYNTAX VlanIndex
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VLAN ID used in the VLAN Tag header for this VLAN. "The VLAN-ID or other identifier refering to this VLAN."
A value of 0 indicates none has been assigned."
::= { dot1qVlanEntry 2 } ::= { dot1qVlanEntry 2 }
dot1qVlanFdbId OBJECT-TYPE dot1qVlanFdbId OBJECT-TYPE
SYNTAX INTEGER (1..4095) SYNTAX INTEGER (1..4095)
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 }
dot1qVlanOperEgressPorts 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/D9 12.10.2.1"
::= { dot1qVlanEntry 4 } ::= { dot1qVlanEntry 4 }
dot1qVlanCurrentUntaggedPorts OBJECT-TYPE
dot1qVlanOperUntaggedPorts 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/D9 12.10.2.1"
::= { dot1qVlanEntry 5 } ::= { dot1qVlanEntry 5 }
-- -------------------------------------------------------------
-- Do we need this Bridge Up time?
-- -------------------------------------------------------------
dot1qVlanBridgeUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sysUpTime value when this entry was created."
::= { dot1qVlanEntry 6 }
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 conditions under which it will remain the conditions under which it will remain
so differ from the following values. so differ from the following values.
permanent(2) - this entry, corresponding to an permanent(2) - this entry, corresponding to an
entry in dot1qVlanStaticTable, is currently entry in dot1qVlanStaticTable, is currently
in use and will remain so after the next in use and will remain so after the next
reset of the device. reset of the device.
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."
::= { dot1qVlanEntry 7 } ::= { 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
DESCRIPTION DESCRIPTION
"A table containing static configuration information for "A table containing static configuration information for
each VLAN configured into the device by (local or each VLAN configured into the device by (local or
network) management. All entries are permanent and will network) management. All entries are permanent and will
be restored after the device is reset." be restored after the device is reset."
::= { dot1qVlan 2 } ::= { dot1qVlan 3 }
dot1qVlanStaticEntry OBJECT-TYPE dot1qVlanStaticEntry OBJECT-TYPE
SYNTAX Dot1qVlanStaticEntry SYNTAX Dot1qVlanStaticEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Static information for a VLAN configured into the "Static information for a VLAN configured into the
device by (local or network) management." device by (local or network) management."
INDEX { dot1qVlanIfIndex } INDEX { dot1qVlanIndex }
::= { dot1qVlanStaticTable 1 } ::= { dot1qVlanStaticTable 1 }
Dot1qVlanStaticEntry ::= Dot1qVlanStaticEntry ::=
SEQUENCE { SEQUENCE {
dot1qVlanStaticVlanId
INTEGER,
dot1qVlanStaticName dot1qVlanStaticName
DisplayString, DisplayString,
dot1qVlanFixedPorts dot1qVlanStaticEgressPorts
PortList, PortList,
dot1qVlanForbiddenPorts dot1qVlanForbiddenEgressPorts
PortList, PortList,
dot1qVlanAdminUntaggedPorts dot1qVlanStaticUntagged
PortList, PortList,
dot1qVlanStaticRowStatus dot1qVlanStaticRowStatus
RowStatus RowStatus
} }
dot1qVlanStaticVlanId OBJECT-TYPE
SYNTAX INTEGER (0|1..4094)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A unique VLAN ID used in the VLAN Tag for this VLAN, or
a value of 0 indicating that none has been assigned.
This may only be written as the row is created."
REFERENCE
"IEEE 802.1Q/D9: Section 12.7.7.3"
::= { dot1qVlanStaticEntry 1 }
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
"A unique, administratively assigned string, which may "An administratively assigned string, which may be used
be used to identify the VLAN. This is reflected back to identify the VLAN."
(as read-only) in the ifDescr field for the ifTable
entry for this VLAN referenced by dot1qVlanIfIndex."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.2.1" "IEEE 802.1Q/D9 12.10.2.1"
::= { dot1qVlanStaticEntry 2 } ::= { dot1qVlanStaticEntry 1 }
dot1qVlanFixedPorts 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 set of ports which are permanently assigned to the
this VLAN by management. The default value of this egress list for this VLAN by management. Changes to a
object is a string of zeros of appropriate length." bit in this object affect the per-port per-VLAN
Registrar control for Registration Fixed for the
relevant GVRP state machine on each port. The default
value of this object is a string of zeros of appropriate
length, indicating not fixed."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.7.7.3" "IEEE 802.1Q/D10 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 3 } ::= { dot1qVlanStaticEntry 2 }
dot1qVlanForbiddenPorts 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 from joining "The set of ports which are prohibited by management
this VLAN by management. The default value of this from being included in the egress list for this VLAN.
object is a string of zeros of appropriate length." Changes to this object that cause a port to be included
or excluded affect the per-port per-VLAN Registrar
control for Registration Forbidden for the relevant
GVRP state machine on each port. The default value of
this object is a string of zeros of appropriate length,
excluding all ports from the forbidden set."
REFERENCE REFERENCE
"IEEE 802.1Q/D9: Section 12.7.7.3" "IEEE 802.1Q/D10 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 4 } ::= { dot1qVlanStaticEntry 3 }
dot1qVlanAdminUntaggedPorts OBJECT-TYPE dot1qVlanStaticUntagged 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 traffic for this "The set of ports which should transmit egress packets
VLAN as untagged frames. The default value of this for this VLAN as untagged. The default value of this
object is a string of appropriate length, with each bit object for the default VLAN (VlanId 001) is a string
set to one for those ports which define this VLAN as of appropriate length including all ports. There is no
their PVID, otherwise the bit is set to zero." specified default for other VLANs. If a device cannot
support a value being set then its agent will reject the
set operation."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.2.1" "IEEE 802.1Q/D9 12.10.2.1"
::= { dot1qVlanStaticEntry 5 } ::= { 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 6 } ::= { dot1qVlanStaticEntry 5 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- 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 3 } ::= { dot1qVlan 4 }
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, VlanId,
dot1qPortAcceptableFrameTypes dot1qPortAcceptableFrameTypes
INTEGER, INTEGER,
dot1qPortIngressFiltering dot1qPortIngressFiltering
TruthValue, TruthValue,
dot1qPortGvrpAdminStatus dot1qPortGvrpStatus
EnabledStatus,
dot1qPortGvrpOperStatus
EnabledStatus, EnabledStatus,
dot1qPortGvrpFailedRegistrations dot1qPortGvrpFailedRegistrations
Counter32, Counter32,
dot1qPortGvrpLastPduOrigin dot1qPortGvrpLastPduOrigin
MacAddress MacAddress
} }
dot1qPvid OBJECT-TYPE dot1qPvid OBJECT-TYPE
SYNTAX VlanId SYNTAX VlanId
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 60, line 22 skipping to change at page 67, line 28
} }
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, This control does not affect incoming BPDU frames, such
such as GARP and STP." as GARP and STP."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.1.3" "IEEE 802.1Q/D9 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
skipping to change at page 60, line 45 skipping to change at page 68, line 6
frames for VLANs not in the port egress filters. When frames for VLANs not in the port egress filters. When
false(2), the port will accept all incoming frames. false(2), the port will accept all incoming frames.
This control does not affect incoming BPDU frames, such This control does not affect incoming BPDU frames, such
as GARP and STP." as GARP and STP."
REFERENCE REFERENCE
"IEEE 802.1Q/D9 12.10.1.4" "IEEE 802.1Q/D9 12.10.1.4"
DEFVAL { false } DEFVAL { false }
::= { dot1qPortVlanEntry 3 } ::= { dot1qPortVlanEntry 3 }
dot1qPortGvrpAdminStatus OBJECT-TYPE dot1qPortGvrpStatus 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 state of GVRP operation on this port. The value
GVRP, on this port. The value enabled(1) indicates that enabled(1) indicates that GVRP is enabled on this port,
GVRP should be enabled on this port, if GVRP is also as long as dot1qGvrpStatus is also enabled for this
enabled for this device. When disabled(2), GVRP is device. When disabled(2) but dot1qGvrpStatus is still
disabled on this port." enabled for the device, GVRP is disabled on this port:
any GVRP packets received will be silently discarded and
no GVRP registrations will be propagated from other
ports. This object affects all GVRP Applicant and
Registrar state machines on this port. A transition
from disabled(2) to enabled(1) will cause a reset of all
GVRP state machines on this port and zeroing of all
related counters."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1qPortVlanEntry 4 } ::= { dot1qPortVlanEntry 4 }
dot1qPortGvrpOperStatus OBJECT-TYPE
SYNTAX EnabledStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current operational status of GVRP on this port."
::= { dot1qPortVlanEntry 5 }
dot1qPortGvrpFailedRegistrations OBJECT-TYPE dot1qPortGvrpFailedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of failed GVRP registrations, for any "The total number of failed GVRP registrations, for any
reason, on this port." reason, on this port."
::= { dot1qPortVlanEntry 6 } ::= { dot1qPortVlanEntry 6 }
dot1qPortGvrpLastPduOrigin OBJECT-TYPE dot1qPortGvrpLastPduOrigin OBJECT-TYPE
skipping to change at page 62, line 7 skipping to change at page 69, line 12
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 REFERENCE
"IEEE 802.1Q/D9: Section 12.6.1" "IEEE 802.1Q/D9: Section 12.6.1"
::= { dot1qVlan 4 } ::= { 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, dot1qVlanIfIndex } INDEX { dot1dBasePort, dot1qVlanIndex }
::= { dot1qPortVlanStatisticsTable 1 } ::= { dot1qPortVlanStatisticsTable 1 }
Dot1qPortVlanStatisticsEntry ::= Dot1qPortVlanStatisticsEntry ::=
SEQUENCE { SEQUENCE {
dot1qFramesReceived dot1qFramesReceived
Counter32, Counter32,
dot1qOctetsReceived dot1qOctetsReceived
Counter32, Counter32,
dot1qForwardOutbound dot1qForwardOutbound
Counter32, Counter32,
skipping to change at page 64, line 27 skipping to change at page 71, line 31
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 REFERENCE
"IEEE 802.1Q/D9: Section 12.6.1" "IEEE 802.1Q/D9: Section 12.6.1"
::= { dot1qVlan 5 } ::= { 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, dot1qVlanIfIndex } INDEX { dot1dBasePort, dot1qVlanIndex }
::= { dot1qPortVlanHCStatisticsTable 1 } ::= { dot1qPortVlanHCStatisticsTable 1 }
Dot1qPortVlanHCStatisticsEntry ::= Dot1qPortVlanHCStatisticsEntry ::=
SEQUENCE { SEQUENCE {
dot1qHCFramesReceived dot1qHCFramesReceived
Counter64, Counter64,
dot1qHCOctetsReceived dot1qHCOctetsReceived
Counter64, Counter64,
dot1qHCForwardOutbound dot1qHCForwardOutbound
Counter64, Counter64,
skipping to change at page 66, line 42 skipping to change at page 73, line 46
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames discarded by this port and VLAN "The number of frames discarded by this port and VLAN
due to ingress filtering." due to ingress filtering."
::= { dot1qPortVlanHCStatisticsEntry 8 } ::= { dot1qPortVlanHCStatisticsEntry 8 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The VLAN Learning Constraints Table -- The VLAN Learning Constraints Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Editor: This table is defined in a slightly different sense
-- to that in IEEE 802.1Q, combining the two different types of dot1qLearningConstraintsLastChange OBJECT-TYPE
-- constraint for Independent and Shared into a single table. 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/D9 12.10.3.1"
::= { dot1qVlan 6 } ::= { 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 }
Dot1qLearningConstraintsEntry ::= Dot1qLearningConstraintsEntry ::=
SEQUENCE { SEQUENCE {
dot1qConstraintVlan dot1qConstraintVlan
VlanIfIndex, VlanIndex,
dot1qConstraintSet dot1qConstraintSet
INTEGER, INTEGER,
dot1qConstraintType dot1qConstraintType
INTEGER, INTEGER,
dot1qConstraintStatus dot1qConstraintStatus
RowStatus RowStatus
} }
dot1qConstraintVlan OBJECT-TYPE dot1qConstraintVlan OBJECT-TYPE
SYNTAX VlanIfIndex SYNTAX VlanIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value refering to the ifTable entry for the "The index of the row in dot1qVlanCurrentTable for the
VLAN constrained by this entry." VLAN constrained by this entry."
::= { dot1qLearningConstraintsEntry 1 } ::= { dot1qLearningConstraintsEntry 1 }
dot1qConstraintSet OBJECT-TYPE dot1qConstraintSet OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identity of the constraint set to which "The identity of the constraint set to which
dot1qConstraintVlan belongs. These values may be chosen dot1qConstraintVlan belongs. These values may be chosen
skipping to change at page 68, line 42 skipping to change at page 76, line 9
::= { dot1qLearningConstraintsEntry 4 } ::= { dot1qLearningConstraintsEntry 4 }
dot1qConstraintSetDefault OBJECT-TYPE dot1qConstraintSetDefault OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identity of the constraint set to which a VLAN "The identity of the constraint set to which a VLAN
belongs, if there is not an explicit entry for that VLAN belongs, if there is not an explicit entry for that VLAN
in dot1qLearningConstraintsTable." in dot1qLearningConstraintsTable."
::= { dot1qVlan 7 } ::= { dot1qVlan 9 }
dot1qConstraintTypeDefault OBJECT-TYPE dot1qConstraintTypeDefault OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
independent(1), independent(1),
shared(2) shared(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of constraint set to which a VLAN belongs, if "The type of constraint set to which a VLAN belongs, if
there is not an explicit entry for that VLAN in there is not an explicit entry for that VLAN in
dot1qLearningConstraintsTable. The types are as defined dot1qLearningConstraintsTable. The types are as defined
for dot1qConstraintType." for dot1qConstraintType."
::= { dot1qVlan 8 } ::= { dot1qVlan 10 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- IEEE 802.1Q MIB - Conformance Information -- IEEE 802.1Q MIB - Conformance Information
-- ------------------------------------------------------------- -- -------------------------------------------------------------
qBridgeConformance OBJECT IDENTIFIER ::= { qBridgeMIB 2 } qBridgeConformance OBJECT IDENTIFIER ::= { qBridgeMIB 2 }
qBridgeGroups OBJECT IDENTIFIER ::= { qBridgeConformance 1 } qBridgeGroups OBJECT IDENTIFIER ::= { qBridgeConformance 1 }
qBridgeCompliances OBJECT IDENTIFIER qBridgeCompliances OBJECT IDENTIFIER
skipping to change at page 69, line 34 skipping to change at page 76, line 46
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- units of conformance -- units of conformance
-- ------------------------------------------------------------- -- -------------------------------------------------------------
qBridgeBaseGroup OBJECT-GROUP qBridgeBaseGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qVlanVersionNumber, dot1qVlanVersionNumber,
dot1qMaxVlanId, dot1qMaxVlanId,
dot1qMaxSupportedVlans, dot1qMaxSupportedVlans,
dot1qNumVlans, dot1qNumVlans,
dot1qResetToDefaults, dot1qGvrpStatus
dot1qGvrpAdminStatus
} }
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 }
qBridgeTpFdbGroup OBJECT-GROUP
OBJECTS {
dot1qTpFdbClear
}
STATUS current
DESCRIPTION
"A collection of objects providing device level control
for the Filtering Databases."
::= { qBridgeGroups 2 }
qBridgeFdbGroup OBJECT-GROUP
OBJECTS {
dot1qFdbClear
}
STATUS current
DESCRIPTION
"A collection of objects providing per FDB control
for the Filtering Databases."
::= { qBridgeGroups 3 }
qBridgeFdbUnicastGroup OBJECT-GROUP qBridgeFdbUnicastGroup OBJECT-GROUP
OBJECTS { OBJECTS {
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 4 } ::= { qBridgeGroups 2 }
qBridgeFdbMulticastGroup OBJECT-GROUP qBridgeFdbMulticastGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qTpGroupAllowedToGoTo, dot1qTpGroupAllowedToGoTo,
dot1qTpGroupGmrp, dot1qTpGroupLearnt
dot1qTpGroupIgmp
} }
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 5 } ::= { qBridgeGroups 3 }
qBridgeServiceRequirementsGroup OBJECT-GROUP qBridgeServiceRequirementsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qServiceReqPorts, dot1qForwardAllPorts,
dot1qServiceReqStaticPorts dot1qForwardAllStaticPorts,
dot1qForwardUnregisteredPorts,
dot1qForwardUnregisteredStaticPorts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
service requirements, learnt dynamically or statically service requirements, learnt dynamically or statically
configured by management, in each Filtering Database." configured by management, in each Filtering Database."
::= { qBridgeGroups 6 } ::= { qBridgeGroups 4 }
qBridgeFdbStaticGroup OBJECT-GROUP qBridgeFdbStaticGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qStaticAllowedToGoTo, dot1qStaticUnicastAllowedToGoTo,
dot1qStaticStatus dot1qStaticUnicastStatus,
dot1qStaticMulticastStaticEgressPorts,
dot1qStaticMulticastForbiddenEgressPorts,
dot1qStaticMulticastStatus
} }
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." management, in each Filtering Database or VLAN."
::= { qBridgeGroups 7 } ::= { qBridgeGroups 5 }
qBridgeVlanGroup OBJECT-GROUP qBridgeVlanGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qVlanId,
dot1qVlanFdbId, dot1qVlanFdbId,
dot1qVlanOperEgressPorts, dot1qVlanCurrentEgressPorts,
dot1qVlanOperUntaggedPorts, dot1qVlanCurrentUntaggedPorts,
dot1qVlanBridgeUpTime,
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 8 } ::= { qBridgeGroups 6 }
qBridgeVlanStaticGroup OBJECT-GROUP qBridgeVlanStaticGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qVlanStaticVlanId,
dot1qVlanStaticName, dot1qVlanStaticName,
dot1qVlanFixedPorts, dot1qVlanStaticEgressPorts,
dot1qVlanForbiddenPorts, dot1qVlanForbiddenEgressPorts,
dot1qVlanAdminUntaggedPorts, dot1qVlanStaticUntagged,
dot1qVlanStaticRowStatus dot1qVlanStaticRowStatus
} }
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 9 } ::= { qBridgeGroups 7 }
qBridgePortGroup OBJECT-GROUP qBridgePortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qPvid, dot1qPvid,
dot1qPortAcceptableFrameTypes, dot1qPortAcceptableFrameTypes,
dot1qPortIngressFiltering, dot1qPortIngressFiltering,
dot1qPortGvrpAdminStatus, dot1qPortGvrpStatus,
dot1qPortGvrpOperStatus,
dot1qPortGvrpFailedRegistrations, dot1qPortGvrpFailedRegistrations,
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 10 } ::= { qBridgeGroups 8 }
qBridgeVlanStatisticsGroup OBJECT-GROUP qBridgeVlanStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qOctetsReceived dot1qOctetsReceived
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing per-port octet "A collection of objects providing per-port octet
statistics for all VLANs currently configured on statistics for all VLANs currently configured on
this device." this device."
::= { qBridgeGroups 11 } ::= { qBridgeGroups 9 }
qBridgeVlanPacketStatisticsGroup OBJECT-GROUP qBridgeVlanPacketStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qFramesReceived, dot1qFramesReceived,
dot1qForwardOutbound, dot1qForwardOutbound,
dot1qDiscardInbound, dot1qDiscardInbound,
dot1qDiscardNoBuffers, dot1qDiscardNoBuffers,
dot1qDiscardTransitDelayExceeded, dot1qDiscardTransitDelayExceeded,
dot1qDiscardError, dot1qDiscardError,
dot1qDiscardOnIngressFiltering 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 12 } ::= { qBridgeGroups 10 }
qBridgeVlanHCStatisticsGroup OBJECT-GROUP qBridgeVlanHCStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qHCOctetsReceived dot1qHCOctetsReceived
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing per-port octet count "A collection of objects providing per-port octet count
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 13 } ::= { qBridgeGroups 11 }
qBridgeVlanHCPacketStatisticsGroup OBJECT-GROUP qBridgeVlanHCPacketStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qHCFramesReceived, dot1qHCFramesReceived,
dot1qHCForwardOutbound, dot1qHCForwardOutbound,
dot1qHCDiscardInbound, dot1qHCDiscardInbound,
dot1qHCDiscardNoBuffers, dot1qHCDiscardNoBuffers,
dot1qHCDiscardTransitDelayExceeded, dot1qHCDiscardTransitDelayExceeded,
dot1qHCDiscardError, dot1qHCDiscardError,
dot1qHCDiscardOnIngressFiltering 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 14 } ::= { qBridgeGroups 12 }
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 15 } ::= { qBridgeGroups 13 }
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 16 } ::= { qBridgeGroups 14 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- 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."
skipping to change at page 75, line 4 skipping to change at page 81, line 39
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."
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." extended filtering services. All objects must be
read-write if extended-filtering services are
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 GROUP qBridgeVlanPacketStatisticsGroup
skipping to change at page 75, line 41 skipping to change at page 82, line 34
DESCRIPTION DESCRIPTION
"This group is optional. It should be implemented "This group is optional. It should be implemented
if qBridgeVlanPacketStatisticsGroup is implemented if qBridgeVlanPacketStatisticsGroup is implemented
and if the network interface to which this bridge and if the network interface to which this bridge
port is attached has the value of the corresponding port is attached has the value of the corresponding
instance of ifSpeed greater than 650,000,000 instance of ifSpeed greater than 650,000,000
bits/second." bits/second."
GROUP qBridgeLearningConstraintsGroup GROUP qBridgeLearningConstraintsGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is mandatory for devices implementing
both Independent VLAN Learning (IVL) and Shared
VLAN Learning (SVL) modes of operation of the
filtering database."
GROUP qBridgeLearningConstraintDefaultGroup GROUP qBridgeLearningConstraintDefaultGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is mandatory for devices implementing
both Independent VLAN Learning (IVL) and Shared
VLAN Learning (SVL) modes of operation of the
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 78, line 8 skipping to change at page 85, line 8
802.1 working group during the definition of the IEEE 802.1D updates 802.1 working group during the definition of the IEEE 802.1D updates
[12] and IEEE 802.1Q [13]. Some ideas were also taken from an [12] and IEEE 802.1Q [13]. Some ideas were also taken from an
earlier Internet Draft for a VLAN MIB [16] from I. Jeyasubramanian. 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] Cerf, V., "IAB Recommendations for the Development of Internet
Network Management Standards", RFC 1052, NRI, April 1988. Network Management Standards", RFC 1052, April 1988.
[2] Cerf, V., "Report of the Second Ad Hoc Network Management Review [2] Cerf, V., "Report of the Second Ad Hoc Network Management Review
Group", RFC 1109, NRI, August 1989. Group", RFC 1109, August 1989.
[3] Rose M., and K. McCloghrie, "Structure and Identification of [3] Rose M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", STD 16, RFC Management Information for TCP/IP-based internets", STD 16, RFC
1155, Performance Systems International, Hughes LAN Systems, May 1155, May 1990.
1990.
[4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, SNMP Research, Network Management Protocol", STD 15, RFC 1157, May 1990.
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[5] McCloghrie K., and M. Rose, Editors, "Management Information [5] McCloghrie K., and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets", STD 17, Base for Network Management of TCP/IP-based internets", STD 17,
RFC 1213, Performance Systems International, March 1991. RFC 1213, March 1991.
[6] Information processing systems - Open Systems Interconnection - [6] 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 - [7] 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", [8] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
STD 16, RFC 1212, Performance Systems International, Hughes LAN STD 16, RFC 1212, March 1991.
Systems, March 1991.
[9] Rose, M., Editor, "A Convention for Defining Traps for use with [9] Rose, M., Editor, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, Performance Systems International, March the SNMP", RFC 1215, March 1991.
1991.
[10] ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges". [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 [11] 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 Dynamic Multicast Filtering)", November 1997. and Dynamic Multicast Filtering)", March 1998.
[12] ANSI/IEEE Draft Standard P802.1Q/D9, "IEEE Standards for Local [12] ANSI/IEEE Draft Standard P802.1Q/D10, "IEEE Standards for Local
and Metropolitan Area Networks: Virtual Bridged Local Area and Metropolitan Area Networks: Virtual Bridged Local Area
Networks", February 1998. Networks", March 1998.
[13] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K., [13] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K.,
"Definitions of Managed Objects for Bridges", RFC 1493, cisco "Definitions of Managed Objects for Bridges", RFC 1493, July
Systems, Digital Equipment, Hughes LAN Systems, July 1993. 1993.
[14] McCloghrie, K., Kastenholz, F. "Evolution of the Interfaces [14] McCloghrie, K., Kastenholz, F. "Evolution of the Interfaces
Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, Group of MIB-II", RFC 1573, January 1994.
January 1994.
[15] Decker, E., McCloghrie, K., Langille, P., Rijsinghani, A. [15] 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, cisco Systems, Hughes LAN Systems, Digital Equipment, 1525, September 1993
September 1993
[16] Jeyasubramanian, I., "Definitions of Managed Objects for IEEE [16] Jeyasubramanian, I., "Definitions of Managed Objects for IEEE
802.1Q Virtual LAN Bridges", draft-jeya-vlan-8021q-mib-01.txt, 802.1Q Virtual LAN Bridges", draft-jeya-vlan-8021q-mib-01.txt,
FSPL, June 1997 June 1997
[17] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [17] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for version 2 of the Simple Waldbusser, "Protocol Operations for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[18] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [18] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Structure of Management Information for version 2 Waldbusser, "Structure of Management Information for version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996. January 1996.
skipping to change at page 80, line 25 skipping to change at page 88, line 9
objects can have a serious effect on the operation of the network, objects can have a serious effect on the operation of the network,
including enabling or disabling forwarding of data. It is including enabling or disabling forwarding of data. It is
recommended that implementers seriously consider whether set recommended that implementers seriously consider whether set
operations should be allowed without providing, at a minimum, operations should be allowed without providing, at a minimum,
authentication of request origin. authentication of request origin.
11. Authors' Addresses 11. Authors' Addresses
Les Bell Les Bell
3Com Europe Limited 3Com Europe Limited
3Com Centre 3Com Centre, Boundary Way
Boundary Way
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
+44 (1442) 438025 +44 (1442) 438025
les_bell@3com.com Les_Bell@3Com.com
Andrew Smith Andrew Smith
Extreme Networks Extreme Networks
10460 Bandley Drive 10460 Bandley Drive
Cupertino CA 95014 Cupertino CA 95014
USA USA
+1 (408) 342 0999 +1 (408) 342 0999
andrew@extremenetworks.com andrew@extremenetworks.com
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 Rijsinghani Anil Rijhsinghani
Cabletron Systems Cabletron Systems
550 King Street, LKG2-2/Y10 550 King Street, LKG2-2/Y10
Littleton, MA 01460-1289 Littleton, MA 01460-1289
USA USA
+1 (508) 486-6786 +1 (508) 486-6786
anil@lkg.dec.com Anil.Rijhsinghani@digital.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 Network Management Framework ........................ 2
1.1 Object Definitions ......................................... 2 1.1 Object Definitions ......................................... 2
2 Overview ..................................................... 3 2 Overview ..................................................... 3
2.1 Scope ...................................................... 3 2.1 Scope ...................................................... 3
3 Structure of MIBs ............................................ 4 3 Structure of MIBs ............................................ 4
3.1 Structure of Extended Bridge MIB module .................... 4 3.1 Structure of Extended Bridge MIB module .................... 5
3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ...... 5 3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ...... 5
3.1.2 The dot1dExtBase Group ................................... 6 3.1.2 The dot1dExtBase Group ................................... 6
3.1.3 The dot1dPriority Group .................................. 6 3.1.3 The dot1dPriority Group .................................. 6
3.1.4 The dot1dGarp Group ...................................... 6 3.1.4 The dot1dGarp Group ...................................... 7
3.1.5 The dot1dGmrp Group ...................................... 7 3.1.5 The dot1dGmrp Group ...................................... 7
3.1.6 The dot1dHCPort Group .................................... 7 3.1.6 The dot1dHCPort Group .................................... 7
3.2 Structure of Virtual Bridge MIB module ..................... 7 3.2 Structure of Virtual Bridge MIB module ..................... 7
3.2.1 Relationship to IEEE 802.1Q Manageable Objects ........... 7 3.2.1 Relationship to IEEE 802.1Q Manageable Objects ........... 7
3.2.2 The dot1qBase Group ...................................... 11 3.2.2 The dot1qBase Group ...................................... 11
3.2.3 The dot1qTp Group ........................................ 11 3.2.3 The dot1qTp Group ........................................ 11
3.2.4 The dot1qStatic Group .................................... 11 3.2.4 The dot1qStatic Group .................................... 11
3.2.5 The dot1qVlan Group ...................................... 11 3.2.5 The dot1qVlan Group ...................................... 12
3.3 Textual Conventions ........................................ 11 3.3 Textual Conventions ........................................ 12
3.4 Relationship to Other MIBs ................................. 12 3.4 Relationship to Other MIBs ................................. 12
3.4.1 Relationship to the 'system' group ....................... 12 3.4.1 Relationship to the 'system' group ....................... 12
3.4.2 Relation to Interfaces MIB ............................... 12 3.4.2 Relation to Interfaces MIB ............................... 13
3.4.2.1 Layering Model ......................................... 13 3.4.2.1 Layering Model ......................................... 14
3.4.2.2 Interpretations of ifTable for VLANs ................... 14 3.4.2.2 ifStackTable ........................................... 14
3.4.2.3 ifStackTable ........................................... 15 3.4.2.3 ifRcvAddressTable ...................................... 15
3.4.2.4 ifRcvAddressTable ...................................... 15
3.4.3 Relation to Basic Bridge MIB ............................. 15 3.4.3 Relation to Basic Bridge MIB ............................. 15
3.4.3.1 The dot1dBase Group .................................... 16 3.4.3.1 The dot1dBase Group .................................... 15
3.4.3.2 The dot1dStp Group ..................................... 16 3.4.3.2 The dot1dStp Group ..................................... 15
3.4.3.3 The dot1dTp Group ...................................... 16 3.4.3.3 The dot1dTp Group ...................................... 15
3.4.3.4 The dot1dStatic Group .................................. 17 3.4.3.4 The dot1dStatic Group .................................. 16
4 Extensions to RFC 1493 ....................................... 17 4 Extensions to RFC 1493 ....................................... 17
5 Change Log and Editorial Stuff ............................... 18 5 Change Log and Editorial Stuff ............................... 17
5.1 Changes since draft-bell-bridgemib-00.txt .................. 18 5.1 Changes since draft-ietf-bridge-bridgemib-00.txt ........... 17
5.2 To Do List ................................................. 20 5.2 To Do List ................................................. 18
5.3 Open Issues ................................................ 20 5.3 Open Issues ................................................ 19
5.4 Closed Issues in his Draft ................................. 21 5.4 Issues closed in this draft ................................ 22
6 Definitions for Extended Bridge MIB .......................... 23 5.5 Issues closed in previous drafts ........................... 23
7 Definitions for Virtual Bridge MIB ........................... 39 6 Definitions for Extended Bridge MIB .......................... 25
8 Acknowledgments .............................................. 77 7 Definitions for Virtual Bridge MIB ........................... 43
9 References ................................................... 78 8 Acknowledgments .............................................. 84
10 Security Considerations ..................................... 80 9 References ................................................... 85
11 Authors' Addresses .......................................... 80 10 Security Considerations ..................................... 87
11 Authors' Addresses .......................................... 88
Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise
explain it or assist in its implmentation may be prepared, copied,
published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed
for the purpose of developing Internet standards in which case the
procedures for copyrights defined in the Internet Standards
process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not
be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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