[Docs] [txt|pdf] [Tracker] [WG] [Email] [Nits]

Versions: 00 01 02 03 04 05 RFC 2674

   Internet Draft                                                Les Bell
   Expires October 1998                                        3Com Corp.
   draft-ietf-bridge-bridgemib-00.txt                        Andrew Smith
                                                         Extreme Networks
                                                            Paul Langille
                                                          Acacia Networks
                                                         Anil Rijsinghani
                                                        Cabletron Systems
                                                         Keith McCloghrie
                                                            cisco Systems
                                                               April 1998
   
          Definitions of Managed Objects for Bridges with Traffic
          Classes, Multicast Filtering and Virtual LAN Extensions
   
   
   Status of this Memo
   
   This document is an Internet Draft.  Internet Drafts are working
   documents of the Internet Engineering Task Force (IETF), its Areas,
   and its Working Groups.  Note that other groups may also distribute
   working documents as Internet Drafts.
   
   Internet Drafts are draft documents valid for a maximum of six
   months.  Internet Drafts may be updated, replaced, or obsoleted by
   other documents at any time.  It is not appropriate to use Internet
   Drafts as reference material or to cite them other than as a "working
   draft" or "work in progress."
   
   To view the entire list of current Internet-Drafts, please check
   the "1id-abstracts.txt" listing contained in the Internet-Drafts
   Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net
   (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au
   (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu
   (US West Coast).
   
   This document is a product of the IETF's Bridge MIB Working Group.
   
   
   
   Abstract
   
   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP based internets.
   In particular it defines objects for managing MAC bridges based on
   the IEEE 802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 1]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   (VLAN) standards for bridging between Local Area Network (LAN)
   segments.  Provisions are made for support of transparent bridging.
   Provisions are also made so that these objects apply to bridges
   connected by subnetworks other than LAN segments.  This memo also
   includes several MIB modules in a manner that is compliant to the
   SNMPv2 SMI [18].
   
   
   1.  The SNMP Network Management Framework
   
   The SNMP Network Management Framework consists of several major
   components.  They are:
   
   o    RFC 1902 [18] which defines the SMI, the mechanisms used for
        describing and naming objects for the purpose of management.
        This supercedes an earlier definition of SMI in RFC 1155 [3].
   
   o    STD 17, RFC 1213 [5] defines MIB-II, the core set of managed
        objects for the Internet suite of protocols.
   
   o    RFC 1157 [4] and RFC 1905 [17] which define two versions of
        protocols providing network access to managed objects.
   
   Textual conventions are defined in RFC 1903 [19] and conformance
   statements are defined in RFC 1904 [20].
   
   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.
   
   This memo specifies MIB modules that are compliant to the SNMPv2 SMI
   [18].
   
   
   1.1.  Object Definitions
   
   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object object type is named
   by an OBJECT IDENTIFIER, an administratively assigned name.  The
   object type together with an object instance serves to uniquely
   identify a specific instantiation of the object.  For human
   convenience, we often use a textual string, termed the descriptor, to
   refer to the object type.
   
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 2]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   2.  Overview
   
   A common device present in many networks is the Bridge.  This device
   is used to connect Local Area Network segments below the network
   layer.  These devices are often known as 'layer 2 switches'.
   
   There are two major modes defined for this bridging; transparent and
   source route.  The transparent method of bridging is defined by IEEE
   802.1D-1998 [11].  Managed objects for source route bridges are
   defined in [15].
   
   IEEE 802.1D is augmented by IEEE 802.1Q-1998 [12] to provide support
   for 'virtual bridged LANs' where a single bridged physical LAN
   network may be used to support multiple logical bridged LANs, each of
   which offers a service approximately the same as that defined by
   802.1D.  Such virtual LANs (VLANs) are an integral feature of
   switched LAN networks.  A VLAN can be viewed as a group of end-
   stations on multiple LAN segments and can communicate as if they were
   on a single LAN.  IEEE 802.1Q defines port-based Virtual LANs where
   membership is determined by the bridge port on which data frames are
   received.  This memo defines the objects needed for the management of
   port-based VLANs in bridge entities.
   
   This memo defines those objects needed for the management of a
   bridging entity operating in the transparent mode, as well as some
   objects applicable to all types of bridges.  Managed objects for
   Source-Routing are defined in [15].
   
   
   2.1.  Scope
   
   This MIB includes a comprehensive set of managed objects which
   attempts to match the set defined in IEEE 802.1D and IEEE 802.1Q.
   However, to be consistent with the spirit of the SNMP Framework, a
   subjective judgement was made to omit the objects from those
   standards most 'costly' to implement in an agent and least omissions
   are described in section 3 below.
   
   Historical note:
   
   RFC 1493 used the following principles for determining inclusion of
   an object in the BRIDGE-MIB module:
   
   (1)  Start with a small set of essential objects and add only as
        further objects are needed.
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 3]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   (2)  Require objects be essential for either fault or configuration
        management.
   
   (3)  Consider evidence of current use and/or utility.
   
   (4)  Limit the total of objects.
   
   (5)  Exclude objects which are simply derivable from others in this
        or other MIBs.
   
   (6)  Avoid causing critical sections to be heavily instrumented.  The
        guideline that was followed is one counter per critical section
        per layer.
   
   
   
   
   3.  Structure of MIBs
   
   This document defines additional objects, on top of those existing in
   the base BRIDGE-MIB module from defined in RFC1493: that MIB module
   is maintained unchanged for backwards compatibility.  Section 3.4.3
   of the present document contains some recommendations regarding usage
   of objects in RFC1493 by devices implementing the enhancements
   defined here.
   
   Two MIB modules are defined here:
   
   
   (1)  Managed objects for an extended bridge MIB module P-BRIDGE-MIB
        for the traffic class and multicast filtering enhancements
        defined by IEEE 802.1D-1998.
   
   
   (2)  Managed objects for a virtual bridge MIB modeul Q-BRIDGE-MIB for
        the Virtual LAN bridging enhancements defined by IEEE 802.1Q-
        1998.
   
   
   3.1.  Structure of Extended Bridge MIB module
   
   Objects in this MIB are arranged into groups.  Each group is
   organized as a set of related objects.  The overall structure and
   assignment of objects to their groups is shown below.
   
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 4]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   3.1.1.  Relationship to IEEE 802.1D-1998 Manageable Objects
   
   This section contains a cross-reference to the objects defined in
   IEEE 802.1D-1998 [11]. It also details those objects that are not
   considered necessary in this MIB module.
   
   Some objects defined by [11] have been included in the virtual bridge
   MIB module rather than this one: dot1qTpGroupTable and
   dot1qServiceReqTable are required for virtual bridged LANs with
   additional indexing e.g. per-VLAN, per-FDB and so are not defined
   here. Instead, devices which do not implement virtual bridged LANs,
   should implement these tables with a fixed value for dot1qFdbId (the
   value 1 is recommended).  Devices which support dynamic learning of
   Multicast Group Addresses in the Filtering Database should support
   dot1qTpGroupTable.  Devices which support static or dynamic learning
   of Multicast Group Service Requirements should support
   dot1qServiceReqTable.
   
     Extended Bridge MIB Name            IEEE 802.1D Name
   
     dot1dExtended                       Bridge
       dot1dExtBase
         dot1dTrafficClassesEnabled
         dot1dTrafficClassesResetToDefaults
         dot1dGmrpAdminStatus             .ApplicantAdministrativeControl
         dot1dGarpReset
       dot1dPriority
         dot1dPortPriorityTable
           dot1dPortDefaultUserPriority   .UserPriority
           dot1dPortNumTrafficClasses
         dot1dUserPriorityRegenTable      .UserPriorityRegenerationTable
           dot1dUserPriority
           dot1dRegenUserPriority
         dot1dTrafficClassTable           .TrafficClassTable
           dot1dTrafficClass
         dot1dPortOutboundAccessPriorityTable
                                          .OutboundAccessPriorityTable
           dot1dPortOutboundAccessPriority
       dot1dGarp
         dot1dPortGarpTable
           dot1dPortGarpJoinTime          .JoinTime
           dot1dPortGarpLeaveTime         .LeaveTime
           dot1dPortGarpLeaveAllTime      .LeaveAllTime
       dot1dGmrp
         dot1dPortGmrpTable
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 5]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           dot1dPortGmrpAdminStatus       .ApplicantAdministrativeControl
           dot1dPortGmrpFailedRegistrations
                                          .FailedRegistrations
           dot1dPortGmrpLastPduOrigin     .OriginatorOfLastPDU
   
      The following IEEE 802.1D management objects have not been
      included in the Bridge MIB for the indicated reasons.
   
     IEEE 802.1D Object                Disposition
   
     Bridge.StateValue                 not considered useful
     Bridge.ApplicantAdministrativeControl
                                       not provided per-attribute
                                       (e.g. per-VLAN, per-Group).
                                       Only per-{device,port,application}
                                       control is provided in this MIB.
   
   
   3.1.2.  The dot1dExtBase Group
   
   This group contains the objects which are applicable to all bridges
   implementing the traffic class and multicast filtering features of
   802.1D.  It includes per-device configuration of GARP and GMRP
   protocols.  This group will be implemented by all devices which
   implement the extensions defined in 802.1D-1998.
   
   
   3.1.3.  The dot1dPriority Group
   
   This group contains the objects for configuring and reporting status
   of priority-based queuing mechanisms in a bridge.  This includes per-
   port user_priority treatment, mapping of user_priority in frames into
   internal traffic classes and outbound user_priority and
   access_priority.
   
   
   3.1.4.  The dot1dGarp Group
   
   This group contains the objects for configuring and reporting on
   operation of the Generic Attribute Registration Protocol (GARP).
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 6]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   3.1.5.  The dot1dGmrp Group
   
   This group contains the objects for configuring and reporting on
   operation of the GARP Multicast Registration Protocol (GMRP).
   
   
   3.1.6.  The dot1dHCPort Group
   
   This group contains the objects for reporting port bridging
   statistics for high-capacity network interfaces.
   
   
   
   
   3.2.  Structure of Virtual Bridge MIB module
   
   Objects in this MIB are arranged into groups.  Each group is
   organized as a set of related objects.  The overall structure and
   assignment of objects to their groups is shown below.  Some of the
   original objects from RFC1493 need to be indexed differently when
   extended in a VLAN environment so some objects in that module
   effectively duplicate new objects defined here: this is necessary for
   backwards compatibility.
   
   
   3.2.1.  Relationship to IEEE 802.1Q Manageable Objects
   
   This section contains a cross-reference to the objects defined in
   [12]. It also details those objects that are not considered necessary
   in this MIB module.
   
   Note: unlike IEEE 802.1D, [12] chose not to define a new set of
   managed object names so those following are referenced from the
   descriptions of management operations with section numbering from
   clause 12 in that document.
   
     Virtual Bridge MIB object           802.1Q object
   
     dot1qBase
       dot1qVlanVersionNumber           12.10.1.1 read bridge vlan config
       dot1qMaxVlanId                   12.10.1.1 read bridge vlan config
       dot1qMaxSupportedVlans           12.10.1.1 read bridge vlan config
       dot1qCanOverridePvidTagging      12.10.1.1 read bridge vlan config
       dot1qNumVlans
       dot1qResetToDefaults             12.10.1.5 reset vlan bridge
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 7]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       dot1dGvrpAdminStatus             12.9.2.1/2 read/set garp
                                                  applicant controls
     dot1qTp
       dot1qTpFdbClear                  12.4.1.4 reset bridge
       dot1qFdbTable
         dot1qFdbId
         dot1qFdbClear                  12.4.1.4 reset bridge
       dot1qTpFdbTable
         dot1qTpFdbAddress
         dot1qTpFdbPort
         dot1qTpFdbStatus
       dot1qTpGroupTable                12.7.7.1 read filtering entry
         dot1qTpGroupAddress
         dot1qTpGroupAllowedToGoTo
         dot1qTpGroupGmrp
         dot1qTpGroupIgmp
       dot1qServiceReqTable             12.7.7.1 read filtering entry
         dot1qServiceRequirement
         dot1qServiceReqPorts
         dot1qServiceReqStaticPorts
     dot1qStatic
       dot1qStaticTable                 12.7.7.1 create/delete/read
                                                  filtering entry
                                        12.7.6.1 read permanent database
         dot1qStaticAddress
         dot1qStaticReceivePort
         dot1qStaticAllowedToGoTo
         dot1qStaticStatus
     dot1qVlan
       dot1qVlanTable                   12.10.2.1 read vlan configuration
                                        12.10.3.5 read VID to FID
                                                  allocations
                                        12.10.3.6 read FID allocation
                                                  for VID
                                        12.10.3.7 read VIDs allocated to
                                                  FID
         dot1qVlanIfIndex
         dot1qVlanId
         dot1qVlanFdbId
         dot1qVlanOperEgressPorts
         dot1qVlanOperUntaggedPorts
         dot1qVlanBridgeUpTime          12.4.1.2.3 read bridge
         dot1qVlanStatus
       dot1qVlanStaticTable             12.7.7.1/2/3 create/delete/read
                                                  filtering entry
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 8]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
                                        12.7.6.1 read permanent database
                                        12.10.2.2 create vlan config
                                        12.10.2.3 delete vlan config
         dot1qVlanStaticVlanId
         dot1qVlanStaticName            12.4.1.3 set bridge name
         dot1qVlanFixedPorts
         dot1qVlanForbiddenPorts
         dot1qVlanAdminUntaggedPorts
         dot1qVlanStaticRowStatus
       dot1qPortVlanConfigTable         12.10.1.1 read bridge vlan
                                                  configuration
         dot1qPvid                      12.10.1.2 configure PVID values
         dot1qPortAcceptableFrameTypes  12.10.1.3 configure acceptable
                                                  frame types parameter
         dot1qPortIngressFiltering      12.10.1.4 configure ingress
                                                  filtering parameters
         dot1qPortGvrpAdminStatus       12.9.2.2 set garp applicant
                                                  controls
         dot1qPortGvrpOperStatus        12.9.2.1 read garp applicant
                                                  controls
         dot1qPortGvrpFailedRegistrations
         dot1qPortGvrpLastPduOrigin
       dot1qPortVlanStatisticsTable     12.6.1.1 read forwarding port
                                                  counters
         dot1qFramesReceived
         dot1qOctetsReceived (optional)
         dot1qForwardOutbound
         dot1qDiscardInbound
         dot1qDiscardNoBuffers
         dot1qDiscardTransitDelayExceeded
         dot1qDiscardError
         dot1qDiscardOnIngressFiltering (optional)
       dot1qPortVlanHCStatisticsTable   12.6.1.1 read forwarding port
                                                  counters
         dot1qHCFramesReceived
         dot1qHCOctetsReceived (optional)
         dot1qHCForwardOutbound
         dot1qHCDiscardInbound
         dot1qHCDiscardNoBuffers
         dot1qHCDiscardTransitDelayExceeded
         dot1qHCDiscardError
         dot1qHCDiscardOnIngressFiltering (optional)
       dot1qLearningConstraintsTable    12.10.3.1/3/4 read/set/delete
                                                vlan learning constraints
                                        12.10.3.2 read vlan learning
   
   
   
   
   
   Bell, et al.            Expires October 1998         [Page 9]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
                                                constraints for VID
         dot1qConstraintVlan
         dot1qConstraintSet
         dot1qConstraintType
         dot1qConstraintStatus
       dot1qConstraintSetDefault
       dot1qConstraintTypeDefault
   
      The following IEEE 802.1Q management objects have not been
      included in the Bridge MIB for the indicated reasons.
   
      IEEE 802.1Q Object                  Disposition
   
      reset bridge (12.4.1.4)             use dot1qTpFdbClear or
                                          dot1qFdbClear to clear FDB.
   
      read forwarding port counters (12.6.1.1)
        discard on error details          not considered useful
   
      read permanent database (12.7.6.1)
        permanent database size           [Issue 21]
        number of static filtering entries
                                          count rows in dot1qStaticTable
                                          [Issue 9].
        number of static VLAN             count rows in
        registration entries              dot1qVlanStaticTable [Issue 9].
   
      read filtering entry range          use GetNext operation.
         (12.7.7.4)
   
      read filtering database (12.7.1.1)
        filtering database size           [Issue 20]
   
      read garp state (12.9.3.1)          not considered useful
   
      notify vlan registration failure    not considered useful
        (12.10.1.6)
   
      notify learning constraint violation
        (12.10.3.10)                      not considered useful
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 10]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   3.2.2.  The dot1qBase Group
   
   This mandatory group contains the objects which are applicable to all
   bridges implementing 802.1Q virtual LANs.
   
   
   3.2.3.  The dot1qTp Group
   
   This group contains objects that control the operation and report the
   status of transparent bridging.  This includes management of the
   dynamic Filtering Databases for both unicast and multicast
   forwarding.  This group will be implemented by all bridges that
   perform destination-address filtering.
   
   
   3.2.4.  The dot1qStatic Group
   
   This group contains objects that control static configuration
   information for transparent bridging.  This includes management of
   the static entries in the Filtering Databases for both unicast and
   multicast forwarding.
   
   
   3.2.5.  The dot1qVlan Group
   
   This group contains objects that control configuration and report
   status of the Virtual LANs known to a bridge.  This includes
   management of the statically configured VLANs as well as reporting
   VLANs discovered by other means e.g. GVRP.  It also controls
   configuration and reports status of per-port objects relating to
   VLANs and reports traffic statistics.  It also provides for
   management of the VLAN Learning Constraints.
   
   
   
   
   3.3.  Textual Conventions
   
   The datatypes MacAddress, BridgeId, Timeout, EnabledStatus, PortList,
   VlanIfIndex and VlanId are used as textual conventions in this
   document.  These textual conventions have NO effect on either the
   syntax nor the semantics of any managed object.  Objects defined
   using these conventions are always encoded by means of the rules that
   define their primitive type.  Hence, no changes to the SMI or the
   SNMP are necessary to accommodate these textual conventions which are
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 11]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   adopted merely for the convenience of readers.
   
   
   
   
   3.4.  Relationship to Other MIBs
   
   As described above, some IEEE 802.1D management objects have not been
   included in this MIB because they overlap with objects in other MIBs
   applicable to a bridge implementing this MIB.  In particular, it is
   assumed that a bridge implementing this MIB will also implement (at
   least) the 'system' group defined in MIB-II [6], the 'interfaces'
   group defined [14] and the old Bridge MIB [13].
   
   
   3.4.1.  Relationship to the 'system' group
   
   In MIB-II, the 'system' group is defined as being mandatory for all
   systems such that each managed entity contains one instance of each
   object in the 'system' group.  Thus, those objects apply to the
   entity as a whole irrespective of whether the entity's sole
   functionality is bridging, or whether bridging is only a subset of
   the entity's functionality.
   
   
   3.4.2.  Relation to Interfaces MIB
   
   RFC 1573, the Interface MIB Evolution [14], requires that any MIB
   which is an adjunct of the Interface MIB, clarify specific areas
   within the Interface MIB.  These areas were intentionally left vague
   in [14] to avoid over constraining the MIB, thereby precluding
   management of certain media-types.
   
   Section 3.3 of [14] enumerates several areas which a media- specific
   MIB must clarify.  Each of these areas is addressed in a following
   subsection.  The implementor is referred to [14] in order to
   understand the general intent of these areas.
   
   In [14], the 'interfaces' group is defined as being mandatory for all
   systems and contains information on an entity's interfaces, where
   each interface is thought of as being attached to a `subnetwork'.
   (Note that this term is not to be confused with `subnet' which refers
   to an addressing partitioning scheme used in the Internet suite of
   protocols.) The term 'segment' is used in this memo to refer to such
   a subnetwork, whether it be an Ethernet segment, a 'ring', a WAN
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 12]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   link, or even an X.25 virtual circuit.
   
   Implicit in this Bridge MIB is the notion of ports on a bridge.  Each
   of these ports is associated with one interface of the 'interfaces'
   group (one row in ifTable) and, in most situations, each port is
   associated with a different interface.  However, there are situations
   in which multiple ports are associated with the same interface.  An
   example of such a situation would be several ports each corresponding
   one-to-one with several X.25 virtual circuits but all on the same
   interface.
   
   Each port is uniquely identified by a port number.  A port number has
   no mandatory relationship to an interface number, but in the simple
   case a port number will have the same value as the corresponding
   interface's interface number.  Port numbers are in the range
   (1..dot1dBaseNumPorts).
   
   Some entities perform other functionality as well as bridging through
   the sending and receiving of data on their interfaces.  In such
   situations, only a subset of the data sent/received on an interface
   is within the domain of the entity's bridging functionality.  This
   subset is considered to be delineated according to a set of
   protocols, with some protocols being bridged, and other protocols not
   being bridged.  For example, in an entity which exclusively performed
   bridging, all protocols would be considered as being bridged, whereas
   in an entity which performed IP routing on IP datagrams and only
   bridged other protocols, only the non-IP data would be considered as
   being bridged.  Thus, this Bridge MIB (and in particular, its
   counters) is applicable only to that subset of the data on an
   entity's interfaces which is sent/received for a protocol being
   bridged.  All such data is sent/received via the ports of the bridge.
   
   3.4.2.1.  Layering Model
   
   This memo assumes the interpretation of the Interfaces Group to be in
   accordance with [14] which states that the interfaces table (ifTable)
   contains information on the managed resource's interfaces and that
   each sub-layer below the internetwork layer of a network interface is
   considered an interface.
   
   This memo recommends that, within an entity, each VLAN which is
   instantiated as an entry in dot1qVlanTable by either management
   configuration through dot1qVlanStaticTable or by dynamic means (e.g.
   through GVRP protocol), also be represented by an entry in ifTable.
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 13]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   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
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 14]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
                                  entries.
   
   
   3.4.2.3.  ifStackTable
   
   In addition, [14] defines a table 'ifStackTable' for describing the
   relationship between logical interfaces within an entity.  It is
   anticipated that implementors will use this table to describe the
   binding of e.g. IP interfaces to VLANs and then onto physical ports.
   However, it cannot represent the full capability of the 802.1Q VLAN
   bridging standard since that makes a distinction between VLAN
   bindings on 'ingress' to and 'egress' from a port: these
   relationships may or may not be symmetrical whereas [14] 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.
   
   
   3.4.2.4.  ifRcvAddressTable
   
   This table contains all MAC addresses, unicast, multicast, and
   broadcast, for which an interface will receive packets and forward
   them up to a higher layer entity for local consumption.  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
   accepted for possible forwarding out some other port.  This table is
   explicitly not intended to provide a bridge address filtering
   mechanism.
   
   
   3.4.3.  Relation to Basic Bridge MIB
   
   This section defines how objects in the basic bridge MIB module
   should be represented for devices which implement the extensions:
   some of the old objects are less useful in such devices but must
   still be implemented for reasons of backwards comaptibility. Note
   that formal conformance statements for that MIB module do not exist
   since it is defined in SMIv1.
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 15]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   3.4.3.1.  The dot1dBase Group
   
   This mandatory group contains the objects which are applicable to all
   types of bridges.  Interpretation of this group is unchanged.
   
   
   3.4.3.2.  The dot1dStp Group
   
   This group contains the objects that denote the bridge's state with
   respect to the Spanning Tree Protocol.  Interpretation of this group
   is unchanged.
   
   
   3.4.3.3.  The dot1dTp Group
   
   This group contains objects that describe the entity's state with
   respect to transparent bridging.
   
   In a device operating with a single Filtering Database,
   interpretation of this group is unchanged.
   
   In a device supporting multiple Filtering Databases, this group is
   interpreted as follows:
   
   dot1dTpLearnedEntryDiscards
         The sum of the counters for each of the individual Filtering
         Databases.
   
      dot1dTpAgingTime
         This applies to all Filtering Databases.
   
      dot1dTpFdbTable
         Report MAC addresses learned on each port, regardless of which
         Filtering Database they have been learnt in.  If an address has
         been learnt in multiple databases on a single port, report it
         only once.  If an address has been learnt in multiple databases
         on more than one port, report the entry on any one of the valid
         ports.
   
      dot1dTpPortTable
         This table is port-based and is not affected by multiple
         Filtering Databases or multiple VLANs.  The counters should
         include frames received or transmitted for all VLANs. Note that
         equivalent 64-bit port statistics counters are defined in this
         document for high-capacity network interfaces.
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 16]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   3.4.3.4.  The dot1dStatic Group
   
   This optional group contains objects that describe the configuration
   of destination-address filtering.
   
   In a device operating with a single Filtering Database,
   interpretation of this group is unchanged.
   
   In a device supporting multiple Filtering Databases, this group is
   interpreted as follows:
   
   dot1dStaticTable
         Entries read from this table include all static entries from
         all of the Filtering Databases.  Entries for the same MAC
         address and receive port in more than one Filtering Database
         must appear only once since these are the indices of this
         table.  This table should be implemented as read-only in
         devices that support multiple Forwarding Databases - instead,
         write access should be provided through dot1qStaticTable, as
         defined in this document.
   
   
   
   
   
   4.  Extensions to RFC 1493
   
   In addition to the objects in RFC1493, this document contains:
   
   (1)  References point to sections of IEEE 802.1D-1998.
   
   (2)  Added support for multiple traffic classes and dynamic multicast
        filtering as per IEEE 802.1D-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
        counters.
   
   
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 17]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   5.  Change Log and Editorial Stuff
   
   5.1.  Changes since draft-bell-bridgemib-00.txt
   
   
   [To Do (2)]
        SMIv2 conversion has been done.
   
   [To Do (3)]
        Conformance Groups and clauses have been defined.
   
   [To Do (4)]
        Done.  See also Issue (1).
   
   [To Do (5)]
        Section 3.4.3 updated with recommendations on interpretation of
        the BRIDGE-MIB from RFC 1493.
   
   [Issue (1)]
        Counter32 versions of the statistics have been provided, with
        appropriate conformance clauses.
   
   [Issue (4)]
        RFC 1493 should be included by reference, as we are not
        modifying it in any way, and it should be progressed to a full
        standard.
   
   [Issue (6)]
        dot1qServiceReqTable has been added to support static and
        dynamic configuration of the "Forward All Groups" and "Forward
        Unregistered Groups" Service Requirements.  This has been added
        to the dot1q MIB, rather than the dot1p MIB, as it is applied to
        each Filtering Database separately.
   
   [Issue (7)]
        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
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 18]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
        required and has been removed.
   
   [Issue (10)]
        No action required.
   
   [Issue (13)]
        No action required.  This version is simpler than 802.1Q.
   
   [Issue (14)]
        No action required.
   
   [Issue (15)]
        Removed the per FDB Aging Time, dot1qFdbAgingTime.
   
   [Issue (16)]
        No action required.  Per-port is sufficient.
   
   [Issue (17)]
        Put dot1qVlanTable before dot1qVlanStaticTable, and moved the
        definition of dot1qVlanIfIndex to dot1qVlanTable.  As
        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)]
        No action required.  Do not think (up|down) are appropriate, as
        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)]
        All write-only items have been changed to read-write, with a
        definition of the value to be returned when they are read.
   
   [Issue (23)]
        Added dot1qConstraintSetDefault and dot1qConstraintTypeDefault,
        allowing a default constraint set to be defined for unspecified
        VLANs.  This allows a shared VLAN set, or independent VLAN set
        constraints to be used as defaults.
   
   [Issue (24)]
        Separate controls to enable and disable GARP have been removed.
        They were an unnecessary complication.  GMRP and GVRP controls
        have been simplified as a result of this.
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 19]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   Other changes
        The items in dot1qPortVlanTable have been re-ordered, to put all
        GVRP items together.
   
        Additional notes have been provided in section 3.1.1, explaining
        why Multicast Group and Service Requirements are defined only in
        the Q-BRIDGE-MIB.
   
        New issues added, closed issues moved to a new section; minor
        editorial changes.
   
   
   5.2.  To Do List
   
   
   (1)  Update boilerplate for appropriate new SNMP framework(s) (v3?)
   
   
   
   5.3.  Open Issues
   
   
   (2)  Indexing of tables by VlanId or by ifIndex? (assume ifIndex)
   
   (3)  Indexing of FDB tables by MacAddress or by something else?
        (assume MacAddress)
   
   (5)  ifStackTable usage
   
   (8)  Learned entry discards counter - per-VLAN? per-device? this
        object is not in 802.1D.
   
   (9)  Do we need per-FID static/dynamic filtering entry counts?
        (12.7.1.1.3)
   
   (11) 802.1D has separate registrar and applicant controls per state
        machine (GVRP and GMRP): do we need per-VLAN and per-Group
        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
        well as Applicant? (dot1qPortGvrpAdminStatus,
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 20]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
        dot1pPortGmrpAdminStatus).
   
   (20) Do we need "read filtering database (12.7.1.1): filtering
        database size"?
   
   (21) Do we need "read forwarding port counters (12.6.1.1): permanent
        database size"?
   
   (22) Do we need a 'next free ifIndex' object?
   
   (23) Do we need default learning constraints? (assume yes)
   
   (24) Can we remove separate GARP controls? (assume yes)
   
   (25) Do we need to split dot1qStaticTable into
        dot1qStaticUnicastTable and dot1qStaticMulticastTable?
   
   (26) Should we have the different Service Requirements  (AllGroups,
        AllUnregisteredGroups) in dot1qServiceReqTable or should we
        leave with dot1qServiceRequirement as a 2nd index?  (assume the
        former for now).
   
   (27) Do we want "capabilities" bitmap objects?
   
   (28) Should ifRcvAddressTable contain entries for e.g. spanning-tree,
        GMRP, GVRP addresses?
   
   
   
   5.4.  Closed Issues in his Draft
   
   
   (1)  Should this MIB offer support for SMIv1-only agents
        (Counter32/64)? ADDED Counter32/Counter64 versions of the per-
        VLAN statistics. ADDED Counter64 versions of the per-port
        statistics from RFC1493. Added appropriate conformance clauses
        for all.
   
   (4)  Include RFC1493 by value or reference? REFERENCE
   
   (6)  Representations of filtering entry for "AllGroups" and
        "AllUnregisteredGroups" DONE
   
   (7)  Should we represent all available FIDs up front or use a "next
        free" object for the manager to create them as needed?  NEITHER
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 21]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
        - see issue 25 above.
   
   (10) Separate config and status info for e.g. dot1dPortGmrpTable,
        dot1qPortVlanTable?  NO CHANGE
   
   (13) Learning constraints table seems clumsy - can we improve this?
        DONE
   
   (14) Do we need to define a "notify vlan registration failure" trap?
        NO
   
   (15) dot1qFdbAgingTime is currently per-FID: 802.1Q has it per-
        device. PER DEVICE
   
   (16) dot1pPortDefaultUserPriority - can this usefully be per-port,
        per-VLAN? PER-PORT
   
   (17) Both dot1qVlanTable and dot1qVlanStaticTable are indexed by
        dot1qVlanIfIndex but that only appears in dot1qVlanStaticTable -
        is this a problem? MOVED TO dot1qVlanTable.
   
   (18) Should we choose same names (up/down) as IF-MIB for values of
        the admin/oper status values, rather than defining our own new
        TC?  Is there an existing TC we can import? NO CHANGE.
   
   (19) Should we have write-only "reset" objects or should these be
        read-write to help MIB browsers (assume write-only)? READ-WRITE.
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 22]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   6.  Definitions for Extended Bridge MIB
   
   
   P-BRIDGE-MIB DEFINITIONS ::= BEGIN
   
   -- -------------------------------------------------------------
   -- IEEE 802.1p MIB
   -- -------------------------------------------------------------
   
   IMPORTS
       MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64
           FROM SNMPv2-SMI
       TruthValue, TEXTUAL-CONVENTION
           FROM SNMPv2-TC
       MODULE-COMPLIANCE, OBJECT-GROUP
           FROM SNMPv2-CONF
       MacAddress, Timeout, dot1dTp, dot1dTpPort,
       dot1dBridge, dot1dBasePortEntry, dot1dBasePort
           FROM BRIDGE-MIB;
   
   pBridgeMIB MODULE-IDENTITY
       LAST-UPDATED "9804242200Z"
       ORGANIZATION "IETF Bridge MIB Working Group"
       CONTACT-INFO
           "       Les Bell
           Postal: 3Com Europe Ltd.
                   3Com Centre, Boundary Way
                   Hemel Hempstead, Herts. HP2 7YU
                   UK
            Phone: +44 1442 438025
            Email: Les_Bell@3Com.com
   
                   Andrew Smith
           Postal: Extreme Networks
                   10460 Bandley Drive
                   Cupertino CA 95014
                   USA
            Phone: +1 (408) 342 0999
            Email: andrew@extremenetworks.com
   
                   Paul Langille
           Postal: Acacia Networks, Inc.
                   650 Suffolk St.
                   Lowell, MA 01854
                   USA
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 23]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
            Phone: +1 (978) 275 0662
            Email: plangille@acacianet.com
   
                   Anil Rijsinghani
           Postal: Cabletron Systems
                   550 King Street, LKG2-2/Y10
                   Littleton, MA 01460-1289
                   USA
            Phone: +1 (508) 486-6786
            Email: anil@lkg.dec.com
   
                   Keith McCloghrie
           Postal: cisco Systems, Inc.
                   170 West Tasman Drive
                   San Jose, CA 95134-1706
                   USA
            Phone: +1 (408) 526 5260
            Email: kzm@cisco.com"
       DESCRIPTION
           "The Bridge MIB Extension module for managing Priority
           and Multicast Filtering, defined by IEEE 802.1D-1998."
       ::= { dot1dBridge 6 }
   
   pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 }
   
   -- -------------------------------------------------------------
   -- Textual Conventions
   -- -------------------------------------------------------------
   
   EnabledStatus ::= TEXTUAL-CONVENTION
       STATUS      current
       DESCRIPTION
           "A simple status value for the object."
       SYNTAX      INTEGER { enabled(1), disabled(2) }
   
   -- -------------------------------------------------------------
   
   -- -------------------------------------------------------------
   -- groups in the P-BRIDGE MIB
   -- -------------------------------------------------------------
   
   dot1dExtBase    OBJECT IDENTIFIER ::= { pBridgeMIBObjects 1 }
   dot1dPriority   OBJECT IDENTIFIER ::= { pBridgeMIBObjects 2 }
   dot1dGarp       OBJECT IDENTIFIER ::= { pBridgeMIBObjects 3 }
   dot1dGmrp       OBJECT IDENTIFIER ::= { pBridgeMIBObjects 4 }
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 24]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   -- -------------------------------------------------------------
   
   -- -------------------------------------------------------------
   -- the dot1dExtBase group
   -- -------------------------------------------------------------
   
   dot1dTrafficClassesEnabled OBJECT-TYPE
       SYNTAX      TruthValue
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The value true(1) indicates that Traffic Classes are
           enabled on this bridge.  When false(2), the bridge
           operates with a single priority level for all traffic."
       DEFVAL      { true }
       ::= { dot1dExtBase 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 }
   
   dot1dGmrpAdminStatus OBJECT-TYPE
       SYNTAX      EnabledStatus
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The administrative status requested by management for
           GMRP.  The value enabled(1) indicates that GMRP should
           be enabled on this device, in all VLANs, on all ports
           for which it has not been specifically disabled.  When
           disabled(2), GMRP is disabled, in all VLANs, on all
           ports."
       DEFVAL      { enabled }
       ::= { dot1dExtBase 3 }
   
   dot1dGarpReset OBJECT-TYPE
       SYNTAX      TruthValue
       MAX-ACCESS  read-write
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 25]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       STATUS      current
       DESCRIPTION
           "When the value true(1) is written to this object, all
           GARP parameters are reset to their power-on values and
           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 }
   
   -- -------------------------------------------------------------
   -- the dot1dPriority group
   -- -------------------------------------------------------------
   
   -- -------------------------------------------------------------
   -- Port Priority Table
   -- -------------------------------------------------------------
   
   dot1dPortPriorityTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1dPortPriorityEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table that contains information about every port that
           is associated with this transparent bridge."
       ::= { dot1dPriority 1 }
   
   dot1dPortPriorityEntry OBJECT-TYPE
       SYNTAX      Dot1dPortPriorityEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A list of Default User Priorities for each port of a
           transparent bridge.  This is indexed by dot1dBasePort."
       AUGMENTS { dot1dBasePortEntry }
       ::= { dot1dPortPriorityTable 1 }
   
   Dot1dPortPriorityEntry ::=
       SEQUENCE {
           dot1dPortDefaultUserPriority
               INTEGER,
           dot1dPortNumTrafficClasses
               INTEGER
       }
   
   dot1dPortDefaultUserPriority OBJECT-TYPE
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 26]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       SYNTAX      INTEGER (0..7)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The default ingress User Priority for this port."
       ::= { dot1dPortPriorityEntry 1 }
   
   dot1dPortNumTrafficClasses OBJECT-TYPE
       SYNTAX      INTEGER (1..8)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The number of egress traffic classes supported on this
           port.  This object may optionally be read-only."
       ::= { dot1dPortPriorityEntry 2 }
   
   -- -------------------------------------------------------------
   -- User Priority Regeneration Table
   -- -------------------------------------------------------------
   
   dot1dUserPriorityRegenTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1dUserPriorityRegenEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A list of Regenerated User Priorities for each received
           User Priority on each port of a bridge.  The Regenerated
           User Priority value is used to index the Traffic Class
           Table for each input port.  The default values for
           Regenerated User Priorities are the same as the User
           Priorities."
       ::= { dot1dPriority 2 }
   
   dot1dUserPriorityRegenEntry OBJECT-TYPE
       SYNTAX      Dot1dUserPriorityRegenEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A mapping of incoming User Priority to a Regenerated
           User Priority."
       INDEX   { dot1dBasePort, dot1dUserPriority }
       ::= { dot1dUserPriorityRegenTable 1 }
   
   Dot1dUserPriorityRegenEntry ::=
       SEQUENCE {
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 27]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           dot1dUserPriority
               INTEGER,
           dot1dRegenUserPriority
               INTEGER
       }
   
   dot1dUserPriority OBJECT-TYPE
       SYNTAX      INTEGER (0..7)
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "The User Priority for a frame received on this port."
       ::= { dot1dUserPriorityRegenEntry 1 }
   
   dot1dRegenUserPriority OBJECT-TYPE
       SYNTAX      INTEGER (0..7)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The Regenerated User Priority the incoming User
           Priority is mapped to for this port."
       ::= { dot1dUserPriorityRegenEntry 2 }
   
   -- -------------------------------------------------------------
   -- Traffic Class Table
   -- -------------------------------------------------------------
   
   dot1dTrafficClassTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1dTrafficClassEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table mapping Regenerated User Priority to Traffic
           Class, for forwarding by the bridge.  Traffic class is a
           number in the range (1..dot1dPortNumTrafficClasses)."
       REFERENCE
           "IEEE 802.1D/D16 Table 7-2"
       ::= { dot1dPriority 3 }
   
   dot1dTrafficClassEntry OBJECT-TYPE
       SYNTAX      Dot1dTrafficClassEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "User Priority to Traffic Class mapping."
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 28]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       INDEX   { dot1dBasePort, dot1dRegenUserPriority }
       ::= { dot1dTrafficClassTable 1 }
   
   Dot1dTrafficClassEntry ::=
       SEQUENCE {
           dot1dTrafficClass
               INTEGER
       }
   
   dot1dTrafficClass OBJECT-TYPE
       SYNTAX      INTEGER (0..7)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The Traffic Class the received frame is mapped to.
           It is optional to support writing to this object."
       ::= { dot1dTrafficClassEntry 1 }
   
   -- -------------------------------------------------------------
   -- Outbound Access Priority Table
   -- -------------------------------------------------------------
   
   dot1dPortOutboundAccessPriorityTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1dPortOutboundAccessPriorityEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table mapping Regenerated User Priority to Outbound
           Access Priority.  This is a fixed mapping for all port
           types, with two options for 802.5 Token Ring."
       REFERENCE
           "IEEE 802.1D/D16 Table 7-3"
       ::= { dot1dPriority 4 }
   
   dot1dPortOutboundAccessPriorityEntry OBJECT-TYPE
       SYNTAX      Dot1dPortOutboundAccessPriorityEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Regenerated User Priority to Outbound Access Priority
           mapping."
       INDEX   { dot1dBasePort, dot1dRegenUserPriority }
       ::= { dot1dPortOutboundAccessPriorityTable 1 }
   
   Dot1dPortOutboundAccessPriorityEntry ::=
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 29]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       SEQUENCE {
           dot1dPortOutboundAccessPriority
               INTEGER
       }
   
   dot1dPortOutboundAccessPriority OBJECT-TYPE
       SYNTAX      INTEGER (0..7)
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The Outbound Access Priority the received frame is
           mapped to."
       ::= { dot1dPortOutboundAccessPriorityEntry 1 }
   
   -- -------------------------------------------------------------
   -- the dot1dGarp group
   -- -------------------------------------------------------------
   
   -- -------------------------------------------------------------
   -- The GARP Port Table
   -- -------------------------------------------------------------
   
   dot1dPortGarpTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1dPortGarpEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table of GARP control information about every bridge
           port.  This is indexed by dot1dBasePort."
       ::= { dot1dGarp 1 }
   
   dot1dPortGarpEntry OBJECT-TYPE
       SYNTAX      Dot1dPortGarpEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "GARP control information for a bridge port."
       AUGMENTS { dot1dBasePortEntry }
       ::= { dot1dPortGarpTable 1 }
   
   Dot1dPortGarpEntry ::=
       SEQUENCE {
           dot1dPortGarpJoinTime
               Timeout,
           dot1dPortGarpLeaveTime
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 30]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
               Timeout,
           dot1dPortGarpLeaveAllTime
               Timeout
       }
   
   dot1dPortGarpJoinTime OBJECT-TYPE
       SYNTAX      Timeout
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The GARP Join time, in centiseconds."
       DEFVAL      { 20 }
       ::= { dot1dPortGarpEntry 1 }
   
   dot1dPortGarpLeaveTime OBJECT-TYPE
       SYNTAX      Timeout
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The GARP Leave time, in centiseconds."
       DEFVAL      { 60 }
       ::= { dot1dPortGarpEntry 2 }
   
   dot1dPortGarpLeaveAllTime OBJECT-TYPE
       SYNTAX      Timeout
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The GARP LeaveAll time, in centiseconds."
       DEFVAL      { 1000 }
       ::= { dot1dPortGarpEntry 3 }
   
   -- -------------------------------------------------------------
   -- The GMRP Port Configuration and Status Table
   -- -------------------------------------------------------------
   
   dot1dPortGmrpTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1dPortGmrpEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table of GMRP control and status information about
           every bridge port.  Augments the dot1dBasePortTable."
       ::= { dot1dGmrp 1 }
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 31]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   dot1dPortGmrpEntry OBJECT-TYPE
       SYNTAX      Dot1dPortGmrpEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "GMRP control and status information for a bridge port."
       AUGMENTS { dot1dBasePortEntry }
       ::= { dot1dPortGmrpTable 1 }
   
   Dot1dPortGmrpEntry ::=
       SEQUENCE {
           dot1dPortGmrpAdminStatus
               EnabledStatus,
           dot1dPortGmrpOperStatus
               EnabledStatus,
           dot1dPortGmrpFailedRegistrations
               Counter32,
           dot1dPortGmrpLastPduOrigin
               MacAddress
       }
   
   dot1dPortGmrpAdminStatus OBJECT-TYPE
       SYNTAX      EnabledStatus
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The administrative status requested by management for
           GMRP, on this port.  The value enabled(1) indicates that
           GMRP should be enabled on this port, in all VLANs, if
           GMRP is also enabled for this device.  When disabled(2),
           GMRP is disabled on this port, in all VLANs."
       DEFVAL      { enabled }
       ::= { 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
       SYNTAX      Counter32
       MAX-ACCESS  read-only
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 32]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       STATUS      current
       DESCRIPTION
           "The total number of failed GMRP registrations, for any
           reason, in all VLANs, on this port."
       ::= { dot1dPortGmrpEntry 3 }
   
   dot1dPortGmrpLastPduOrigin OBJECT-TYPE
       SYNTAX      MacAddress
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The Source MAC Address of the last GMRP message
           received on this port."
       ::= { dot1dPortGmrpEntry 4 }
   
   -- -------------------------------------------------------------
   --  High Capacity Port Table for Transparent Bridges
   -- -------------------------------------------------------------
   
   dot1dTpHCPortTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1dTpHCPortEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table that contains information about every high
           capacity port that is associated with this transparent
           bridge."
       ::= { dot1dTp 5 }
   
   dot1dTpHCPortEntry OBJECT-TYPE
       SYNTAX      Dot1dTpHCPortEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Statistics information for each high capacity port of a
           transparent bridge."
       INDEX   { dot1dTpPort }
       ::= { dot1dTpHCPortTable 1 }
   
   Dot1dTpHCPortEntry ::=
       SEQUENCE {
           dot1dTpHCPortInFrames
               Counter64,
           dot1dTpHCPortOutFrames
               Counter64,
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 33]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           dot1dTpHCPortInDiscards
               Counter64
       }
   
   dot1dTpHCPortInFrames OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames that have been received by this
           port from its segment. Note that a frame received on the
           interface corresponding to this port is only counted by
           this object if and only if it is for a protocol being
           processed by the local bridging function, including
           bridge management frames."
       REFERENCE
           "IEEE 802.1D-1998: Section 14.6.1.1.3"
       ::= { dot1dTpHCPortEntry 1 }
   
   dot1dTpHCPortOutFrames OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames that have been transmitted by this
           port to its segment.  Note that a frame transmitted on
           the interface corresponding to this port is only counted
           by this object if and only if it is for a protocol being
           processed by the local bridging function, including
           bridge management frames."
       REFERENCE
           "IEEE 802.1D-1998: Section 14.6.1.1.3"
       ::= { dot1dTpHCPortEntry 2 }
   
   dot1dTpHCPortInDiscards OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "Count of valid frames received which were discarded
           (i.e., filtered) by the Forwarding Process."
       REFERENCE
           "IEEE 802.1D-1998: Section 14.6.1.1.3"
       ::= { dot1dTpHCPortEntry 3 }
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 34]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   -- -------------------------------------------------------------
   -- IEEE 802.1p MIB - Conformance Information
   -- -------------------------------------------------------------
   
   pBridgeConformance OBJECT IDENTIFIER ::= { pBridgeMIB 2 }
   
   pBridgeGroups OBJECT IDENTIFIER ::= { pBridgeConformance 1 }
   
   pBridgeCompliances OBJECT IDENTIFIER
       ::= { pBridgeConformance 2 }
   
   -- -------------------------------------------------------------
   -- units of conformance
   -- -------------------------------------------------------------
   
   pBridgeExtBaseGroup OBJECT-GROUP
       OBJECTS {
           dot1dTrafficClassesEnabled,
           dot1dGmrpAdminStatus,
           dot1dGarpReset
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing device level control
           and status information for the Priority and Multicast
           Filtering extended bridge services."
       ::= { pBridgeGroups 1 }
   
   pBridgeExtBaseOptionalGroup OBJECT-GROUP
       OBJECTS {
           dot1dTrafficClassesResetToDefaults
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing device level control
           for bridge Priority services."
       ::= { pBridgeGroups 2 }
   
   pBridgePriorityGroup OBJECT-GROUP
       OBJECTS {
           dot1dPortDefaultUserPriority,
           dot1dPortNumTrafficClasses,
           dot1dRegenUserPriority,
           dot1dTrafficClass
       }
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 35]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       STATUS      current
       DESCRIPTION
           "A collection of objects defining the priorities
           applicable to each port and the traffic classes
           within a bridge."
       ::= { pBridgeGroups 3 }
   
   pBridgeAccessPriorityGroup OBJECT-GROUP
       OBJECTS {
           dot1dPortOutboundAccessPriority
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects defining the media dependent
           outbound access level for each priority."
       ::= { pBridgeGroups 4 }
   
   pBridgeConfigurablePriorityGroup OBJECT-GROUP
       OBJECTS {
           dot1dPortDefaultUserPriority,
           dot1dPortNumTrafficClasses,
           dot1dRegenUserPriority,
           dot1dTrafficClass
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects where write-access would
           provide the ability to configure the use of priority
           in a bridge."
       ::= { pBridgeGroups 5 }
   
   pBridgePortGarpGroup OBJECT-GROUP
       OBJECTS {
           dot1dPortGarpJoinTime,
           dot1dPortGarpLeaveTime,
           dot1dPortGarpLeaveAllTime
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing port level control
           and status information for GARP operation."
       ::= { pBridgeGroups 6 }
   
   pBridgePortGmrpGroup OBJECT-GROUP
       OBJECTS {
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 36]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           dot1dPortGmrpAdminStatus,
           dot1dPortGmrpOperStatus,
           dot1dPortGmrpFailedRegistrations,
           dot1dPortGmrpLastPduOrigin
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing port level control
           and status information for GMRP operation."
       ::= { pBridgeGroups 7 }
   
   pBridgeHCPortGroup OBJECT-GROUP
       OBJECTS {
           dot1dTpHCPortInFrames,
           dot1dTpHCPortOutFrames,
           dot1dTpHCPortInDiscards
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing 64-bit statistics
            counters for high capacity bridge ports."
       ::= { pBridgeGroups 8 }
   
   -- -------------------------------------------------------------
   -- compliance statements
   -- -------------------------------------------------------------
   
   pBridgeCompliance MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
           "The compliance statement for device support of Priority
           and Multicast Filtering extended bridge services."
   
       MODULE
           MANDATORY-GROUPS { pBridgeExtBaseGroup }
   
           GROUP       pBridgePriorityGroup
           DESCRIPTION
               "This group is mandatory only for devices supporting
               the priority forwarding operations defined by the
               extended bridge services."
   
           GROUP       pBridgeAccessPriorityGroup
           DESCRIPTION
               "This group is optional."
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 37]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           GROUP       pBridgeConfigurablePriorityGroup
           DESCRIPTION
               "Write-access must be provided to all objects in
               this group in order to manage priority in a switch
               as specified by IEEE 802.1D.  However, it is
               optional to support management of priority."
   
           GROUP       pBridgePortGarpGroup
           DESCRIPTION
               "This group is mandatory for devices supporting any
               of the GARP applications: GMRP, defined by the
               extended bridge services of 802.1D; or GVRP, defined
               by 802.1Q (refer to the Q-BRIDGE-MIB for conformance
               statements for GVRP)."
   
           GROUP       pBridgePortGmrpGroup
           DESCRIPTION
               "This group is mandatory for devices supporting the
               GMRP application, defined by the extended bridge
               services."
   
           GROUP       pBridgeHCPortGroup
           DESCRIPTION
               "This group is mandatory if the network interface
               to which this bridge port is attached has the
               value of the corresponding instance of ifSpeed
               greater than 650,000,000 bits/second."
   
           OBJECT dot1dTrafficClassesEnabled
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access is not required."
   
           OBJECT      dot1dPortNumTrafficClasses
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access is not required."
   
          ::= { pBridgeCompliances 1 }
   
   END
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 38]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   7.  Definitions for Virtual Bridge MIB
   
   
   Q-BRIDGE-MIB DEFINITIONS ::= BEGIN
   
   -- -------------------------------------------------------------
   -- IEEE 802.1Q MIB
   -- -------------------------------------------------------------
   
   IMPORTS
       MODULE-IDENTITY, OBJECT-TYPE,
       Counter32, Counter64, TimeTicks
           FROM SNMPv2-SMI
       RowStatus, TruthValue, DisplayString, TEXTUAL-CONVENTION
           FROM SNMPv2-TC
       MODULE-COMPLIANCE, OBJECT-GROUP
           FROM SNMPv2-CONF
       InterfaceIndex
           FROM IF-MIB
       MacAddress, dot1dBridge, dot1dBasePortEntry, dot1dBasePort
           FROM BRIDGE-MIB
       EnabledStatus
           FROM P-BRIDGE-MIB;
   
   qBridgeMIB MODULE-IDENTITY
       LAST-UPDATED "9804242200Z"
       ORGANIZATION "IETF Bridge MIB Working Group"
       CONTACT-INFO
               "       Les Bell
               Postal: 3Com Europe Ltd.
                       3Com Centre, Boundary Way
                       Hemel Hempstead, Herts. HP2 7YU
                       UK
                Phone: +44 1442 438025
                Email: Les_Bell@3Com.com
   
                       Andrew Smith
               Postal: Extreme Networks
                       10460 Bandley Drive
                       Cupertino CA 95014
                       USA
                Phone: +1 (408) 342 0999
                Email: andrew@extremenetworks.com
   
                       Paul Langille
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 39]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
               Postal: Acacia Networks, Inc.
                       650 Suffolk St.
                       Lowell, MA 01854
                       USA
                Phone: +1 (978) 275 0662
                Email: plangille@acacianet.com
   
                       Anil Rijsinghani
               Postal: Cabletron Systems
                       550 King Street, LKG2-2/Y10
                       Littleton, MA 01460-1289
                       USA
                Phone: +1 (508) 486-6786
                Email: anil@lkg.dec.com
   
                       Keith McCloghrie
               Postal: cisco Systems, Inc.
                       170 West Tasman Drive
                       San Jose, CA 95134-1706
                       USA
                Phone: +1 (408) 526 5260
                Email: kzm@cisco.com"
       DESCRIPTION
           "The VLAN Bridge MIB module for managing Virtual Bridged
           Local Area Networks, as defined by IEEE 802.1Q-1998."
       ::= { dot1dBridge 7 }
   
   qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 }
   
   -- -------------------------------------------------------------
   -- Textual Conventions
   -- -------------------------------------------------------------
   
   PortList ::= TEXTUAL-CONVENTION
       STATUS      current
       DESCRIPTION
           "Each octet within this value specifies a set of eight
           ports, with the first octet specifying ports 1 through
           8, the second octet specifying ports 9 through 16, etc.
           Within each octet, the most significant bit represents
           the lowest numbered port, and the least significant bit
           represents the highest numbered port.  Thus, each port
           of the bridge is represented by a single bit within the
           value of this object.  If that bit has a value of '1'
           then that port is included in the set of ports; the port
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 40]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           is not included if its bit has a value of '0'."
       SYNTAX      OCTET STRING
   
   VlanIfIndex ::= TEXTUAL-CONVENTION
       STATUS      current
       DESCRIPTION
           "The value of the instance of the ifIndex object,
           defined by IF-MIB, for the interface corresponding to a
           given VLAN."
       SYNTAX      InterfaceIndex
   
   VlanId ::= TEXTUAL-CONVENTION
       STATUS      current
       DESCRIPTION
           "The 12-bit VLAN ID used in the VLAN Tag header."
       SYNTAX      INTEGER (1..4094)
   
   -- -------------------------------------------------------------
   -- groups in the Q-BRIDGE MIB
   -- -------------------------------------------------------------
   
   dot1qBase       OBJECT IDENTIFIER ::= { qBridgeMIBObjects 1 }
   dot1qTp         OBJECT IDENTIFIER ::= { qBridgeMIBObjects 2 }
   dot1qStatic     OBJECT IDENTIFIER ::= { qBridgeMIBObjects 3 }
   dot1qVlan       OBJECT IDENTIFIER ::= { qBridgeMIBObjects 4 }
   
   -- -------------------------------------------------------------
   
   -- -------------------------------------------------------------
   -- dot1qBase group
   -- -------------------------------------------------------------
   
   dot1qVlanVersionNumber OBJECT-TYPE
       SYNTAX      INTEGER {
                       version1(1)
                   }
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The version number of IEEE 802.1Q that this device
           supports."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.1.1"
       ::= { dot1qBase 1 }
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 41]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   dot1qMaxVlanId OBJECT-TYPE
       SYNTAX      VlanId
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The maximum IEEE 802.1Q VLAN ID that this device
           supports."
       REFERENCE
           "IEEE 802.1Q/D9 9.3.2.3"
       ::= { dot1qBase 2 }
   
   dot1qMaxSupportedVlans OBJECT-TYPE
       SYNTAX      INTEGER (1..4094)
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The maximum number of IEEE 802.1Q VLANs that this
           device supports."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.1.1"
       ::= { dot1qBase 3 }
   
   dot1qNumVlans OBJECT-TYPE
       SYNTAX      INTEGER (1..4094)
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The current number of IEEE 802.1Q VLANs that are
           configured in this device."
       REFERENCE
           "IEEE 802.1Q/D9 12.7.1.1"
       ::= { dot1qBase 4 }
   
   dot1qResetToDefaults 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 }
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 42]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   dot1qGvrpAdminStatus OBJECT-TYPE
       SYNTAX      EnabledStatus
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The administrative status requested by management for
           GVRP.  The value enabled(1) indicates that GVRP should
           be enabled on this device, on all ports for which it has
           not been specifically disabled.  When disabled(2), GVRP
           is disabled, on all ports."
       DEFVAL      { enabled }
       ::= { dot1qBase 6 }
   
   -- -------------------------------------------------------------
   -- 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
   -- -------------------------------------------------------------
   
   dot1qFdbTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qFdbEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table that contains configuration and control
           information for each Filtering Database currently
           operating on this device.  Entries in this table appear
           automatically when VLANs are assigned FDB IDs in the
           dot1qVlanTable."
       ::= { dot1qTp 2 }
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 43]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   dot1qFdbEntry OBJECT-TYPE
       SYNTAX      Dot1qFdbEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Information about a specific Filtering Database."
       INDEX   { dot1qFdbId }
       ::= { dot1qFdbTable 1 }
   
   Dot1qFdbEntry ::=
       SEQUENCE {
           dot1qFdbId
               INTEGER,
           dot1qFdbClear
               TruthValue
       }
   
   dot1qFdbId OBJECT-TYPE
       SYNTAX       INTEGER
       MAX-ACCESS   not-accessible
       STATUS       current
       DESCRIPTION
           "The identity of this Filtering Database."
       ::= { dot1qFdbEntry 1 }
   
   dot1qFdbClear OBJECT-TYPE
       SYNTAX       TruthValue
       MAX-ACCESS   read-write
       STATUS       current
       DESCRIPTION
           "Writing true(1) to this object discards all MAC
           addresses learnt in this Filtering Database.
           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"
       ::= { dot1qFdbEntry 2 }
   
   -- -------------------------------------------------------------
   -- Multiple Forwarding Databases for 802.1Q Transparent devices
   -- This table is an alternative to the dot1dTpFdbTable,
   -- previously defined for 802.1D devices which only support a
   -- single Forwarding Database.
   -- -------------------------------------------------------------
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 44]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   dot1qTpFdbTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qTpFdbEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table that contains information about unicast entries
           for which the device has forwarding and/or filtering
           information.  This information is used by the
           transparent bridging function in determining how to
           propagate a received frame."
       REFERENCE
           "IEEE 802.1Q/D9 12.7.7"
       ::= { dot1qTp 3 }
   
   dot1qTpFdbEntry OBJECT-TYPE
       SYNTAX      Dot1qTpFdbEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Information about a specific unicast MAC address for
           which the device has some forwarding and/or filtering
           information."
       INDEX   { dot1qFdbId, dot1qTpFdbAddress }
       ::= { dot1qTpFdbTable 1 }
   
   Dot1qTpFdbEntry ::=
       SEQUENCE {
           dot1qTpFdbAddress
               MacAddress,
           dot1qTpFdbPort
               INTEGER,
           dot1qTpFdbStatus
               INTEGER
       }
   
   dot1qTpFdbAddress OBJECT-TYPE
       SYNTAX      MacAddress
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A unicast MAC address for which the device has
           forwarding and/or filtering information."
       ::= { dot1qTpFdbEntry 1 }
   
   dot1qTpFdbPort OBJECT-TYPE
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 45]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       SYNTAX      INTEGER (0..65535)
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "Either the value '0', or the port number of the port on
           which a frame having a source address equal to the value
           of the corresponding instance of dot1qTpFdbAddress has
           been seen.  A value of '0' indicates that the port
           number has not been learned but that the device does
           have some forwarding/filtering information about this
           address (e.g. in the dot1qStaticTable).  Implementors
           are encouraged to assign the port value to this object
           whenever it is learned even for addresses for which the
           corresponding value of dot1qTpFdbStatus is not
           learned(3)."
       ::= { dot1qTpFdbEntry 2 }
   
   dot1qTpFdbStatus OBJECT-TYPE
       SYNTAX      INTEGER {
                       other(1),
                       invalid(2),
                       learned(3),
                       self(4),
                       mgmt(5)
                   }
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The status of this entry.  The meanings of the values
           are:
               other(1) - none of the following.  This may include
                   the case where some other MIB object (not the
                   corresponding instance of dot1qTpFdbPort, nor an
                   entry in the dot1qStaticTable) is being used to
                   determine if and how frames addressed to the
                   value of the corresponding instance of
                   dot1qTpFdbAddress are being forwarded.
               invalid(2) - this entry is no longer valid (e.g., it
                   was learned but has since aged out), but has not
                   yet been flushed from the table.
               learned(3) - the value of the corresponding instance
                   of dot1qTpFdbPort was learned and is being used.
               self(4) - the value of the corresponding instance of
                   dot1qTpFdbAddress represents one of the device's
                   addresses.  The corresponding instance of
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 46]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
                   dot1qTpFdbPort indicates which of the device's
                   ports has this address.
               mgmt(5) - the value of the corresponding instance of
                   dot1qTpFdbAddress is also the value of an
                   existing instance of dot1qStaticAddress."
       ::= { dot1qTpFdbEntry 3 }
   
   -- -------------------------------------------------------------
   -- Dynamic Group Registration Table
   -- -------------------------------------------------------------
   
   dot1qTpGroupTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qTpGroupEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing filtering information for each FDB,
           for VLANs configured into the bridge by (local or
           network) management, or learnt dynamically, specifying
           the set of ports to which frames received on a VLAN for
           this FDB and containing a specific Group destination
           address are allowed to be forwarded."
       ::= { dot1qTp 4 }
   
   dot1qTpGroupEntry OBJECT-TYPE
       SYNTAX      Dot1qTpGroupEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Filtering information configured into the bridge by
           management, or learnt dynamically, specifying the set of
           ports to which frames received on a VLAN for this FDB
           and containing a specific Group destination address, are
           allowed to be forwarded.  The subsets of these ports
           learnt dynamically are also given."
       INDEX   { dot1qFdbId, dot1qTpGroupAddress }
       ::= { dot1qTpGroupTable 1 }
   
   Dot1qTpGroupEntry ::=
       SEQUENCE {
           dot1qTpGroupAddress
               MacAddress,
           dot1qTpGroupAllowedToGoTo
               PortList,
           dot1qTpGroupGmrp
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 47]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
               PortList,
           dot1qTpGroupIgmp
               PortList
       }
   
   dot1qTpGroupAddress OBJECT-TYPE
       SYNTAX      MacAddress
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "The destination Group MAC address in a frame to which
           this entry's filtering information applies."
       ::= { dot1qTpGroupEntry 1 }
   
   dot1qTpGroupAllowedToGoTo OBJECT-TYPE
       SYNTAX      PortList
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The complete set of ports, in this Filtering Database,
           to which frames destined for this Group MAC address are
           allowed to be forwarded."
       ::= { dot1qTpGroupEntry 2 }
   
   dot1qTpGroupGmrp OBJECT-TYPE
       SYNTAX      PortList
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The subset of ports in dot1qTpGroupAllowedToGoTo which
           were learnt by GMRP, in this Filtering database."
       ::= { 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
   -- -------------------------------------------------------------
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 48]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   dot1qServiceReqTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qServiceReqEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing forwarding information for each FDB,
           configured in the bridge, specifying the set of ports to
           which each Service Requirement applies, configured
           statically by management, or dynamically by GMRP."
       REFERENCE
           "IEEE 802.1Q/D9 12.7.2, 12.7.7"
       ::= { dot1qTp 5 }
   
   dot1qServiceReqEntry OBJECT-TYPE
       SYNTAX      Dot1qServiceReqEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Forwarding information for a Service Requiremant
           within an FDB, specifying the set of ports to which that
           Service Requirement applies, configured statically by
           management, or dynamically by GMRP."
       INDEX   { dot1qFdbId, dot1qServiceRequirement }
       ::= { dot1qServiceReqTable 1 }
   
   Dot1qServiceReqEntry ::=
       SEQUENCE {
           dot1qServiceRequirement
               INTEGER,
           dot1qServiceReqPorts
               PortList,
           dot1qServiceReqStaticPorts
               PortList
       }
   
   dot1qServiceRequirement OBJECT-TYPE
       SYNTAX      INTEGER {
                       forwardAllGroups(1),
                       forwardUnknownGroups(2)
                   }
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "The Service Requirement to which this entry's
           forwarding information applies.  A port may be included
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 49]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           in the Service Requirements for both forwardAllGroups(1)
           and forwardUnknownGroups(2), in which case
           forwardAllGroups(1) will apply.  The Service Requirement
           meanings are:
               forwardAllGroups(1) - Traffic for all multicast
                   groups will be forwarded to the ports in the
                   list, dot1qServiceReqPorts.
               forwardUnknownGroups(2) - Traffic for multicast
                   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
       SYNTAX      PortList
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The complete set of ports, in this Filtering Database,
           to which frames destined for this Service Requirement
           are allowed to be forwarded.  This includes ports for
           which the Service Requirement has been learnt
           dynamically, by GMRP, or configured statically by
           management."
       ::= { dot1qServiceReqEntry 2 }
   
   dot1qServiceReqStaticPorts OBJECT-TYPE
       SYNTAX      PortList
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The set of ports configured by management, in this
           Filtering Database, to which frames destined for this
           Service Requirement are allowed to be forwarded.  Ports
           entered in this list will also appear in the complete
           set shown by dot1qServiceReqPorts.  This value will be
           restored after the device is reset."
       ::= { dot1qServiceReqEntry 3 }
   
   -- -------------------------------------------------------------
   -- The Static (Destination-Address Filtering) Database
   -- -------------------------------------------------------------
   
   dot1qStaticTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qStaticEntry
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 50]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing filtering information for each
           Filtering Database, configured into the device by (local
           or network) management specifying the set of ports to
           which frames received from specific ports and containing
           specific destination addresses are allowed to be
           forwarded.  The value of zero in this table as the port
           number from which frames with a specific destination
           address are received, is used to specify all ports for
           which there is no specific entry in this table for that
           particular destination address.  Entries are valid for
           unicast and for group/broadcast addresses."
       REFERENCE
           "IEEE 802.1Q/D9 12.7.7"
       ::= { dot1qStatic 1 }
   
   dot1qStaticEntry OBJECT-TYPE
       SYNTAX      Dot1qStaticEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Filtering information configured into the device by
           (local or network) management specifying the set of
           ports to which frames received from a specific port and
           containing a specific destination address are allowed to
           be forwarded."
       INDEX   {
           dot1qFdbId,
           dot1qStaticAddress,
           dot1qStaticReceivePort
       }
       ::= { dot1qStaticTable 1 }
   
   Dot1qStaticEntry ::=
       SEQUENCE {
           dot1qStaticAddress
               MacAddress,
           dot1qStaticReceivePort
               INTEGER,
           dot1qStaticAllowedToGoTo
               PortList,
           dot1qStaticStatus
               INTEGER
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 51]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       }
   
   dot1qStaticAddress 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 can
           take the value of a unicast address, a group address or
           the broadcast address."
       ::= { dot1qStaticEntry 1 }
   
   -- -------------------------------------------------------------
   -- This is not defined in 802.1Q/D9 - see section 12.7.7.
   -- Do we need it?
   -- -------------------------------------------------------------
   
   dot1qStaticReceivePort OBJECT-TYPE
       SYNTAX      INTEGER (0..65535)
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Either the value '0', or the port number of the port
           from which a frame must be received in order for this
           entry's filtering information to apply.  A value of zero
           indicates that this entry applies on all ports of the
           device for which there is no other applicable entry."
       ::= { dot1qStaticEntry 2 }
   
   dot1qStaticAllowedToGoTo 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 MAC address,
           are allowed to be forwarded.  The default value of this
           object is a string of ones of appropriate length."
       ::= { dot1qStaticEntry 3 }
   
   dot1qStaticStatus OBJECT-TYPE
       SYNTAX      INTEGER {
                       other(1),
                       invalid(2),
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 52]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
                       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 }
       ::= { dot1qStaticEntry 4 }
   
   -- -------------------------------------------------------------
   -- The Current VLAN Database
   -- -------------------------------------------------------------
   
   dot1qVlanTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qVlanEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing current configuration information
           for each VLAN currently configured into the device by
           (local or network) management, or dynamically created
           as a result of GVRP requests received."
       ::= { dot1qVlan 1 }
   
   dot1qVlanEntry OBJECT-TYPE
       SYNTAX      Dot1qVlanEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Information for a VLAN configured into the device by
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 53]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           (local or network) management, or dynamically created
           as a result of GVRP requests received."
       INDEX   { dot1qVlanIfIndex }
       ::= { dot1qVlanTable 1 }
   
   Dot1qVlanEntry ::=
       SEQUENCE {
           dot1qVlanIfIndex
               VlanIfIndex,
           dot1qVlanId
               INTEGER,
           dot1qVlanFdbId
               INTEGER,
           dot1qVlanOperEgressPorts
               PortList,
           dot1qVlanOperUntaggedPorts
               PortList,
           dot1qVlanBridgeUpTime
               TimeTicks,
           dot1qVlanStatus
               INTEGER
       }
   
   dot1qVlanIfIndex OBJECT-TYPE
       SYNTAX      VlanIfIndex
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "The ifIndex value refering to the ifTable entry for
           the virtual interface presented by this VLAN."
       ::= { dot1qVlanEntry 1 }
   
   dot1qVlanId OBJECT-TYPE
       SYNTAX      INTEGER (0|1..4094)
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The VLAN ID used in the VLAN Tag header for this VLAN.
           A value of 0 indicates none has been assigned."
       ::= { dot1qVlanEntry 2 }
   
   dot1qVlanFdbId OBJECT-TYPE
       SYNTAX      INTEGER (1..4095)
       MAX-ACCESS  read-only
       STATUS      current
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 54]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       DESCRIPTION
           "The Filtering Database used by this VLAN.  This is one
           of the dot1qFdbId values in the dot1qFdbTable.  This
           value is allocated automatically by the device whenever
           the VLAN is created: either dynamically by GVRP, or by
           management, in dot1qVlanStaticTable.  Allocation of this
           value follows the learning constraints defined for this
           VLAN in dot1qLearningConstraintsTable."
       ::= { dot1qVlanEntry 3 }
   
   dot1qVlanOperEgressPorts OBJECT-TYPE
       SYNTAX      PortList
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The set of ports which are transmitting traffic for
           this VLAN as either tagged or untagged frames."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.2.1"
       ::= { dot1qVlanEntry 4 }
   
   dot1qVlanOperUntaggedPorts OBJECT-TYPE
       SYNTAX      PortList
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The set of ports which are transmitting traffic for
           this VLAN as untagged frames."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.2.1"
       ::= { 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
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 55]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       SYNTAX      INTEGER {
                       other(1),
                       permanent(2),
                       dynamicGvrp(3)
                   }
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "This object indicates the status of this entry.
               other(1) - this entry is currently in use but
                   the conditions under which it will remain
                   so differ from the following values.
               permanent(2) - this entry, corresponding to an
                   entry in dot1qVlanStaticTable, is currently
                   in use and will remain so after the next
                   reset of the device.
               dynamicGvrp(3) - this entry is currently in use
                   and will remain so until removed by GVRP."
       ::= { dot1qVlanEntry 7 }
   
   -- -------------------------------------------------------------
   -- The Static VLAN Database
   -- -------------------------------------------------------------
   
   dot1qVlanStaticTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qVlanStaticEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing static configuration information for
           each VLAN configured into the device by (local or
           network) management.  All entries are permanent and will
           be restored after the device is reset."
       ::= { dot1qVlan 2 }
   
   dot1qVlanStaticEntry OBJECT-TYPE
       SYNTAX      Dot1qVlanStaticEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Static information for a VLAN configured into the
           device by (local or network) management."
       INDEX   { dot1qVlanIfIndex }
       ::= { dot1qVlanStaticTable 1 }
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 56]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   Dot1qVlanStaticEntry ::=
       SEQUENCE {
           dot1qVlanStaticVlanId
               INTEGER,
           dot1qVlanStaticName
               DisplayString,
           dot1qVlanFixedPorts
               PortList,
           dot1qVlanForbiddenPorts
               PortList,
           dot1qVlanAdminUntaggedPorts
               PortList,
           dot1qVlanStaticRowStatus
               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
       SYNTAX      DisplayString (SIZE (0..32))
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "A unique, administratively assigned string, which may
           be used to identify the VLAN.  This is reflected back
           (as read-only) in the ifDescr field for the ifTable
           entry for this VLAN referenced by dot1qVlanIfIndex."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.2.1"
       ::= { dot1qVlanStaticEntry 2 }
   
   dot1qVlanFixedPorts OBJECT-TYPE
       SYNTAX      PortList
       MAX-ACCESS  read-write
       STATUS      current
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 57]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       DESCRIPTION
           "The set of ports which are permanently assigned to
           this VLAN by management.  The default value of this
           object is a string of zeros of appropriate length."
       REFERENCE
           "IEEE 802.1Q/D9 12.7.7.3"
       ::= { dot1qVlanStaticEntry 3 }
   
   dot1qVlanForbiddenPorts OBJECT-TYPE
       SYNTAX      PortList
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The set of ports which are prohibited from joining
           this VLAN by management.  The default value of this
           object is a string of zeros of appropriate length."
       REFERENCE
           "IEEE 802.1Q/D9: Section 12.7.7.3"
       ::= { dot1qVlanStaticEntry 4 }
   
   dot1qVlanAdminUntaggedPorts OBJECT-TYPE
       SYNTAX      PortList
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The set of ports which should transmit traffic for this
           VLAN as untagged frames.  The default value of this
           object is a string of appropriate length, with each bit
           set to one for those ports which define this VLAN as
           their PVID, otherwise the bit is set to zero."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.2.1"
       ::= { dot1qVlanStaticEntry 5 }
   
   dot1qVlanStaticRowStatus OBJECT-TYPE
       SYNTAX      RowStatus
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "This object indicates the status of this entry."
       ::= { dot1qVlanStaticEntry 6 }
   
   -- -------------------------------------------------------------
   -- The VLAN Port Configuration Table
   -- -------------------------------------------------------------
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 58]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   dot1qPortVlanTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qPortVlanEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing per port control and status
           information for VLAN configuration in the device."
       ::= { dot1qVlan 3 }
   
   dot1qPortVlanEntry OBJECT-TYPE
       SYNTAX      Dot1qPortVlanEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Information controlling VLAN configuration for a port
           on the device.  This is indexed by dot1dBasePort."
       AUGMENTS { dot1dBasePortEntry }
       ::= { dot1qPortVlanTable 1 }
   
   Dot1qPortVlanEntry ::=
       SEQUENCE {
           dot1qPvid
               VlanId,
           dot1qPortAcceptableFrameTypes
               INTEGER,
           dot1qPortIngressFiltering
               TruthValue,
           dot1qPortGvrpAdminStatus
               EnabledStatus,
           dot1qPortGvrpOperStatus
               EnabledStatus,
           dot1qPortGvrpFailedRegistrations
               Counter32,
           dot1qPortGvrpLastPduOrigin
               MacAddress
       }
   
   dot1qPvid OBJECT-TYPE
       SYNTAX      VlanId
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The PVID, the VLAN ID assigned to untagged frames or
           Prority-Tagged frames received on this port."
       REFERENCE
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 59]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           "IEEE 802.1Q/D9 12.10.1.1"
       DEFVAL      { 1 }
       ::= { dot1qPortVlanEntry 1 }
   
   dot1qPortAcceptableFrameTypes OBJECT-TYPE
       SYNTAX      INTEGER {
                       admitAll(1),
                       admitOnlyVlanTagged(2)
                   }
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "When this is admitOnlyVlanTagged(2) the device will
           discard untagged frames or Prority-Tagged frames
           received on this port.  When admitAll(1), untagged
           frames or Prority-Tagged frames received on this port
           will be accepted and assigned to the PVID for this port.
   
           This control does not affect incoming BPDU frames,
           such as GARP and STP."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.1.3"
       DEFVAL      { admitAll }
       ::= { dot1qPortVlanEntry 2 }
   
   dot1qPortIngressFiltering OBJECT-TYPE
       SYNTAX      TruthValue
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "When this is true(1) the device will discard incoming
           frames for VLANs not in the port egress filters.  When
           false(2), the port will accept all incoming frames.
   
           This control does not affect incoming BPDU frames, such
           as GARP and STP."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.1.4"
       DEFVAL      { false }
       ::= { dot1qPortVlanEntry 3 }
   
   dot1qPortGvrpAdminStatus OBJECT-TYPE
       SYNTAX      EnabledStatus
       MAX-ACCESS  read-write
       STATUS      current
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 60]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       DESCRIPTION
           "The administrative status requested by management for
           GVRP, on this port.  The value enabled(1) indicates that
           GVRP should be enabled on this port, if GVRP is also
           enabled for this device.  When disabled(2), GVRP is
           disabled on this port."
       DEFVAL      { enabled }
       ::= { 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
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The total number of failed GVRP registrations, for any
           reason, on this port."
       ::= { dot1qPortVlanEntry 6 }
   
   dot1qPortGvrpLastPduOrigin OBJECT-TYPE
       SYNTAX      MacAddress
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The Source MAC Address of the last GVRP message
           received on this port."
       ::= { dot1qPortVlanEntry 7 }
   
   -- -------------------------------------------------------------
   -- Per port VLAN Statistics Table
   -- -------------------------------------------------------------
   
   dot1qPortVlanStatisticsTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qPortVlanStatisticsEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing per port, per VLAN statistics for
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 61]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           traffic received."
       REFERENCE
           "IEEE 802.1Q/D9: Section 12.6.1"
       ::= { dot1qVlan 4 }
   
   dot1qPortVlanStatisticsEntry OBJECT-TYPE
       SYNTAX      Dot1qPortVlanStatisticsEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Traffic statistics for a VLAN on an interface."
       INDEX   { dot1dBasePort, dot1qVlanIfIndex }
       ::= { dot1qPortVlanStatisticsTable 1 }
   
   Dot1qPortVlanStatisticsEntry ::=
       SEQUENCE {
           dot1qFramesReceived
               Counter32,
           dot1qOctetsReceived
               Counter32,
           dot1qForwardOutbound
               Counter32,
           dot1qDiscardInbound
               Counter32,
           dot1qDiscardNoBuffers
               Counter32,
           dot1qDiscardTransitDelayExceeded
               Counter32,
           dot1qDiscardError
               Counter32,
           dot1qDiscardOnIngressFiltering
               Counter32
       }
   
   dot1qFramesReceived OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames received on this port and VLAN."
       ::= { dot1qPortVlanStatisticsEntry 1 }
   
   dot1qOctetsReceived OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 62]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       STATUS      current
       DESCRIPTION
           "The number of octets received on this port and VLAN."
       ::= { dot1qPortVlanStatisticsEntry 2 }
   
   dot1qForwardOutbound OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames forwarded from this port and
           VLAN."
       ::= { dot1qPortVlanStatisticsEntry 3 }
   
   dot1qDiscardInbound OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of inbound frames discarded on this port and
           VLAN."
       ::= { dot1qPortVlanStatisticsEntry 4 }
   
   dot1qDiscardNoBuffers OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames discarded due to lack of buffers
           for this port and VLAN."
       ::= { dot1qPortVlanStatisticsEntry 5 }
   
   dot1qDiscardTransitDelayExceeded OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames discarded by this port and VLAN
           due to excessive transit delay through the device."
       ::= { dot1qPortVlanStatisticsEntry 6 }
   
   dot1qDiscardError OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 63]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       DESCRIPTION
           "The number of frames discarded by this port and VLAN
           due to other errors."
       ::= { dot1qPortVlanStatisticsEntry 7 }
   
   dot1qDiscardOnIngressFiltering OBJECT-TYPE
       SYNTAX      Counter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames discarded by this port and VLAN
           due to ingress filtering."
       ::= { dot1qPortVlanStatisticsEntry 8 }
   
   dot1qPortVlanHCStatisticsTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qPortVlanHCStatisticsEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing per port, per VLAN statistics for
           traffic received on high capacity interfaces."
       REFERENCE
           "IEEE 802.1Q/D9: Section 12.6.1"
       ::= { dot1qVlan 5 }
   
   dot1qPortVlanHCStatisticsEntry OBJECT-TYPE
       SYNTAX      Dot1qPortVlanHCStatisticsEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Traffic statistics for a VLAN on a high capacity
           interface."
       INDEX   { dot1dBasePort, dot1qVlanIfIndex }
       ::= { dot1qPortVlanHCStatisticsTable 1 }
   
   Dot1qPortVlanHCStatisticsEntry ::=
       SEQUENCE {
           dot1qHCFramesReceived
               Counter64,
           dot1qHCOctetsReceived
               Counter64,
           dot1qHCForwardOutbound
               Counter64,
           dot1qHCDiscardInbound
               Counter64,
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 64]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           dot1qHCDiscardNoBuffers
               Counter64,
           dot1qHCDiscardTransitDelayExceeded
               Counter64,
           dot1qHCDiscardError
               Counter64,
           dot1qHCDiscardOnIngressFiltering
               Counter64
       }
   
   dot1qHCFramesReceived OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames received on this port and VLAN."
       ::= { dot1qPortVlanHCStatisticsEntry 1 }
   
   dot1qHCOctetsReceived OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of octets received on this port and VLAN."
       ::= { dot1qPortVlanHCStatisticsEntry 2 }
   
   dot1qHCForwardOutbound OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames forwarded from this port and
           VLAN."
       ::= { dot1qPortVlanHCStatisticsEntry 3 }
   
   dot1qHCDiscardInbound OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of inbound frames discarded on this port
           and VLAN."
       ::= { dot1qPortVlanHCStatisticsEntry 4 }
   
   dot1qHCDiscardNoBuffers OBJECT-TYPE
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 65]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames discarded due to lack of buffers
           for this port and VLAN."
       ::= { dot1qPortVlanHCStatisticsEntry 5 }
   
   dot1qHCDiscardTransitDelayExceeded OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames discarded by this port and VLAN
           due to excessive transit delay through the device."
       ::= { dot1qPortVlanHCStatisticsEntry 6 }
   
   dot1qHCDiscardError OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames discarded by this port and VLAN
           due to other errors."
       ::= { dot1qPortVlanHCStatisticsEntry 7 }
   
   dot1qHCDiscardOnIngressFiltering OBJECT-TYPE
       SYNTAX      Counter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The number of frames discarded by this port and VLAN
           due to ingress filtering."
       ::= { dot1qPortVlanHCStatisticsEntry 8 }
   
   -- -------------------------------------------------------------
   -- The VLAN Learning Constraints Table
   -- -------------------------------------------------------------
   -- Editor: This table is defined in a slightly different sense
   -- to that in IEEE 802.1Q, combining the two different types of
   -- constraint for Independent and Shared into a single table.
   -- -------------------------------------------------------------
   
   dot1qLearningConstraintsTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF Dot1qLearningConstraintsEntry
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 66]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table containing learning constraints for sets of
           Shared and Independendent VLANs."
       REFERENCE
           "IEEE 802.1Q/D9 12.10.3.1"
       ::= { dot1qVlan 6 }
   
   dot1qLearningConstraintsEntry OBJECT-TYPE
       SYNTAX      Dot1qLearningConstraintsEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A learning constraint defined for a VLAN."
       INDEX   { dot1qConstraintVlan, dot1qConstraintSet }
       ::= { dot1qLearningConstraintsTable 1 }
   
   Dot1qLearningConstraintsEntry ::=
       SEQUENCE {
           dot1qConstraintVlan
               VlanIfIndex,
           dot1qConstraintSet
               INTEGER,
           dot1qConstraintType
               INTEGER,
           dot1qConstraintStatus
               RowStatus
       }
   
   dot1qConstraintVlan OBJECT-TYPE
       SYNTAX      VlanIfIndex
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "The ifIndex value refering to the ifTable entry for the
           VLAN constrained by this entry."
       ::= { dot1qLearningConstraintsEntry 1 }
   
   dot1qConstraintSet OBJECT-TYPE
       SYNTAX      INTEGER (0..65535)
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "The identity of the constraint set to which
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 67]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           dot1qConstraintVlan belongs.  These values may be chosen
           by the management station."
       ::= { dot1qLearningConstraintsEntry 2 }
   
   dot1qConstraintType OBJECT-TYPE
       SYNTAX      INTEGER {
                       independent(1),
                       shared(2)
                   }
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The type of constraint this entry defines.
               independent(1) - the VLAN, dot1qConstraintVlan,
                   uses an independent filtering database
                   from all other VLANs in the same set, defined by
                   dot1qConstraintSet.
               shared(2) - the VLAN, dot1qConstraintVlan shares the
                   same filtering database as all other VLANs in
                   the same set, defined by dot1qConstraintSet."
       ::= { dot1qLearningConstraintsEntry 3 }
   
   dot1qConstraintStatus OBJECT-TYPE
       SYNTAX      RowStatus
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The status of this entry."
       ::= { dot1qLearningConstraintsEntry 4 }
   
   dot1qConstraintSetDefault OBJECT-TYPE
       SYNTAX      INTEGER (0..65535)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The identity of the constraint set to which a VLAN
           belongs, if there is not an explicit entry for that VLAN
           in dot1qLearningConstraintsTable."
       ::= { dot1qVlan 7 }
   
   dot1qConstraintTypeDefault OBJECT-TYPE
       SYNTAX      INTEGER {
                       independent(1),
                       shared(2)
                   }
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 68]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "The type of constraint set to which a VLAN belongs, if
           there is not an explicit entry for that VLAN in
           dot1qLearningConstraintsTable.  The types are as defined
           for dot1qConstraintType."
       ::= { dot1qVlan 8 }
   
   -- -------------------------------------------------------------
   -- IEEE 802.1Q MIB - Conformance Information
   -- -------------------------------------------------------------
   
   qBridgeConformance OBJECT IDENTIFIER ::= { qBridgeMIB 2 }
   
   qBridgeGroups OBJECT IDENTIFIER ::= { qBridgeConformance 1 }
   
   qBridgeCompliances OBJECT IDENTIFIER
       ::= { qBridgeConformance 2 }
   
   -- -------------------------------------------------------------
   -- units of conformance
   -- -------------------------------------------------------------
   
   qBridgeBaseGroup OBJECT-GROUP
       OBJECTS {
           dot1qVlanVersionNumber,
           dot1qMaxVlanId,
           dot1qMaxSupportedVlans,
           dot1qNumVlans,
           dot1qResetToDefaults,
           dot1qGvrpAdminStatus
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing device level control
           and status information for the Virtual LAN bridge
           services."
       ::= { qBridgeGroups 1 }
   
   qBridgeTpFdbGroup OBJECT-GROUP
       OBJECTS {
           dot1qTpFdbClear
       }
       STATUS      current
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 69]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       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
       OBJECTS {
           dot1qTpFdbPort,
           dot1qTpFdbStatus
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing information about all
           unicast addresses, learnt dynamically or statically
           configured by management, in each Filtering Database."
       ::= { qBridgeGroups 4 }
   
   qBridgeFdbMulticastGroup OBJECT-GROUP
       OBJECTS {
           dot1qTpGroupAllowedToGoTo,
           dot1qTpGroupGmrp,
           dot1qTpGroupIgmp
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing information about all
           multicast addresses, learnt dynamically or statically
           configured by management, in each Filtering Database."
       ::= { qBridgeGroups 5 }
   
   qBridgeServiceRequirementsGroup OBJECT-GROUP
       OBJECTS {
           dot1qServiceReqPorts,
           dot1qServiceReqStaticPorts
       }
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 70]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
       STATUS      current
       DESCRIPTION
           "A collection of objects providing information about
           service requirements, learnt dynamically or statically
           configured by management, in each Filtering Database."
       ::= { qBridgeGroups 6 }
   
   qBridgeFdbStaticGroup OBJECT-GROUP
       OBJECTS {
           dot1qStaticAllowedToGoTo,
           dot1qStaticStatus
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing information about
           unicast and multicast addresses statically configured by
           management, in each Filtering Database."
       ::= { qBridgeGroups 7 }
   
   qBridgeVlanGroup OBJECT-GROUP
       OBJECTS {
           dot1qVlanId,
           dot1qVlanFdbId,
           dot1qVlanOperEgressPorts,
           dot1qVlanOperUntaggedPorts,
           dot1qVlanBridgeUpTime,
           dot1qVlanStatus
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing information about
           all VLANs currently configured on this device."
       ::= { qBridgeGroups 8 }
   
   qBridgeVlanStaticGroup OBJECT-GROUP
       OBJECTS {
           dot1qVlanStaticVlanId,
           dot1qVlanStaticName,
           dot1qVlanFixedPorts,
           dot1qVlanForbiddenPorts,
           dot1qVlanAdminUntaggedPorts,
           dot1qVlanStaticRowStatus
       }
       STATUS      current
       DESCRIPTION
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 71]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           "A collection of objects providing information about
           VLANs statically configured by management."
       ::= { qBridgeGroups 9 }
   
   qBridgePortGroup OBJECT-GROUP
       OBJECTS {
           dot1qPvid,
           dot1qPortAcceptableFrameTypes,
           dot1qPortIngressFiltering,
           dot1qPortGvrpAdminStatus,
           dot1qPortGvrpOperStatus,
           dot1qPortGvrpFailedRegistrations,
           dot1qPortGvrpLastPduOrigin
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing port level VLAN
           control and status information for all ports."
       ::= { qBridgeGroups 10 }
   
   qBridgeVlanStatisticsGroup OBJECT-GROUP
       OBJECTS {
           dot1qOctetsReceived
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing per-port octet
           statistics for all VLANs currently configured on
           this device."
       ::= { qBridgeGroups 11 }
   
   qBridgeVlanPacketStatisticsGroup OBJECT-GROUP
       OBJECTS {
           dot1qFramesReceived,
           dot1qForwardOutbound,
           dot1qDiscardInbound,
           dot1qDiscardNoBuffers,
           dot1qDiscardTransitDelayExceeded,
           dot1qDiscardError,
           dot1qDiscardOnIngressFiltering
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing per-port packet
           statistics for all VLANs currently configured on this
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 72]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           device."
       ::= { qBridgeGroups 12 }
   
   qBridgeVlanHCStatisticsGroup OBJECT-GROUP
       OBJECTS {
           dot1qHCOctetsReceived
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing per-port octet count
           statistics for all VLANs currently configured on this
           device for high capacity interfaces."
       ::= { qBridgeGroups 13 }
   
   qBridgeVlanHCPacketStatisticsGroup OBJECT-GROUP
       OBJECTS {
           dot1qHCFramesReceived,
           dot1qHCForwardOutbound,
           dot1qHCDiscardInbound,
           dot1qHCDiscardNoBuffers,
           dot1qHCDiscardTransitDelayExceeded,
           dot1qHCDiscardError,
           dot1qHCDiscardOnIngressFiltering
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects providing per-port packet
           statistics for all VLANs currently configured on this
           device for high capacity interfaces."
       ::= { qBridgeGroups 14 }
   
   qBridgeLearningConstraintsGroup OBJECT-GROUP
       OBJECTS {
           dot1qConstraintType,
           dot1qConstraintStatus
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects defining the Filtering Database
           constraints all VLANs have with each other."
       ::= { qBridgeGroups 15 }
   
   qBridgeLearningConstraintDefaultGroup OBJECT-GROUP
       OBJECTS {
           dot1qConstraintSetDefault,
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 73]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           dot1qConstraintTypeDefault
       }
       STATUS      current
       DESCRIPTION
           "A collection of objects defining the default Filtering
           Database constraints for VLANs which have no specific
           constraints defined."
       ::= { qBridgeGroups 16 }
   
   -- -------------------------------------------------------------
   -- compliance statements
   -- -------------------------------------------------------------
   
   qBridgeCompliance MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
           "The compliance statement for device support of Virtual
           LAN Bridge services."
   
       MODULE
           MANDATORY-GROUPS {
               qBridgeBaseGroup,
               qBridgeVlanGroup,
               qBridgeVlanStaticGroup,
               qBridgePortGroup
           }
   
           GROUP       qBridgeFdbGroup
           DESCRIPTION
               "This group is optional."
   
           GROUP       qBridgeTpFdbGroup
           DESCRIPTION
               "This group is optional."
   
           GROUP       qBridgeFdbUnicastGroup
           DESCRIPTION
               "This group is mandatory for bridges that implement
               802.1Q transparent bridging."
   
           GROUP       qBridgeFdbMulticastGroup
           DESCRIPTION
               "This group is mandatory for bridges that implement
               802.1Q transparent bridging."
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 74]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           GROUP       qBridgeServiceRequirementsGroup
           DESCRIPTION
               "This group is mandatory for bridges that implement
               extended filtering services."
   
           GROUP       qBridgeFdbStaticGroup
           DESCRIPTION
               "This group is optional."
   
           GROUP       qBridgeVlanStatisticsGroup
           DESCRIPTION
               "This group is optional."
   
           GROUP       qBridgeVlanPacketStatisticsGroup
           DESCRIPTION
               "This group is optional but should be implemented if
               qBridgeVlanStatisticsGroup is implemented."
   
           GROUP       qBridgeVlanHCStatisticsGroup
           DESCRIPTION
               "This group is optional.  It should be implemented
               if qBridgeVlanStatisticsGroup is implemented and if
               the network interface to which this bridge port is
               attached has the value of the corresponding instance
               of ifSpeed greater than 20,000,000 bits/second."
   
           GROUP       qBridgeVlanHCPacketStatisticsGroup
           DESCRIPTION
               "This group is optional.  It should be implemented
               if qBridgeVlanPacketStatisticsGroup is implemented
               and if the network interface to which this bridge
               port is attached has the value of the corresponding
               instance of ifSpeed greater than 650,000,000
               bits/second."
   
           GROUP       qBridgeLearningConstraintsGroup
           DESCRIPTION
               "This group is optional."
   
           GROUP       qBridgeLearningConstraintDefaultGroup
           DESCRIPTION
               "This group is optional."
   
           OBJECT      dot1qPortAcceptableFrameTypes
           MIN-ACCESS  read-only
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 75]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
           DESCRIPTION
               "Write access is not required."
   
           OBJECT      dot1qPortIngressFiltering
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access is not required."
   
           OBJECT      dot1qConstraintSetDefault
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access is not required."
   
           OBJECT      dot1qConstraintTypeDefault
           MIN-ACCESS  read-only
           DESCRIPTION
               "Write access is not required."
   
          ::= { qBridgeCompliances 1 }
   
   END
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 76]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   8.  Acknowledgments
   
   This document expands upon previous work which resulted in RFC1493.
   
   Much of the groundwork for this document was performed by the IEEE
   802.1 working group during the definition of the IEEE 802.1D updates
   [12] and IEEE 802.1Q [13].  Some ideas were also taken from an
   earlier Internet Draft for a VLAN MIB [16] from I. Jeyasubramanian.
   
   The authors wish to thank the members of the Bridge Working Group for
   their many comments and suggestions which improved this effort.
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 77]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   9.  References
   
   [1]  Cerf, V., "IAB Recommendations for the Development of Internet
        Network Management Standards", RFC 1052, NRI, April 1988.
   
   [2]  Cerf, V., "Report of the Second Ad Hoc Network Management Review
        Group", RFC 1109, NRI, August 1989.
   
   [3]  Rose M., and K. McCloghrie, "Structure and Identification of
        Management Information for TCP/IP-based internets", STD 16, RFC
        1155, Performance Systems International, Hughes LAN Systems, May
        1990.
   
   [4]  Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
        Network Management Protocol", STD 15, RFC 1157, SNMP Research,
        Performance Systems International, Performance Systems
        International, MIT Laboratory for Computer Science, May 1990.
   
   [5]  McCloghrie K., and M. Rose, Editors, "Management Information
        Base for Network Management of TCP/IP-based internets", STD 17,
        RFC 1213, Performance Systems International, March 1991.
   
   [6]  Information processing systems - Open Systems Interconnection -
        Specification of Abstract Syntax Notation One (ASN.1),
        International Organization for Standardization, International
        Standard 8824, December 1987.
   
   [7]  Information processing systems - Open Systems Interconnection -
        Specification of Basic Encoding Rules for Abstract Notation One
        (ASN.1), International Organization for Standardization,
        International Standard 8825, December 1987.
   
   [8]  Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
        STD 16, RFC 1212, Performance Systems International, Hughes LAN
        Systems, March 1991.
   
   [9]  Rose, M., Editor, "A Convention for Defining Traps for use with
        the SNMP", RFC 1215, Performance Systems International, March
        1991.
   
   [10] ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges".
   
   [11] ISO/IEC Final CD 15802-3, ANSI/IEEE Std 802.1D-1998 "Information
        technology - Telecommunications and information exchange between
        systems - Local and metropolitan area networks - Common
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 78]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
        specifications - Part 3: Media Access Control (MAC) Bridges:
        Revision (Incorporating IEEE P802.1p: Traffic Class Expediting
        and Dynamic Multicast Filtering)", November 1997.
   
   [12] ANSI/IEEE Draft Standard P802.1Q/D9, "IEEE Standards for Local
        and Metropolitan Area Networks: Virtual Bridged Local Area
        Networks", February 1998.
   
   [13] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K.,
        "Definitions of Managed Objects for Bridges", RFC 1493, cisco
        Systems, Digital Equipment, Hughes LAN Systems, July 1993.
   
   [14] McCloghrie, K., Kastenholz, F.  "Evolution of the Interfaces
        Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software,
        January 1994.
   
   [15] Decker, E., McCloghrie, K., Langille, P., Rijsinghani, A.
        "Definitions of Managed Objects for Source Routing Bridges", RFC
        1525, cisco Systems, Hughes LAN Systems, Digital Equipment,
        September 1993
   
   [16] Jeyasubramanian, I., "Definitions of Managed Objects for IEEE
        802.1Q Virtual LAN Bridges", draft-jeya-vlan-8021q-mib-01.txt,
        FSPL, June 1997
   
   [17] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
        Waldbusser, "Protocol Operations for version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
   
   [18] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
        Waldbusser, "Structure of Management Information for version 2
        of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
        January 1996.
   
   [19] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
        Waldbusser, "Textual Conventions for version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
   
   [20] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
        Waldbusser, "Conformance Statements for version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 79]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   10.  Security Considerations
   
   Certain management information defined in this MIB may be considered
   sensitive in some network environments.  Therefore, authentication of
   received SNMP requests and controlled access to management
   information should be employed in such environments.  The method for
   this authentication is a function of the SNMP Administrative
   Framework, and has not been expanded by this MIB.
   
   Several objects in this MIB allow write access.  Setting these
   objects can have a serious effect on the operation of the network,
   including enabling or disabling forwarding of data.  It is
   recommended that implementers seriously consider whether set
   operations should be allowed without providing, at a minimum,
   authentication of request origin.
   
   
   
   
   11.  Authors' Addresses
   
        Les Bell
        3Com Europe Limited
        3Com Centre
        Boundary Way
        Hemel Hempstead
        Herts.  HP2 7YU
        UK
        +44 (1442) 438025
        les_bell@3com.com
   
        Andrew Smith
        Extreme Networks
        10460 Bandley Drive
        Cupertino CA 95014
        USA
        +1 (408) 342 0999
        andrew@extremenetworks.com
   
        Paul Langille
        Acacia Networks, Inc.
        650 Suffolk St.
        Lowell, MA 01854
        USA
        +1 (978) 275 0662
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 80]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
        plangille@acacianet.com
   
        Anil Rijsinghani
        Cabletron Systems
        550 King Street, LKG2-2/Y10
        Littleton, MA 01460-1289
        USA
        +1 (508) 486-6786
        anil@lkg.dec.com
   
        Keith McCloghrie
        cisco Systems, Inc.
        170 West Tasman Drive
        San Jose, CA 95134-1706
        USA
        +1 (408) 526 5260
        kzm@cisco.com
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 81]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   Table of Contents
   
   
   1 The SNMP Network Management Framework ........................    2
   1.1 Object Definitions .........................................    2
   2 Overview .....................................................    3
   2.1 Scope ......................................................    3
   3 Structure of MIBs ............................................    4
   3.1 Structure of Extended Bridge MIB module ....................    4
   3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ......    5
   3.1.2 The dot1dExtBase Group ...................................    6
   3.1.3 The dot1dPriority Group ..................................    6
   3.1.4 The dot1dGarp Group ......................................    6
   3.1.5 The dot1dGmrp Group ......................................    7
   3.1.6 The dot1dHCPort Group ....................................    7
   3.2 Structure of Virtual Bridge MIB module .....................    7
   3.2.1 Relationship to IEEE 802.1Q Manageable Objects ...........    7
   3.2.2 The dot1qBase Group ......................................   11
   3.2.3 The dot1qTp Group ........................................   11
   3.2.4 The dot1qStatic Group ....................................   11
   3.2.5 The dot1qVlan Group ......................................   11
   3.3 Textual Conventions ........................................   11
   3.4 Relationship to Other MIBs .................................   12
   3.4.1 Relationship to the 'system' group .......................   12
   3.4.2 Relation to Interfaces MIB ...............................   12
   3.4.2.1 Layering Model .........................................   13
   3.4.2.2 Interpretations of ifTable for VLANs ...................   14
   3.4.2.3 ifStackTable ...........................................   15
   3.4.2.4 ifRcvAddressTable ......................................   15
   3.4.3 Relation to Basic Bridge MIB .............................   15
   3.4.3.1 The dot1dBase Group ....................................   16
   3.4.3.2 The dot1dStp Group .....................................   16
   3.4.3.3 The dot1dTp Group ......................................   16
   3.4.3.4 The dot1dStatic Group ..................................   17
   4 Extensions to RFC 1493 .......................................   17
   5 Change Log and Editorial Stuff ...............................   18
   5.1 Changes since draft-bell-bridgemib-00.txt ..................   18
   5.2 To Do List .................................................   20
   5.3 Open Issues ................................................   20
   5.4 Closed Issues in his Draft .................................   21
   6 Definitions for Extended Bridge MIB ..........................   23
   7 Definitions for Virtual Bridge MIB ...........................   39
   8 Acknowledgments ..............................................   77
   9 References ...................................................   78
   10 Security Considerations .....................................   80
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 82]


   Internet Draft          Bridge MIB Extensions              April 1998
   
   
   11 Authors' Addresses ..........................................   80
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   Bell, et al.            Expires October 1998        [Page 83]
   

Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/