draft-ietf-bridge-bridgemib-03.txt   draft-ietf-bridge-bridgemib-04.txt 
Internet Draft E.L. Bell Internet Draft E.L. Bell
Expires May 1999 3Com Corp. Expires July 1999 3Com Corp.
draft-ietf-bridge-bridgemib-03.txt A. Smith draft-ietf-bridge-bridgemib-04.txt A. Smith
Standards Track Extreme Networks Standards Track Extreme Networks
P. Langille P. Langille
Acacia Networks Newbridge Networks
A. Rijhsinghani A. Rijhsinghani
Cabletron Systems Cabletron Systems
K. McCloghrie K. McCloghrie
cisco Systems cisco Systems
November 1998 January 1999
Definitions of Managed Objects for Bridges with Traffic Definitions of Managed Objects for Bridges with Traffic
Classes, Multicast Filtering and Virtual LAN Extensions Classes, Multicast Filtering and Virtual LAN Extensions
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
documents at any time. It is not appropriate to use Internet Drafts as 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 reference material or to cite them other than as a "working draft" or
"work in progress." "work in progress."
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe), Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
This document is a product of the IETF's Bridge MIB Working Group. This document is a product of the IETF's Bridge MIB Working Group.
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP based internets. In use with network management protocols in TCP/IP based internets. In
particular it defines objects for managing MAC bridges based on the IEEE particular it defines objects for managing MAC bridges based on the IEEE
802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN (VLAN) 802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN (VLAN)
standards for bridging between Local Area Network (LAN) segments. standards for bridging between Local Area Network (LAN) segments.
Provisions are made for support of transparent bridging. Provisions are Provisions are made for support of transparent bridging. Provisions are
skipping to change at page 10, line 37 skipping to change at page 10, line 37
allocations allocations
12.10.3.6 read FID allocated to VID 12.10.3.6 read FID allocated to VID
12.10.3.7 read VIDs allocated to 12.10.3.7 read VIDs allocated to
FID FID
dot1qVlanTimeMark dot1qVlanTimeMark
dot1qVlanIndex dot1qVlanIndex
dot1qVlanFdbId dot1qVlanFdbId
dot1qVlanCurrentEgressPorts dot1qVlanCurrentEgressPorts
dot1qVlanCurrentUntaggedPorts dot1qVlanCurrentUntaggedPorts
dot1qVlanStatus dot1qVlanStatus
dot1qVlanCreationTime
dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read
filtering entry filtering entry
12.7.6.1 read permanent database 12.7.6.1 read permanent database
12.10.2.2 create vlan config 12.10.2.2 create vlan config
12.10.2.3 delete vlan config 12.10.2.3 delete vlan config
dot1qVlanStaticName 12.4.1.3 set bridge name dot1qVlanStaticName 12.4.1.3 set bridge name
dot1qVlanStaticEgressPorts dot1qVlanStaticEgressPorts
dot1qVlanForbiddenEgressPorts dot1qVlanForbiddenEgressPorts
dot1qVlanStaticUntaggedPorts dot1qVlanStaticUntaggedPorts
dot1qVlanStaticRowStatus dot1qVlanStaticRowStatus
skipping to change at page 18, line 19 skipping to change at page 19, line 5
(1) References point to sections of IEEE 802.1D-1998. (1) References point to sections of IEEE 802.1D-1998.
(2) Added support for multiple traffic classes and dynamic multicast (2) Added support for multiple traffic classes and dynamic multicast
filtering as per IEEE 802.1D-1998. filtering as per IEEE 802.1D-1998.
(3) Added support for bridged Virtual LANs as per IEEE 802.1Q-1998. (3) Added support for bridged Virtual LANs as per IEEE 802.1Q-1998.
(4) Added support for 64-bit versions of existing RFC1493 port (4) Added support for 64-bit versions of existing RFC1493 port
counters. counters.
5. Change Log and Editorial Stuff 5. Definitions for Extended Bridge MIB
[Editor: this section will be removed before publication.]
5.1. Changes since draft-ietf-bridge-bridgemib-02.txt
SMIv2 conformance:
Replaced 'UInteger32' with 'Unsigned32'. Replaced 'BIT STRING'
with 'BITS'. Import 'MacAddress' from RFC1903 (SNMPv2-TC) instead
of RFC1493 (BRIDGE-MIB).
Object descriptions clarified:
dot1dTpHCPortInDiscards, dot1qTpVlanPortInDiscards,
dot1qTpVlanPortHCInDiscards
New issues 78-80
Editorial - updated REVISION dates
5.2. Open Issues
(80) Definition of dot1qTpVlanPortInDiscards and
dot1qTpVlanPortHCInDiscards is inconsistent with counters in IEEE
802.1Q-1998 and is underspecified (AHS)
5.3. Issues closed in this draft
The following issues were raised on the mailing list since publication
of the previous draft. Suggested resolutions discussed on the mailing
list are noted here and the changes have been made to the text - they
are listed here for comment:
(77) Should dot1qTpVlanPortInDiscards and dot1qTpVlanPortHCInDiscards
count all frames discarded at receive by the VLAN layer? (AR) -
YES: descriptions updated.
(78) Some SMIv2/syntax errors: UInteger32 should be Unsigned32, BIT
STRINg should be BITS. FIXED.
(79) MacAddress should be imported from RFC1903, not RFC1493. FIXED.
5.4. Issues closed in previous drafts
(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.
(2) Indexing of tables by VlanId or by ifIndex? use VlanId with special
semantics for values >=4096. This raises new issue 49.
(3) Indexing of FDB tables by MacAddress or by something else? Use
MacAddress.
(4) Include RFC1493 by value or reference? REFERENCE
(5) ifStackTable usage - how to represent binding of IP interfaces to
VLANs now that we do not necessarily have one ifEntry per VLAN. -
Not included due to lack of enthusiasm from the group.
(6) Representations of filtering entry for "AllGroups" and
"AllUnregisteredGroups" DONE
(7) Should we represent all available FIDs up front or use a "next
free" object for the manager to create them as needed? NEITHER -
see issue 25 above.
(8) Learned entry discards counter per-VLAN or per-device? Per-device,
already in RFC1493.
(9) Do we need per-FID static/dynamic filtering entry counts?
(12.7.1.1.3) YES - count for dynamic only added as
dot1qFdbDynamicCount.
(10) Separate config and status info for e.g. dot1dPortGmrpTable,
dot1qPortVlanTable? NO CHANGE
(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? YES. Affects dot1qVlanStaticEgressPorts,
dot1qVlanForbiddenEgressPorts and dot1dStaticAllowedToGoTo - added
clarification to DESCRIPTION clauses for the first two (but we
cannot add to RFC1493).
Do we need per-VLAN and per-Group Applicant controls? NEITHER -
per-port is sufficient on dot1qPortGvrpStatus and
dot1pPortGmrpStatus.
(12) Should the per-port GARP admin controls apply to Registrar as well
as Applicant (dot1qPortGvrpStatus, dot1pPortGmrpStatus)?
Alternative would be to provide separate controls for Applicant and
Registrar. YES - No change.
(13) Learning constraints table seems clumsy - can we improve this? DONE
(14) Do we need to define a "notify vlan registration failure" trap? NO
(15) dot1qFdbAgingTime is currently per-FID: 802.1Q has it per-device.
PER DEVICE
(16) dot1pPortDefaultUserPriority - can this usefully be per-port, per-
VLAN? PER-PORT
(17) Both dot1qVlanCurrentTable and dot1qVlanStaticTable are indexed by
dot1qVlanIfIndex but that only appears in dot1qVlanStaticTable - is
this a problem? MOVED TO dot1qVlanCurrentTable.
(18) Should we choose same names (up/down) as IF-MIB for values of the
admin/oper status values, rather than defining our own new TC? Is
there an existing TC we can import? NO CHANGE.
(19) Should we have write-only "reset" objects or should these be read-
write to help MIB browsers (assume write-only)? READ-WRITE.
(20) Do we need "read filtering database (12.7.1.1): filtering database
size"? NO
(21) Do we need "read permanent database (12.7.6.1): permanent database
size"? NO (this issue was wrongly recorded last time)
(22) Do we need a 'next free ifIndex' object? NO - see issue 2. But see
new issue 49.
(23) Do we need default learning constraints? YES - mandatory if device
is Hybrid-VLAN-Learning-capable (can do both IVL and SVL).
(24) Can we remove separate GARP controls? YES.
(25) Do we need to split dot1qStaticTable into dot1qStaticUnicastTable
and dot1qStaticMulticastTable? YES: dot1qStaticTable ->
dot1qStaticUnicastTable, indexed by FID +
dot1qStaticMulticastTable, indexed by VID. Also index
dot1qTpGroupTable by VID. This matches the indexing assumed by
802.1Q.
(26) Should we have the different Service Requirements (AllGroups,
AllUnregisteredGroups) in dot1qServiceReqTable or should we leave
with dot1qServiceRequirement as a 2nd index? Split into 2 tables,
each indexed by VID.
(27) Do we want "capabilities" bitmap objects? YES - per-port
dot1dPortCapabilities and dot1dDeviceCapabilities.
(28) Should ifRcvAddressTable contain entries for e.g. spanning-tree,
GMRP, GVRP addresses? NO - clarify in preface.
(29) dot1dTrafficClassesResetToDefaults - says that it resets stats too.
What about userPriorityRegenTable? (AR): NUKE
dot1dTrafficClassesResetToDefaults
(30) Trunk ports - should MIB support such a concept (802.1Q does not)?
NO
(31) dot1qVlanBridgeUpTime: is this needed per-VLAN? ifLastChange can
do this function if we have ifTable entries per-VLAN: NO
(32) Timestamp-based indexing for some tables? dot1dTpFdbTable in
RFC1493 - NO dot1qTpFdbTable - NO, TimeFilter not practical;
lastChange not useful dot1qVlanCurrentTable - YES- added both
dot1qVlanTimeMark and dot1qVlanNumDeletes. dot1qStaticTable? NO -
cannot use TimeFilter on read-create tables.
dot1qLearningConstraintsTable? NO, add
dot1qLearningConstraintsLastChange. dot1qPortVlanTable? NO - these
are mostly management settable objects.
(33) DEFVAL and MIN-ACCESS for dot1qForwardAllStaticPorts and
dot1qForwardUnregisteredStaticPorts? updated descriptions and these
objects are in an optional group, so MIN-ACCESS not-accessible is
not required.
(34) Should an agent instantiate a set of dot1qForwardAllTable and
dot1qForwardUnregisteredTable entries for each FDB that it could
have or just a set for each FDB that is currently in use? The
latter - added clarification.
(35) Nuke dot1qStaticReceivePort? There are not any implementations of
the RFC1493 equivalent are there? Yes there are - keep it.
(36) Should agent accept SETs to dot1qVlanStaticUntaggedPorts,
dot1qVlanStaticEgressPorts, dot1qVlanForbiddenEgressPorts that it
cannot actually implement? (ELB) NO - clarify description.
(37) Nuke dot1dPortGmrp/GvrpOperStatus? - YES.
(38) Nuke dot1qResetToDefaults? (KZM) - YES
(39) Nuke dot1dGarpReset? (KZM) YES, and update DESCRIPTIONs of
dot1dGmrpStatus, dot1qGvrpStatus, dot1dPortGmrpStatus,
dot1qPortGvrpStatus,
(40) Make dot1dPortGarp timers per-device, not per-port? (KZM) saves
NVRAM - Leave it the same.
(41) MIN-ACCESS read-only for dot1dTrafficClass, dot1dRegenUserPriority
(KZM) - done.
(42) dot1qTpGroupGmrp/Igmp (KZM) - merge these to dot1qTpGroupLearnt -
Yes.
(43) Do we need 64-bit dot1qHC errors? (KZM) - Yes.
(44) Clarification of dot1qHC counter descriptions - what does inbound
mean? What counts as errors? 2 separable issues:
1. It was requested that the meaning of dot1qDiscardInbound be
clarified to ensure it is distinct from other counters.
(Specifically, why is it different from 1493?) (KZM) - this can be
derived from other counters - NUKE IT!
2. Why are all of these so different from RFC1493? e.g. do they
refer to Transparent-only? What about SRT or SR? - Counters
limited to a set equivalent to RFC1493.
(45) Do we need dot1qVersion? (KZM) - Yes.
(46) Nuke dot1qTpFdbClear? dot1qFdbClear? (KZM) - Yes (802.1Q "reset
bridge" operation is not now supported).
(47) Do we need dot1qFdbTable which now contains only dot1qFdbId? - YES
(it also now has dot1qFdbDynamicCount).
(48) Should dot1qTpFdbTable be {FID,MAC} or {MAC,FID} - the former.
(49) Now that dot1qVlanStaticTable is indexed by VlanIndex/VlanId we
need a "next free" variable since these values must be managed by
agent. - Added dot1qVlanNextFreeIndex.
(50) dot1qVlanFdbId, dot1qMaxSupportedVlans, dot1qNumVlans should not be
range-limited. If they are then we need new objects to represent
the number of non-802.1Q "VLANs" too. (AHS) - Range restrictions
removed.
(51) dot1qConfigurablePvidTagging: does this also cover the "I can only
set a single VLAN to be untagged on egress" implementation option
in 802.1Q? - Description of dot1qVlanStaticUntaggedPorts clarified
to cover this.
(52) Do we need an explicit "dot1dExtendedFilteringServicesStatus"
enable/disable object? (AHS) - No.
(53) Should mention that VLAN entries in ifTable should have
ifPhysAddress zero-length/filled (KK). No longer relevant since we
do not include such ifTable entries.
(54) dot1qVlanAdminUntaggedPorts - expand DESCRIPTION to include meaning
of 0 (KK). Changed description to talk about include/exclude from
the set of ports: refer to Portlist TC for 0/1 meaning.
(55) Need to split dot1qStaticAllowedToGoTo into two portmaps in order
to represent the 3 possible states from 802.1Q 8.11.2: static,
forbidden and allowed to be influenced by dynamic info. (ELB) DONE
for multicast - split dot1qStaticAllowedToGoTo into
dot1qStaticMulticastStaticEgressPorts and
dot1qStaticMulticastForbiddenEgressPorts. Same issue for unicast
table. - Not required to split this for unicast.
(56) Should a value of 0 be allowed for dot1qTpFdbPort? This is
inherited from RFC1493. (ELB) - Yes it is allowed. No change
required.
(57) Rename dot1qVlanStaticUntagged as dot1qVlanStaticUntaggedPorts for
consistency. (ELB) - Done.
(58) If an empty string is used for dot1qVlanStaticName, does it have to
be unique? The description implies it must be unique. (ELB) NO -
clarified this.
(59) Should dot1qPvid have syntax VlanIndex (currently it is VlanId)?
(ELB) - Yes, done.
(60) Do dot1qPortAcceptableFrameTypes and dot1qPortIngressFiltering also
apply to tagged GMRP packets? (ELB) - Yes, descriptions clarified.
(61) Do we need dot1qLearningContraintsLastChange? It just reminds the
manager of changes that he or some other manager made. (ELB) - No,
object removed.
(62) Remove support for multiple egress ports in static unicast FDB
entries? (KK) - Not applicable. The entry indicates ports a
unicast address MAY be learnt on, not ports it MUST be forwarded
to. Description clarified.
(63) dot1dGmrpStatus is a member of a mandatory group and has a DEFVAL
of "enabled". This is inappropriate for devices which do not
support extended filtering services but do support priority
forwarding and therefore implement this MIB. (DM) - Similar
problem with dot1dTrafficClassesEnabled. Defined both of these in
separate groups, each group is mandatory only if that feature is
supported by the bridge. Capabilities bit added to indicate
support for traffic classes. Removed MIN-ACCESS for
dot1dTrafficClassesEnabled.
(64) dot1dPortCapabilities, dot1qPortIngressFiltering - tighten up the
text to read: "supports the discarding of any frame received on
that Port whose VLAN classification does not include that Port in
its Member set." (DM) - Done. Also changed the name of the
capability bit for this to dot1qIngressFiltering to resolve
duplicate name. Changed the description of
dot1qPortIngressFiltering object to match the above text.
(65) dot1qConfigurablePvidTagging - According to 802.1Q it is a
requirement. Is there a reason to treat it as optional in the MIB?
(DM) - Reference is 12.10.1.1.3/b/2. The 802.1Q description is
"whether the implementation supports the ability to override the
default PVID setting and its egress status (VLAN-Tagged or
Untagged) on each port". Capability description modified with the
above quote from the standard.
(66) PVID tagging should be moved from dot1dPortCapabilities to
dot1dDeviceCapabilities. (AHS) - Done.
(67) dot1dUserPriorityRegenTable - is not relevant for Ethernet LANs. A
statement to this effect and a reference (ISO/IEC 15802-3 6.4) may
be helpful. (DM) - Done. Also put this in a separate conformance
group, mandatory for media which support native User Priority.
dot1dTrafficClassTable updated to be independent of this table.
(68) What should the compliance be for dot1dPortDefaultUserPriority?
(AHS) - Put this in a separate conformance group, mandatory for
media which do not support native User Priority.
(69) There are no definitions for qBridgeFdbGroup or qBridgeTpFdbGroup -
remove references to these in qBridgeCompliance section. (AHS) -
Done.
(70) Should we count the number of dynamic group address entries per
VLAN? (AHS) - This can be derived by counting rows in
dot1dTpGroupTable. Added it to the 'not included' list in section
3.2.1.
(71) dot1qTpGroupAllowedToGoTo really means 'forward to'. (DM) - The
description has been clarified and the object renamed as
'dot1qTpGroupEgressPorts'.
(72) Why provide a default value for dot1qStaticUnicastAllowedToGoTo?
It should include only member ports of the frame's VLAN
classification. The phrase "a string of ones" is incorrect. Also
for dot1qStaticMulticastStaticEgressPorts. (DM) - Clarified the
description, this value only applies to ports also in the
dot1qVlanCurrentEgressPorts list for the VLAN. Also applied this
clarification to dot1qForwardAllStaticPorts.
(73) dot1qStaticUnicastAllowedToGoTo: why is the term "allowed" used
here? Doesn't this object define exactly to which port(s) the
frame is to be forwarded? (DM) - No. The consensus from recent
discussions interpret this as 'may be dynamically learnt on'.
Clarified the description.
(74) The Untagged Set for a VLAN is only modified statically by
management and this object will always have the same value as the
dot1qVlanStaticUntagged. If so, should it be eliminated. (DM) -
Untagged VLANs may also be dynamically learned. No change
required.
(75) The meaning of dot1qVlanStatus is confusing. (DM) - The description
has been clarified.
(76) dot1qVlanStatisticsTable potentially requires a very large number
of counters and may not be achievable in many architectures. A
control table which specifies for which VLANs the counters would be
maintained could limit the number of counters required. (DM) - Not
considered worthwhile. No change required.
6. Definitions for Extended Bridge MIB
P-BRIDGE-MIB DEFINITIONS ::= BEGIN P-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- IEEE 802.1p MIB -- IEEE 802.1p MIB
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64, BITS
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dTp, dot1dTpPort, dot1dBridge, dot1dTp, dot1dTpPort, dot1dBridge,
dot1dBasePortEntry, dot1dBasePort dot1dBasePortEntry, dot1dBasePort
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
pBridgeMIB MODULE-IDENTITY pBridgeMIB MODULE-IDENTITY
LAST-UPDATED "9811030000Z" LAST-UPDATED "9901070000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Les Bell " Les Bell
Postal: 3Com Europe Ltd. Postal: 3Com Europe Ltd.
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead, Herts. HP2 7YU Hemel Hempstead, Herts. HP2 7YU
UK UK
Phone: +44 1442 438025 Phone: +44 (1442) 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
Andrew Smith Andrew Smith
Postal: Extreme Networks Postal: Extreme Networks
10460 Bandley Drive 10460 Bandley Drive
Cupertino CA 95014 Cupertino CA 95014
USA USA
Phone: +1 (408) 342 0999 Phone: +1 (408) 342 0999
Email: andrew@extremenetworks.com Email: andrew@extremenetworks.com
Paul Langille Paul Langille
Postal: Acacia Networks, Inc. Postal: Newbridge Networks
650 Suffolk St. 5 Corporate Drive
Lowell, MA 01854 Andover, MA 01810
USA USA
Phone: +1 (978) 275 0662 Phone: +1 (978) 691 4665
Email: plangille@acacianet.com Email: langille@newbridge.com
Anil Rijhsinghani Anil Rijhsinghani
Postal: Cabletron Systems Postal: Cabletron Systems
50 Minuteman Road 50 Minuteman Road
Andover MA 01810 Andover MA 01810
USA USA
Phone: +1 (978) 684-1295 Phone: +1 (978) 684 1295
Email: anil@cabletron.com Email: anil@cabletron.com
Keith McCloghrie Keith McCloghrie
Postal: cisco Systems, Inc. Postal: cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
USA USA
Phone: +1 (408) 526 5260 Phone: +1 (408) 526 5260
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing Priority "The Bridge MIB Extension module for managing Priority
and Multicast Filtering, defined by IEEE 802.1D-1998." and Multicast Filtering, defined by IEEE 802.1D-1998."
REVISION "9810070000Z"
DESCRIPTION "Updated with revisions from August 1998 Plenary
meeting."
REVISION "9811030000Z"
DESCRIPTION "Updated with changes agreed on mailing list
after August 1998 IETF."
::= { dot1dBridge 6 } ::= { dot1dBridge 6 }
pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 } pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
EnabledStatus ::= TEXTUAL-CONVENTION EnabledStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 30, line 36 skipping to change at page 22, line 30
DESCRIPTION DESCRIPTION
"The administrative status requested by management for "The administrative status requested by management for
GMRP. The value enabled(1) indicates that GMRP should GMRP. The value enabled(1) indicates that GMRP should
be enabled on this device, in all VLANs, on all ports be enabled on this device, in all VLANs, on all ports
for which it has not been specifically disabled. When for which it has not been specifically disabled. When
disabled(2), GMRP is disabled, in all VLANs, on all disabled(2), GMRP is disabled, in all VLANs, on all
ports and all GMRP packets will be forwarded ports and all GMRP packets will be forwarded
transparently. This object affects both Applicant and transparently. This object affects both Applicant and
Registrar state machines. A transition from disabled(2) Registrar state machines. A transition from disabled(2)
to enabled(1) will cause a reset of all GMRP state to enabled(1) will cause a reset of all GMRP state
machines on all ports and zeroing of all related machines on all ports."
counters."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1dExtBase 3 } ::= { dot1dExtBase 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Port Capabilities Table -- Port Capabilities Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dPortCapabilitiesTable OBJECT-TYPE dot1dPortCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dPortCapabilitiesEntry SYNTAX SEQUENCE OF Dot1dPortCapabilitiesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 39, line 9 skipping to change at page 30, line 43
"The state of GMRP operation on this port. The value "The state of GMRP operation on this port. The value
enabled(1) indicates that GMRP is enabled on this port, enabled(1) indicates that GMRP is enabled on this port,
in all VLANs, as long as dot1dGmrpStatus is also enabled in all VLANs, as long as dot1dGmrpStatus is also enabled
for this device. When disabled(2) but dot1dGmrpStatus for this device. When disabled(2) but dot1dGmrpStatus
is still enabled for the device, GMRP is disabled on is still enabled for the device, GMRP is disabled on
this port in all VLANs: any GMRP packets received will this port in all VLANs: any GMRP packets received will
be silently discarded and no GMRP registrations will be be silently discarded and no GMRP registrations will be
propagated from other ports. This object affects all propagated from other ports. This object affects all
GMRP Applicant and Registrar state machines on this GMRP Applicant and Registrar state machines on this
port. A transition from disabled(2) to enabled(1) will port. A transition from disabled(2) to enabled(1) will
cause a reset of all GMRP state machines on this port cause a reset of all GMRP state machines on this port."
and zeroing of all related counters."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1dPortGmrpEntry 1 } ::= { dot1dPortGmrpEntry 1 }
dot1dPortGmrpFailedRegistrations OBJECT-TYPE dot1dPortGmrpFailedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of failed GMRP registrations, for any "The total number of failed GMRP registrations, for any
reason, in all VLANs, on this port." reason, in all VLANs, on this port."
skipping to change at page 47, line 5 skipping to change at page 38, line 5
OBJECT dot1dRegenUserPriority OBJECT dot1dRegenUserPriority
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { pBridgeCompliances 1 } ::= { pBridgeCompliances 1 }
END END
7. Definitions for Virtual Bridge MIB 6. Definitions for Virtual Bridge MIB
Q-BRIDGE-MIB DEFINITIONS ::= BEGIN Q-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- IEEE 802.1Q MIB -- IEEE 802.1Q MIB
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Counter64, Unsigned32 Counter32, Counter64, Unsigned32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, TruthValue, DisplayString, TEXTUAL-CONVENTION RowStatus, TruthValue, DisplayString, TEXTUAL-CONVENTION,
MacAddress
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
MacAddress, dot1dBridge, dot1dBasePortEntry, dot1dBasePort dot1dBridge, dot1dBasePortEntry, dot1dBasePort
FROM BRIDGE-MIB FROM BRIDGE-MIB
EnabledStatus EnabledStatus
FROM P-BRIDGE-MIB FROM P-BRIDGE-MIB
TimeFilter TimeFilter
FROM RMON2-MIB; FROM RMON2-MIB;
qBridgeMIB MODULE-IDENTITY qBridgeMIB MODULE-IDENTITY
LAST-UPDATED "9811030000Z" LAST-UPDATED "9901070000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Les Bell " Les Bell
Postal: 3Com Europe Ltd. Postal: 3Com Europe Ltd.
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead, Herts. HP2 7YU Hemel Hempstead, Herts. HP2 7YU
UK UK
Phone: +44 1442 438025 Phone: +44 (1442) 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
Andrew Smith Andrew Smith
Postal: Extreme Networks Postal: Extreme Networks
10460 Bandley Drive 10460 Bandley Drive
Cupertino CA 95014 Cupertino CA 95014
USA USA
Phone: +1 (408) 342 0999 Phone: +1 (408) 342 0999
Email: andrew@extremenetworks.com Email: andrew@extremenetworks.com
Paul Langille Paul Langille
Postal: Acacia Networks, Inc. Postal: Newbridge Networks
650 Suffolk St. 5 Corporate Drive
Lowell, MA 01854 Andover, MA 01810
USA USA
Phone: +1 (978) 275 0662 Phone: +1 (978) 691 4665
Email: plangille@acacianet.com Email: langille@newbridge.com
Anil Rijhsinghani Anil Rijhsinghani
Postal: Cabletron Systems Postal: Cabletron Systems
50 Minuteman Road 50 Minuteman Road
Andover MA 01810 Andover MA 01810
USA USA
Phone: +1 (978) 684-1295 Phone: +1 (978) 684 1295
Email: anil@cabletron.com Email: anil@cabletron.com
Keith McCloghrie Keith McCloghrie
Postal: cisco Systems, Inc. Postal: cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
USA USA
Phone: +1 (408) 526 5260 Phone: +1 (408) 526 5260
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The VLAN Bridge MIB module for managing Virtual Bridged "The VLAN Bridge MIB module for managing Virtual Bridged
Local Area Networks, as defined by IEEE 802.1Q-1998." Local Area Networks, as defined by IEEE 802.1Q-1998."
REVISION "9810070000Z"
DESCRIPTION "Updated with revisions from August 1998 Plenary
meeting."
REVISION "9811030000Z"
DESCRIPTION "Updated with changes agreed on mailing list
after August 1998 IETF."
::= { dot1dBridge 7 } ::= { dot1dBridge 7 }
qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 } qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
PortList ::= TEXTUAL-CONVENTION PortList ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 51, line 18 skipping to change at page 42, line 10
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative status requested by management for "The administrative status requested by management for
GVRP. The value enabled(1) indicates that GVRP should GVRP. The value enabled(1) indicates that GVRP should
be enabled on this device, on all ports for which it has be enabled on this device, on all ports for which it has
not been specifically disabled. When disabled(2), GVRP not been specifically disabled. When disabled(2), GVRP
is disabled on all ports and all GVRP packets will be is disabled on all ports and all GVRP packets will be
forwarded transparently. This object affects all GVRP forwarded transparently. This object affects all GVRP
Applicant and Registrar state machines. A transition Applicant and Registrar state machines. A transition
from disabled(2) to enabled(1) will cause a reset of all from disabled(2) to enabled(1) will cause a reset of all
GVRP state machines on all ports and zeroing of all GVRP state machines on all ports."
related counters."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1qBase 5 } ::= { dot1qBase 5 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- the dot1qTp group -- the dot1qTp group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- the current Filtering Database Table -- the current Filtering Database Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 61, line 22 skipping to change at page 52, line 13
entry's filtering information to apply. A value of zero entry's filtering information to apply. A value of zero
indicates that this entry applies on all ports of the indicates that this entry applies on all ports of the
device for which there is no other applicable entry." device for which there is no other applicable entry."
::= { dot1qStaticUnicastEntry 2 } ::= { dot1qStaticUnicastEntry 2 }
dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports a specific unicast address may be "The set of ports for which a frame with a specific
dynamically learnt on. The dot1qTpFdbTable will have an unicast address will be flooded in the event that it
equivalent entry with a dot1qTpFdbPort value of '0' has not been learned. It also specifies the set of
until this address has been learnt, when it will be ports a specific unicast address may be dynamically
updated with the port the address has been seen on. learnt on. The dot1qTpFdbTable will have an equivalent
This only applies to ports that are members of the VLAN, entry with a dot1qTpFdbPort value of '0' until this
defined by dot1qVlanCurrentEgressPorts. The default address has been learnt, when it will be updated with
value of this object is a string of ones of appropriate the port the address has been seen on. This only
length." applies to ports that are members of the VLAN, defined
by dot1qVlanCurrentEgressPorts. The default value of
this object is a string of ones of appropriate length."
REFERENCE
"IEEE 802.1Q/D11 Table 8-5, ISO/IEC 15802-3 Table 7-5"
::= { dot1qStaticUnicastEntry 3 } ::= { dot1qStaticUnicastEntry 3 }
dot1qStaticUnicastStatus OBJECT-TYPE dot1qStaticUnicastStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
invalid(2), invalid(2),
permanent(3), permanent(3),
deleteOnReset(4), deleteOnReset(4),
deleteOnTimeout(5) deleteOnTimeout(5)
} }
skipping to change at page 65, line 29 skipping to change at page 56, line 24
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times a VLAN entry has been deleted from "The number of times a VLAN entry has been deleted from
the dot1qVlanCurrentTable (for any reason). If an entry the dot1qVlanCurrentTable (for any reason). If an entry
is deleted, then inserted, and then deleted, this is deleted, then inserted, and then deleted, this
counter will be incremented by 2." counter will be incremented by 2."
::= { dot1qVlan 1 } ::= { dot1qVlan 1 }
dot1qVlanCurrentTable OBJECT-TYPE dot1qVlanCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qVlanEntry SYNTAX SEQUENCE OF Dot1qVlanCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing current configuration information "A table containing current configuration information
for each VLAN currently configured into the device by for each VLAN currently configured into the device by
(local or network) management, or dynamically created (local or network) management, or dynamically created
as a result of GVRP requests received." as a result of GVRP requests received."
::= { dot1qVlan 2 } ::= { dot1qVlan 2 }
dot1qVlanEntry OBJECT-TYPE dot1qVlanCurrentEntry OBJECT-TYPE
SYNTAX Dot1qVlanEntry SYNTAX Dot1qVlanCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information for a VLAN configured into the device by "Information for a VLAN configured into the device by
(local or network) management, or dynamically created (local or network) management, or dynamically created
as a result of GVRP requests received." as a result of GVRP requests received."
INDEX { dot1qVlanTimeMark, dot1qVlanIndex } INDEX { dot1qVlanTimeMark, dot1qVlanIndex }
::= { dot1qVlanCurrentTable 1 } ::= { dot1qVlanCurrentTable 1 }
Dot1qVlanEntry ::= Dot1qVlanCurrentEntry ::=
SEQUENCE { SEQUENCE {
dot1qVlanTimeMark dot1qVlanTimeMark
TimeFilter, TimeFilter,
dot1qVlanIndex dot1qVlanIndex
VlanIndex, VlanIndex,
dot1qVlanFdbId dot1qVlanFdbId
Unsigned32, Unsigned32,
dot1qVlanCurrentEgressPorts dot1qVlanCurrentEgressPorts
PortList, PortList,
dot1qVlanCurrentUntaggedPorts dot1qVlanCurrentUntaggedPorts
PortList, PortList,
dot1qVlanStatus dot1qVlanStatus
INTEGER INTEGER,
dot1qVlanCreationTime
TimeTicks
} }
dot1qVlanTimeMark OBJECT-TYPE dot1qVlanTimeMark OBJECT-TYPE
SYNTAX TimeFilter SYNTAX TimeFilter
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A TimeFilter for this entry. See the TimeFilter "A TimeFilter for this entry. See the TimeFilter
textual convention to see how this works." textual convention to see how this works."
::= { dot1qVlanEntry 1 } ::= { dot1qVlanCurrentEntry 1 }
dot1qVlanIndex OBJECT-TYPE dot1qVlanIndex OBJECT-TYPE
SYNTAX VlanIndex SYNTAX VlanIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VLAN-ID or other identifier refering to this VLAN." "The VLAN-ID or other identifier refering to this VLAN."
::= { dot1qVlanEntry 2 } ::= { dot1qVlanCurrentEntry 2 }
dot1qVlanFdbId OBJECT-TYPE dot1qVlanFdbId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Filtering Database used by this VLAN. This is one "The Filtering Database used by this VLAN. This is one
of the dot1qFdbId values in the dot1qFdbTable. This of the dot1qFdbId values in the dot1qFdbTable. This
value is allocated automatically by the device whenever value is allocated automatically by the device whenever
the VLAN is created: either dynamically by GVRP, or by the VLAN is created: either dynamically by GVRP, or by
management, in dot1qVlanStaticTable. Allocation of this management, in dot1qVlanStaticTable. Allocation of this
value follows the learning constraints defined for this value follows the learning constraints defined for this
VLAN in dot1qLearningConstraintsTable." VLAN in dot1qLearningConstraintsTable."
::= { dot1qVlanEntry 3 } ::= { dot1qVlanCurrentEntry 3 }
dot1qVlanCurrentEgressPorts OBJECT-TYPE dot1qVlanCurrentEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are transmitting traffic for "The set of ports which are transmitting traffic for
this VLAN as either tagged or untagged frames." this VLAN as either tagged or untagged frames."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanEntry 4 } ::= { dot1qVlanCurrentEntry 4 }
dot1qVlanCurrentUntaggedPorts OBJECT-TYPE dot1qVlanCurrentUntaggedPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are transmitting traffic for "The set of ports which are transmitting traffic for
this VLAN as untagged frames." this VLAN as untagged frames."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanEntry 5 } ::= { dot1qVlanCurrentEntry 5 }
dot1qVlanStatus OBJECT-TYPE dot1qVlanStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
permanent(2), permanent(2),
dynamicGvrp(3) dynamicGvrp(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 68, line 6 skipping to change at page 59, line 4
permanent(2) - this entry, corresponding to an entry permanent(2) - this entry, corresponding to an entry
in dot1qVlanStaticTable, is currently in use and in dot1qVlanStaticTable, is currently in use and
will remain so after the next reset of the will remain so after the next reset of the
device. The port lists for this entry include device. The port lists for this entry include
ports from the equivalent dot1qVlanStaticTable ports from the equivalent dot1qVlanStaticTable
entry and ports learnt dynamically. entry and ports learnt dynamically.
dynamicGvrp(3) - this entry is currently in use dynamicGvrp(3) - this entry is currently in use
and will remain so until removed by GVRP. There and will remain so until removed by GVRP. There
is no static entry for this VLAN and it will be is no static entry for this VLAN and it will be
removed when the last port leaves the VLAN." removed when the last port leaves the VLAN."
::= { dot1qVlanEntry 6 } ::= { dot1qVlanCurrentEntry 6 }
dot1qVlanCreationTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when this VLAN was created."
::= { dot1qVlanCurrentEntry 7 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The Static VLAN Database -- The Static VLAN Database
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qVlanStaticTable OBJECT-TYPE dot1qVlanStaticTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qVlanStaticEntry SYNTAX SEQUENCE OF Dot1qVlanStaticEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 69, line 4 skipping to change at page 60, line 10
dot1qVlanForbiddenEgressPorts dot1qVlanForbiddenEgressPorts
PortList, PortList,
dot1qVlanStaticUntaggedPorts dot1qVlanStaticUntaggedPorts
PortList, PortList,
dot1qVlanStaticRowStatus dot1qVlanStaticRowStatus
RowStatus RowStatus
} }
dot1qVlanStaticName OBJECT-TYPE dot1qVlanStaticName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..32)) SYNTAX DisplayString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An administratively assigned string, which may be used "An administratively assigned string, which may be used
to identify the VLAN." to identify the VLAN."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 1 } ::= { dot1qVlanStaticEntry 1 }
dot1qVlanStaticEgressPorts OBJECT-TYPE dot1qVlanStaticEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are permanently assigned to the "The set of ports which are permanently assigned to the
egress list for this VLAN by management. Changes to a egress list for this VLAN by management. Changes to a
bit in this object affect the per-port per-VLAN bit in this object affect the per-port per-VLAN
Registrar control for Registration Fixed for the Registrar control for Registration Fixed for the
relevant GVRP state machine on each port. The default relevant GVRP state machine on each port. A port may
value of this object is a string of zeros of appropriate not be added in this set if it is already a member of
length, indicating not fixed." the set of ports in dot1qVlanForbiddenEgressPorts. The
default value of this object is a string of zeros of
appropriate length, indicating not fixed."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 2 } ::= { dot1qVlanStaticEntry 2 }
dot1qVlanForbiddenEgressPorts OBJECT-TYPE dot1qVlanForbiddenEgressPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which are prohibited by management "The set of ports which are prohibited by management
from being included in the egress list for this VLAN. from being included in the egress list for this VLAN.
Changes to this object that cause a port to be included Changes to this object that cause a port to be included
or excluded affect the per-port per-VLAN Registrar or excluded affect the per-port per-VLAN Registrar
control for Registration Forbidden for the relevant control for Registration Forbidden for the relevant GVRP
GVRP state machine on each port. The default value of state machine on each port. A port may not be added in
this set if it is already a member of the set of ports
in dot1qVlanStaticEgressPorts. The default value of
this object is a string of zeros of appropriate length, this object is a string of zeros of appropriate length,
excluding all ports from the forbidden set." excluding all ports from the forbidden set."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3"
::= { dot1qVlanStaticEntry 3 } ::= { dot1qVlanStaticEntry 3 }
dot1qVlanStaticUntaggedPorts OBJECT-TYPE dot1qVlanStaticUntaggedPorts OBJECT-TYPE
SYNTAX PortList SYNTAX PortList
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The set of ports which should transmit egress packets "The set of ports which should transmit egress packets
for this VLAN as untagged. The default value of this for this VLAN as untagged. The default value of this
object for the default VLAN (VlanId 001) is a string object for the default VLAN (VlanId 001) is a string
of appropriate length including all ports. There is no of appropriate length including all ports. There is no
specified default for other VLANs. If a device cannot specified default for other VLANs. If a device cannot
support a value being set then its agent will reject the support a value being set then its agent will reject the
set operation. Attempts to set more than one VLAN to be set operation. Attempts to set more than one VLAN to be
untagged on egress may be rejected by devices which do untagged on egress may be rejected by devices which do
not support this option." not support this option."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.10.2.1" "IEEE 802.1Q/D11 Section 12.10.2.1"
::= { dot1qVlanStaticEntry 4 } ::= { dot1qVlanStaticEntry 4 }
dot1qVlanStaticRowStatus OBJECT-TYPE dot1qVlanStaticRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the status of this entry." "This object indicates the status of this entry."
::= { dot1qVlanStaticEntry 5 } ::= { dot1qVlanStaticEntry 5 }
dot1qNextFreeLocalVlanIndex OBJECT-TYPE dot1qNextFreeLocalVlanIndex OBJECT-TYPE
SYNTAX VlanIndex SYNTAX VlanIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 73, line 11 skipping to change at page 64, line 20
"The state of GVRP operation on this port. The value "The state of GVRP operation on this port. The value
enabled(1) indicates that GVRP is enabled on this port, enabled(1) indicates that GVRP is enabled on this port,
as long as dot1qGvrpStatus is also enabled for this as long as dot1qGvrpStatus is also enabled for this
device. When disabled(2) but dot1qGvrpStatus is still device. When disabled(2) but dot1qGvrpStatus is still
enabled for the device, GVRP is disabled on this port: enabled for the device, GVRP is disabled on this port:
any GVRP packets received will be silently discarded and any GVRP packets received will be silently discarded and
no GVRP registrations will be propagated from other no GVRP registrations will be propagated from other
ports. This object affects all GVRP Applicant and ports. This object affects all GVRP Applicant and
Registrar state machines on this port. A transition Registrar state machines on this port. A transition
from disabled(2) to enabled(1) will cause a reset of all from disabled(2) to enabled(1) will cause a reset of all
GVRP state machines on this port and zeroing of all GVRP state machines on this port."
related counters."
DEFVAL { enabled } DEFVAL { enabled }
::= { dot1qPortVlanEntry 4 } ::= { dot1qPortVlanEntry 4 }
dot1qPortGvrpFailedRegistrations OBJECT-TYPE dot1qPortGvrpFailedRegistrations OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of failed GVRP registrations, for any "The total number of failed GVRP registrations, for any
reason, on this port." reason, on this port."
skipping to change at page 75, line 12 skipping to change at page 66, line 19
VLAN (e.g. GMRP, but not GVRP or STP)." VLAN (e.g. GMRP, but not GVRP or STP)."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanStatisticsEntry 2 } ::= { dot1qPortVlanStatisticsEntry 2 }
dot1qTpVlanPortInDiscards OBJECT-TYPE dot1qTpVlanPortInDiscards OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames received by this port which were "The number of valid frames received by this port from
discarded due to VLAN related reasons. Examples of such its segment which were classified as belonging to this
reasons are VLAN ingress filtering, VLAN egress filtering, VLAN which were discarded due to VLAN related reasons.
and Acceptable Frame Type." Specifically, the IEEE 802.1Q counters for Discard
Inbound and Discard on Ingress Filtering."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3" "IEEE 802.1Q/D11 Section 12.6.1.1.3"
::= { dot1qPortVlanStatisticsEntry 3 } ::= { dot1qPortVlanStatisticsEntry 3 }
dot1qPortVlanHCStatisticsTable OBJECT-TYPE dot1qPortVlanHCStatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing per port, per VLAN statistics for "A table containing per port, per VLAN statistics for
skipping to change at page 76, line 41 skipping to change at page 67, line 48
VLAN (e.g. GMRP, but not GVRP or STP)." VLAN (e.g. GMRP, but not GVRP or STP)."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)"
::= { dot1qPortVlanHCStatisticsEntry 2 } ::= { dot1qPortVlanHCStatisticsEntry 2 }
dot1qTpVlanPortHCInDiscards OBJECT-TYPE dot1qTpVlanPortHCInDiscards OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames received by this port which were "The number of valid frames received by this port from
discarded due to VLAN related reasons. Examples of such its segment which were classified as belonging to this
reasons are VLAN ingress filtering, VLAN egress filtering, VLAN which were discarded due to VLAN related reasons.
and Acceptable Frame Type." Specifically, the IEEE 802.1Q counters for Discard
Inbound and Discard on Ingress Filtering."
REFERENCE REFERENCE
"IEEE 802.1Q/D11 Section 12.6.1.1.3" "IEEE 802.1Q/D11 Section 12.6.1.1.3"
::= { dot1qPortVlanHCStatisticsEntry 3 } ::= { dot1qPortVlanHCStatisticsEntry 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- The VLAN Learning Constraints Table -- The VLAN Learning Constraints Table
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qLearningConstraintsTable OBJECT-TYPE dot1qLearningConstraintsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qLearningConstraintsEntry SYNTAX SEQUENCE OF Dot1qLearningConstraintsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing learning constraints for sets of "A table containing learning constraints for sets of
Shared and Independendent VLANs." Shared and Independendent VLANs."
skipping to change at page 78, line 18 skipping to change at page 69, line 27
"The identity of the constraint set to which "The identity of the constraint set to which
dot1qConstraintVlan belongs. These values may be chosen dot1qConstraintVlan belongs. These values may be chosen
by the management station." by the management station."
::= { dot1qLearningConstraintsEntry 2 } ::= { dot1qLearningConstraintsEntry 2 }
dot1qConstraintType OBJECT-TYPE dot1qConstraintType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
independent(1), independent(1),
shared(2) shared(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of constraint this entry defines. "The type of constraint this entry defines.
independent(1) - the VLAN, dot1qConstraintVlan, independent(1) - the VLAN, dot1qConstraintVlan,
uses an independent filtering database uses an independent filtering database from all
from all other VLANs in the same set, defined by other VLANs in the same set, defined by
dot1qConstraintSet. dot1qConstraintSet.
shared(2) - the VLAN, dot1qConstraintVlan shares the shared(2) - the VLAN, dot1qConstraintVlan, shares
same filtering database as all other VLANs in the same filtering database as all other VLANs
the same set, defined by dot1qConstraintSet." in the same set, defined by dot1qConstraintSet."
::= { dot1qLearningConstraintsEntry 3 } ::= { dot1qLearningConstraintsEntry 3 }
dot1qConstraintStatus OBJECT-TYPE dot1qConstraintStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this entry." "The status of this entry."
::= { dot1qLearningConstraintsEntry 4 } ::= { dot1qLearningConstraintsEntry 4 }
dot1qConstraintSetDefault OBJECT-TYPE dot1qConstraintSetDefault OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 81, line 18 skipping to change at page 72, line 27
unicast and multicast addresses statically configured by unicast and multicast addresses statically configured by
management, in each Filtering Database or VLAN." management, in each Filtering Database or VLAN."
::= { qBridgeGroups 5 } ::= { qBridgeGroups 5 }
qBridgeVlanGroup OBJECT-GROUP qBridgeVlanGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qVlanNumDeletes, dot1qVlanNumDeletes,
dot1qVlanFdbId, dot1qVlanFdbId,
dot1qVlanCurrentEgressPorts, dot1qVlanCurrentEgressPorts,
dot1qVlanCurrentUntaggedPorts, dot1qVlanCurrentUntaggedPorts,
dot1qVlanStatus dot1qVlanStatus,
dot1qVlanCreationTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
all VLANs currently configured on this device." all VLANs currently configured on this device."
::= { qBridgeGroups 6 } ::= { qBridgeGroups 6 }
qBridgeVlanStaticGroup OBJECT-GROUP qBridgeVlanStaticGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qVlanStaticName, dot1qVlanStaticName,
skipping to change at page 85, line 4 skipping to change at page 76, line 15
OBJECT dot1qConstraintSetDefault OBJECT dot1qConstraintSetDefault
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dot1qConstraintTypeDefault OBJECT dot1qConstraintTypeDefault
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { qBridgeCompliances 1 } ::= { qBridgeCompliances 1 }
END END
8. Acknowledgments 7. Acknowledgments
This document expands upon previous work which resulted in RFC1493. This document expands upon previous work which resulted in RFC1493.
Much of the groundwork for this document was performed by the IEEE 802.1 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 [19] and working group during the definition of the IEEE 802.1D updates [19] and
IEEE 802.1Q [20]. IEEE 802.1Q [20].
The authors wish to thank the members of the Bridge Working Group for The authors wish to thank the members of the Bridge Working Group for
their many comments and suggestions which improved this effort. their many comments and suggestions which improved this effort.
9. References 8. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998 January 1998
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990 Performance Systems International, Hughes LAN Systems, May 1990
skipping to change at page 88, line 47 skipping to change at page 79, line 14
International Organization for Standardization, International International Organization for Standardization, International
Standard 8824, December 1987. Standard 8824, December 1987.
[17] Information processing systems - Open Systems Interconnection - [17] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation One Specification of Basic Encoding Rules for Abstract Notation One
(ASN.1), International Organization for Standardization, (ASN.1), International Organization for Standardization,
International Standard 8825, December 1987. International Standard 8825, December 1987.
[18] ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges". [18] ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges".
[19] ISO/IEC Final CD 15802-3, ANSI/IEEE Std 802.1D-1998 "Information [19] "Information technology - Telecommunications and information
technology - Telecommunications and information exchange between exchange between systems - Local and metropolitan area networks -
systems - Local and metropolitan area networks - Common Common specifications - Part 3: Media Access Control (MAC) Bridges:
specifications - Part 3: Media Access Control (MAC) Bridges: Revision. This is a revision of ISO/IEC 10038: 1993, 802.1j-1992
Revision (Incorporating IEEE P802.1p: Traffic Class Expediting and and 802.6k-1992. It incorporates P802.11c, P802.1p and P802.12e."
Dynamic Multicast Filtering)", May 1998. ISO/IEC 15802-3: 1998.
[20] ANSI/IEEE Draft Standard P802.1Q/D11, "IEEE Standards for Local and [20] ANSI/IEEE Draft Standard P802.1Q/D11, "IEEE Standards for Local and
Metropolitan Area Networks: Virtual Bridged Local Area Networks", Metropolitan Area Networks: Virtual Bridged Local Area Networks",
July 1998. July 1998.
[21] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K., [21] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K.,
"Definitions of Managed Objects for Bridges", RFC 1493, cisco "Definitions of Managed Objects for Bridges", RFC 1493, cisco
Systems, Digital Equipment, Hughes LAN Systems, July 1993. Systems, Digital Equipment, Hughes LAN Systems, July 1993.
[22] McCloghrie, K., Kastenholz, F. "Evolution of the Interfaces Group [22] McCloghrie, K., Kastenholz, F. "Evolution of the Interfaces Group
skipping to change at page 90, line 5 skipping to change at page 80, line 5
[23] Decker, E., McCloghrie, K., Langille, P., Rijsinghani, A. [23] Decker, E., McCloghrie, K., Langille, P., Rijsinghani, A.
"Definitions of Managed Objects for Source Routing Bridges", RFC "Definitions of Managed Objects for Source Routing Bridges", RFC
1525, cisco Systems, Hughes LAN Systems, Digital Equipment, 1525, cisco Systems, Hughes LAN Systems, Digital Equipment,
September 1993 September 1993
[24] McCloghrie K., and M. Rose, Editors, "Management Information Base [24] McCloghrie K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets", STD 17, RFC for Network Management of TCP/IP-based internets", STD 17, RFC
1213, Hughes LAN Systems, Performance Systems International, March 1213, Hughes LAN Systems, Performance Systems International, March
1991. 1991.
10. Security Considerations 9. Security Considerations
There are a number of management objects defined in this MIB that have a There are a number of management objects defined in this MIB that have a
MAX-ACCESS clause of read-write and/or read-create. Such objects may be MAX-ACCESS clause of read-write and/or read-create. Such objects may be
considered sensitive or vulnerable in some network environments. The considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET control as to who on the secure network is allowed to access and GET/SET
skipping to change at page 91, line 5 skipping to change at page 81, line 5
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the User- as provided by the SNMPv3 framework. Specifically, the use of the User-
based Security Model RFC 2274 [12] and the View-based Access Control based Security Model RFC 2274 [12] and the View-based Access Control
Model RFC 2275 [15] is recommended. Model RFC 2275 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity It is then a customer/user responsibility to ensure that the SNMP entity
giving access to an instance of this MIB, is properly configured to give giving access to an instance of this MIB, is properly configured to give
access to the objects only to those principals (users) that have access to the objects only to those principals (users) that have
legitimate rights to indeed GET or SET (change/create/delete) them. legitimate rights to indeed GET or SET (change/create/delete) them.
11. Authors' Addresses 10. Authors' Addresses
Les Bell Les Bell
3Com Europe Limited 3Com Europe Limited
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
+44 (1442) 438025 +44 (1442) 438025
Les_Bell@3Com.com Les_Bell@3Com.com
Andrew Smith Andrew Smith
Extreme Networks Extreme Networks
10460 Bandley Drive 10460 Bandley Drive
Cupertino CA 95014 Cupertino CA 95014
USA USA
+1 (408) 342 0999 +1 (408) 342 0999
andrew@extremenetworks.com andrew@extremenetworks.com
Paul Langille Paul Langille
Acacia Networks, Inc. Newbridge Networks
650 Suffolk St. 5 Corporate Drive
Lowell, MA 01854 Andover, MA 01810
USA USA
+1 (978) 275 0662 +1 (978) 691 4665
plangille@acacianet.com langille@newbridge.com
Anil Rijhsinghani Anil Rijhsinghani
Cabletron Systems Cabletron Systems
50 Minuteman Road 50 Minuteman Road
Andover MA 01810 Andover MA 01810
USA USA
+1 (978) 684-1295 +1 (978) 684-1295
anil@cabletron.com anil@cabletron.com
Keith McCloghrie Keith McCloghrie
skipping to change at page 92, line 38 skipping to change at page 82, line 38
3.4.2 Relation to Interfaces MIB .................................. 14 3.4.2 Relation to Interfaces MIB .................................. 14
3.4.2.1 Layering Model ............................................ 15 3.4.2.1 Layering Model ............................................ 15
3.4.2.2 ifStackTable .............................................. 15 3.4.2.2 ifStackTable .............................................. 15
3.4.2.3 ifRcvAddressTable ......................................... 15 3.4.2.3 ifRcvAddressTable ......................................... 15
3.4.3 Relation to Basic Bridge MIB ................................ 16 3.4.3 Relation to Basic Bridge MIB ................................ 16
3.4.3.1 The dot1dBase Group ....................................... 16 3.4.3.1 The dot1dBase Group ....................................... 16
3.4.3.2 The dot1dStp Group ........................................ 16 3.4.3.2 The dot1dStp Group ........................................ 16
3.4.3.3 The dot1dTp Group ......................................... 16 3.4.3.3 The dot1dTp Group ......................................... 16
3.4.3.4 The dot1dStatic Group ..................................... 17 3.4.3.4 The dot1dStatic Group ..................................... 17
4 Extensions to RFC 1493 .......................................... 18 4 Extensions to RFC 1493 .......................................... 18
5 Change Log and Editorial Stuff .................................. 18 5 Definitions for Extended Bridge MIB ............................. 19
5.1 Changes since draft-ietf-bridge-bridgemib-02.txt .............. 18 6 Definitions for Virtual Bridge MIB .............................. 38
5.2 Open Issues ................................................... 18 7 Acknowledgments ................................................. 77
5.3 Issues closed in this draft ................................... 19 8 References ...................................................... 77
5.4 Issues closed in previous drafts .............................. 19 9 Security Considerations ......................................... 80
6 Definitions for Extended Bridge MIB ............................. 27 10 Authors' Addresses ............................................. 81
7 Definitions for Virtual Bridge MIB .............................. 47 Copyright (C) The Internet Society (1999). All Rights Reserved.
8 Acknowledgments ................................................. 86
9 References ...................................................... 87
10 Security Considerations ........................................ 90
11 Authors' Addresses ............................................. 91
Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise to others, and derivative works that comment on or otherwise
explain it or assist in its implmentation may be prepared, copied, explain it or assist in its implmentation may be prepared, copied,
published and distributed, in whole or in part, without published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed Internet Society or other Internet organizations, except as needed
 End of changes. 

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