idnits 2.17.1 draft-ietf-bridge-bridgemib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 90 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 15 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([V2SMI]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 30 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 486 has weird spacing: '...address coun...' == Line 490 has weird spacing: '...failure not...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 1999) is 9075 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'USM' is mentioned on line 3606, but not defined == Missing Reference: 'VACM' is mentioned on line 3607, but not defined == Unused Reference: 'V3INTRO' is defined on line 3666, but no explicit reference was found in the text == Unused Reference: 'ASN1' is defined on line 3690, but no explicit reference was found in the text == Unused Reference: 'ASN1BER' is defined on line 3696, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. 'ARCH') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'V1PROTO') ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'V1TRAPS') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'V2COMMUNITY') ** Obsolete normative reference: RFC 1906 (ref. 'V2TRANS') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1905 (ref. 'V2PROTO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2570 (ref. 'V3INTRO') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2572 (ref. 'V3MPC') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. 'V3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2573 (ref. 'V3APPS') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. 'V3VACM') (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1BER' ** Obsolete normative reference: RFC 1493 (ref. 'BRIDGEMIB') (Obsoleted by RFC 4188) ** Obsolete normative reference: RFC 1573 (ref. 'INTERFACEMIB') (Obsoleted by RFC 2233) ** Downref: Normative reference to an Historic RFC: RFC 1525 (ref. 'SRBRIDGEMIB') Summary: 22 errors (**), 0 flaws (~~), 11 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft E.L. Bell 2 Expires December 1999 3Com Corp. 3 draft-ietf-bridge-bridgemib-06.txt A. Smith 4 Standards Track Extreme Networks 5 P. Langille 6 Newbridge Networks 7 A. Rijhsinghani 8 Cabletron Systems 9 K. McCloghrie 10 cisco Systems 11 June 1999 13 Definitions of Managed Objects for Bridges with Traffic 14 Classes, Multicast Filtering and Virtual LAN Extensions 16 Status of this Memo 18 This document is an Internet Draft and is in full conformance with all 19 provisions of Section 10 of RFC2026. Internet Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its Areas, and 21 its Working Groups. Note that other groups may also distribute working 22 documents as Internet Drafts. 24 Internet Drafts are draft documents valid for a maximum of six months. 25 Internet Drafts may be updated, replaced, or obsoleted by other 26 documents at any time. It is not appropriate to use Internet Drafts as 27 reference material or to cite them other than as a "working draft" or 28 "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 To learn the current status of any Internet-Draft, please check the 37 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 38 Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe), 39 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 41 This document is a product of the IETF's Bridge MIB Working Group. 42 Copyright (C) The Internet Society (1999). All Rights Reserved. 44 Abstract 46 This memo defines a portion of the Management Information Base (MIB) for 47 use with network management protocols in TCP/IP based internets. In 48 particular it defines objects for managing MAC bridges based on the IEEE 49 802.1D-1998 MAC Bridges and IEEE 802.1Q-1998 Virtual LAN (VLAN) 50 standards for bridging between Local Area Network (LAN) segments. 52 Provisions are made for support of transparent bridging. Provisions are 53 also made so that these objects apply to bridges connected by 54 subnetworks other than LAN segments. This memo also includes several 55 MIB modules in a manner that is compliant to the SMIv2 [V2SMI]. 57 1. The SNMP Management Framework 59 The SNMP Management Framework presently consists of five major 60 components: 62 o An overall architecture, described in an Architecture for 63 Describing SNMP Management Frameworks [ARCH]. 65 o Mechanisms for describing and naming objects and events for the 66 purpose of management. The first version of this Structure of 67 Management Information (SMI) is called SMIv1 and described in 68 RFC 1155 [V1SMI], RFC 1212 [V1CONCISE] and RFC 1215 [V1TRAPS]. 69 The second version, called SMIv2, is described in STD 58, RFC 70 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58, RFC 2580 71 [V2CONFORM]. 73 o Message protocols for transferring management information. The 74 first version of the SNMP message protocol is called SNMPv1 and 75 described in RFC 1157 [V1PROTO]. A second version of the SNMP 76 message protocol, which is not an Internet standards track 77 protocol, is called SNMPv2c and described in RFC 1901 78 [V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the 79 message protocol is called SNMPv3 and described in RFC 1906 80 [V2TRANS], Message Processing and Dispatching [V3MPC] and User- 81 based Security Model [V3USM]. 83 o Protocol operations for accessing management information. The 84 first set of protocol operations and associated PDU formats is 85 described in RFC 1157 [V1PROTO]. A second set of protocol 86 operations and associated PDU formats is described in RFC 1905 87 [V2PROTO]. 89 o A set of fundamental applications described in SNMPv3 90 Applications [V3APPS] and the view-based access control 91 mechanism described in View-based Access Control Model [V3VACM]. 93 Managed objects are accessed via a virtual information store, termed the 94 Management Information Base or MIB. Objects in the MIB are defined 95 using the mechanisms defined in the SMI. 97 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 98 conforming to the SMIv1 can be produced through the appropriate 99 translations. The resulting translated MIB must be semantically 100 equivalent, except where objects or events are omitted because no 101 translation is possible (use of Counter64). Some machine readable 102 information in SMIv2 will be converted into textual descriptions in 103 SMIv1 during the translation process. However, this loss of machine 104 readable information is not considered to change the semantics of the 105 MIB. 107 2. Overview 109 A common device present in many networks is the Bridge. This device is 110 used to connect Local Area Network segments below the network layer. 111 These devices are often known as 'layer 2 switches'. 113 There are two major modes defined for this bridging: Source-Route and 114 transparent. Source-Route bridging is described by IEEE 802.5 [802.5]. 115 and is not discussed further in this document. 117 The transparent method of bridging is defined by IEEE 802.1D-1998 118 [802.1D] which is an update to the original IEEE 802.1D specification 119 [802.1D-ORIG]. Managed objects for that original specification of 120 transparent bridging were defined in RFC 1493 [BRIDGEMIB]. 122 The original IEEE 802.1D is augmented by IEEE 802.1Q-1998 [802.1Q] to 123 provide support for 'virtual bridged LANs' where a single bridged 124 physical LAN network may be used to support multiple logical bridged 125 LANs, each of which offers a service approximately the same as that 126 defined by IEEE 802.1D. Such virtual LANs (VLANs) are an integral 127 feature of switched LAN networks. A VLAN can be viewed as a group of 128 end-stations on multiple LAN segments and can communicate as if they 129 were on a single LAN. IEEE 802.1Q defines port-based Virtual LANs where 130 membership is determined by the bridge port on which data frames are 131 received. This memo defines the objects needed for the management of 132 port-based VLANs in bridge entities. 134 This memo defines those objects needed for the management of a bridging 135 entity operating in the transparent mode, as well as some objects 136 applicable to all types of bridges. Managed objects for Source-Route 137 bridging are defined in RFC 1525 [SRBRIDGEMIB]. 139 2.1. Scope 141 This MIB includes a comprehensive set of managed objects which attempts 142 to match the set defined in IEEE 802.1D and IEEE 802.1Q. However, to be 143 consistent with the spirit of the SNMP Framework, a subjective judgement 144 was made to omit the objects from those standards most 'costly' to 145 implement in an agent and least 'essential' for fault and configuration 146 management. The omissions are described in section 3 below. 148 Historical note: 150 The original bridge MIB [BRIDGEMIB] used the following principles for 151 determining inclusion of an object in the BRIDGE-MIB module: 153 (1) Start with a small set of essential objects and add only as 154 further objects are needed. 156 (2) Require objects be essential for either fault or configuration 157 management. 159 (3) Consider evidence of current use and/or utility. 161 (4) Limit the total of objects. 163 (5) Exclude objects which are simply derivable from others in this or 164 other MIBs. 166 (6) Avoid causing critical sections to be heavily instrumented. The 167 guideline that was followed is one counter per critical section 168 per layer. 170 3. Structure of MIBs 172 This document defines additional objects, on top of those existing in 173 the original BRIDGE-MIB module defined in [BRIDGEMIB]: that MIB module 174 is to be maintained unchanged for backwards compatibility. Section 175 3.4.3 of the present document contains some recommendations regarding 176 usage of objects in the original bridge MIB by devices implementing the 177 enhancements defined here. 179 Two MIB modules are defined here: 181 (1) Managed objects for an extended bridge MIB module P-BRIDGE-MIB 182 for the traffic class and multicast filtering enhancements 183 defined by IEEE 802.1D-1998 [802.1D]. 185 (2) Managed objects for a virtual bridge MIB module Q-BRIDGE-MIB for 186 the Virtual LAN bridging enhancements defined by IEEE 802.1Q-1998 187 [802.1Q]. 189 3.1. Structure of Extended Bridge MIB module 191 Objects in this MIB are arranged into groups. Each group is organized 192 as a set of related objects. The overall structure and assignment of 193 objects to their groups is shown below. 195 3.1.1. Relationship to IEEE 802.1D-1998 Manageable Objects 197 This section contains a cross-reference to the objects defined in IEEE 198 802.1D-1998 [802.1D]. It also details those objects that are not 199 considered necessary in this MIB module. 201 Some objects defined by IEEE 802.1D-1998 have been included in the 202 virtual bridge MIB module rather than this one: entries in 203 dot1qTpGroupTable, dot1qForwardAllTable and 204 dot1qForwardUnregisteredTable are required for virtual bridged LANs with 205 additional indexing (e.g. per-VLAN, per-FDB) and so are not defined 206 here. Instead, devices which do not implement virtual bridged LANs but 207 do implement the Extended Forwarding Services defined by IEEE 802.1D 208 (i.e. dynamic learning of multicast group addresses and group service 209 requirements in the filtering database) should implement these tables 210 with a fixed value for dot1qFdbId (the value 1 is recommended) or 211 dot1qVlanIndex (the value 1 is recommended). Devices which support 212 Extended Filtering Services should support dot1qTpGroupTable, 213 dot1qForwardAllTable and dot1qForwardUnregisteredTable. 215 Extended Bridge MIB Name IEEE 802.1D-1998 Name 217 dot1dExtended Bridge 218 dot1dExtBase 219 dot1dDeviceCapabilities 220 dot1dExtendedFilteringServices 221 dot1dTrafficClasses 222 dot1dTrafficClassesEnabled 223 dot1dGmrpStatus .ApplicantAdministrativeControl 224 dot1dPriority 225 dot1dPortPriorityTable 226 dot1dPortDefaultUserPriority .UserPriority 227 dot1dPortNumTrafficClasses 228 dot1dUserPriorityRegenTable .UserPriorityRegenerationTable 229 dot1dUserPriority 230 dot1dRegenUserPriority 231 dot1dTrafficClassTable .TrafficClassTable 232 dot1dTrafficClassPriority 233 dot1dTrafficClass 234 dot1dPortOutboundAccessPriorityTable 235 .OutboundAccessPriorityTable 236 dot1dPortOutboundAccessPriority 237 dot1dGarp 238 dot1dPortGarpTable 239 dot1dPortGarpJoinTime .JoinTime 240 dot1dPortGarpLeaveTime .LeaveTime 241 dot1dPortGarpLeaveAllTime .LeaveAllTime 242 dot1dGmrp 243 dot1dPortGmrpTable 244 dot1dPortGmrpStatus .ApplicantAdministrativeControl 245 dot1dPortGmrpFailedRegistrations 246 .FailedRegistrations 247 dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU 248 dot1dTpGroup 249 dot1dTpHCPortTable 250 dot1dTpHCPortInFrames .BridgePort.FramesReceived 251 dot1dTpHCPortOutFrames .ForwardOutBound 252 dot1dTpHCPortInDiscards .DiscardInbound 253 dot1dTpPortOverflowTable 254 dot1dTpPortInOverflowFrames .BridgePort.FramesReceived 255 dot1dTpPortOutOverflowFrames .ForwardOutBound 256 dot1dTpPortInOverflowDiscards .DiscardInbound 258 The following IEEE 802.1D-1998 management objects have not been included 259 in the Bridge MIB for the indicated reasons. 261 IEEE 802.1D-1998 Object Disposition 263 Bridge.StateValue not considered useful 264 Bridge.ApplicantAdministrativeControl 265 not provided per-attribute 266 (e.g. per-VLAN, per-Group). 267 Only per-{device,port,application} 268 control is provided in this MIB. 270 3.1.2. Relationship to IEEE 802.1Q Manageable Objects 272 This section contains section number cross-references to manageable 273 objects defined in IEEE 802.1Q-1998 [802.1Q]. These objects have been 274 included in this MIB as they provide a natural fit with the IEEE 802.1D 275 objects with which they are co-located. 277 Extended Bridge MIB Name IEEE 802.1Q-1998 Section and Name 279 dot1dExtended Bridge 280 dot1dExtBase 281 dot1dDeviceCapabilities 282 dot1qStaticEntryIndividualPort 5.2 implementation options 283 dot1qIVLCapable 284 dot1qSVLCapable 285 dot1qHybridCapable 286 dot1qConfigurablePvidTagging 12.10.1.1 read bridge vlan 287 config 288 dot1dPortCapabilitiesTable 289 dot1dPortCapabilities 290 dot1qDot1qTagging 5.2 implementation options 291 dot1qConfigurableAcceptableFrameTypes 292 5.2 implementation options 293 dot1qIngressFiltering 5.2 implementation options 295 3.1.3. The dot1dExtBase Group 297 This group contains the objects which are applicable to all bridges 298 implementing the traffic class and multicast filtering features of IEEE 299 802.1D-1998 [802.1D]. It includes per-device configuration of GARP and 300 GMRP protocols. This group will be implemented by all devices which 301 implement the extensions defined in 802.1D-1998. 303 3.1.4. The dot1dPriority Group 305 This group contains the objects for configuring and reporting status of 306 priority-based queuing mechanisms in a bridge. This includes per- port 307 user_priority treatment, mapping of user_priority in frames into 308 internal traffic classes and outbound user_priority and access_priority. 310 3.1.5. The dot1dGarp Group 312 This group contains the objects for configuring and reporting on 313 operation of the Generic Attribute Registration Protocol (GARP). 315 3.1.6. The dot1dGmrp Group 317 This group contains the objects for configuring and reporting on 318 operation of the GARP Multicast Registration Protocol (GMRP). 320 3.1.7. The dot1dTpHCPortTable 322 This table extends the dot1dTp group from the original bridge MIB 323 [BRIDGEMIB] and contains the objects for reporting port bridging 324 statistics for high capacity network interfaces. 326 3.1.8. The dot1dTpPortOverflowTable 328 This table extends the dot1dTp group from the original bridge MIB 329 [BRIDGEMIB] and contains the objects for reporting the upper bits of 330 port bridging statistics for high capacity network interfaces for when 331 32-bit counters are inadequate. 333 3.2. Structure of Virtual Bridge MIB module 335 Objects in this MIB are arranged into groups. Each group is organized 336 as a set of related objects. The overall structure and assignment of 337 objects to their groups is shown below. Some manageable objects defined 338 in the original bridge MIB [BRIDGEMIB] need to be indexed differently 339 when they are used in a VLAN bridging environment: these objects are, 340 therefore, effectively duplicated by new objects with different indexing 341 which are defined in the Virtual Bridge MIB. 343 3.2.1. Relationship to IEEE 802.1Q Manageable Objects 345 This section contains section-number cross-references to manageable 346 objects defined in clause 12 of IEEE 802.1Q-1998 [802.1Q]. It also 347 details those objects that are not considered necessary in this MIB 348 module. 350 Note: unlike IEEE 802.1D-1998, IEEE 802.1Q-1998 [802.1Q] did not define 351 exact syntax for a set of managed objects: the following cross- 352 references indicate the section numbering of the descriptions of 353 management operations from clause 12 in the latter document. 355 Virtual Bridge MIB object IEEE 802.1Q-1998 Reference 357 dot1qBase 358 dot1qVlanVersionNumber 12.10.1.1 read bridge vlan config 359 dot1qMaxVlanId 12.10.1.1 read bridge vlan config 360 dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan config 361 dot1qNumVlans 362 dot1dGvrpStatus 12.9.2.1/2 read/set garp 363 applicant controls 364 dot1qTp 365 dot1qFdbTable 366 dot1qFdbId 367 dot1qFdbDynamicCount 12.7.1.1.3 read filtering d/base 368 dot1qTpFdbTable 369 dot1qTpFdbAddress 370 dot1qTpFdbPort 371 dot1qTpFdbStatus 372 dot1qTpGroupTable 12.7.7.1 read filtering entry 373 dot1qTpGroupAddress 374 dot1qTpGroupEgressPorts 375 dot1qTpGroupLearnt 376 dot1qForwardAllTable 12.7.7.1 read filtering entry 377 dot1qForwardAllPorts 378 dot1qForwardAllStaticPorts 379 dot1qForwardAllForbiddenPorts 380 dot1qForwardUnregisteredTable 12.7.7.1 read filtering entry 381 dot1qForwardUnregisteredPorts 382 dot1qForwardUnregisteredStaticPorts 383 dot1qForwardUnregisteredForbiddenPorts 384 dot1qStatic 385 dot1qStaticUnicastTable 12.7.7.1 create/delete/read 386 filtering entry 387 12.7.6.1 read permanent database 388 dot1qStaticUnicastAddress 389 dot1qStaticUnicastReceivePort 390 dot1qStaticUnicastAllowedToGoTo 391 dot1qStaticUnicastStatus 392 dot1qStaticMulticastTable 12.7.7.1 create/delete/read 393 filtering entry 394 12.7.6.1 read permanent database 395 dot1qStaticMulticastAddress 396 dot1qStaticMulticastReceivePort 397 dot1qStaticMulticastStaticEgressPorts 398 dot1qStaticMulticastForbiddenEgressPorts 399 dot1qStaticMulticastStatus 401 dot1qVlan 402 dot1qVlanNumDeletes 403 dot1qVlanCurrentTable 12.10.2.1 read vlan configuration 404 12.10.3.5 read VID to FID 405 allocations 406 12.10.3.6 read FID allocated to VID 407 12.10.3.7 read VIDs allocated to 408 FID 409 dot1qVlanTimeMark 410 dot1qVlanIndex 411 dot1qVlanFdbId 412 dot1qVlanCurrentEgressPorts 413 dot1qVlanCurrentUntaggedPorts 414 dot1qVlanStatus 415 dot1qVlanCreationTime 416 dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read 417 filtering entry 418 12.7.6.1 read permanent database 419 12.10.2.2 create vlan config 420 12.10.2.3 delete vlan config 421 dot1qVlanStaticName 12.4.1.3 set bridge name 422 dot1qVlanStaticEgressPorts 423 dot1qVlanForbiddenEgressPorts 424 dot1qVlanStaticUntaggedPorts 425 dot1qVlanStaticRowStatus 426 dot1qPortVlanConfigTable 12.10.1.1 read bridge vlan 427 configuration 428 dot1qPvid 12.10.1.2 configure PVID values 429 dot1qPortAcceptableFrameTypes 12.10.1.3 configure acceptable 430 frame types parameter 431 dot1qPortIngressFiltering 12.10.1.4 configure ingress 432 filtering parameters 433 dot1qPortGvrpStatus 12.9.2.2 read/set garp applicant 434 controls 435 dot1qPortGvrpFailedRegistrations 436 dot1qPortGvrpLastPduOrigin 437 dot1qPortVlanStatisticsTable 12.6.1.1 read forwarding port 438 counters 439 dot1qTpVlanPortInFrames 440 dot1qTpVlanPortOutFrames 441 dot1qTpVlanPortInDiscards 442 dot1qTpVlanPortInOverflowFrames 443 dot1qTpVlanPortOutOverflowFrames 444 dot1qTpVlanPortInOverflowDiscards 445 dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port 446 counters 447 dot1qTpVlanPortHCInFrames 448 dot1qTpVlanPortHCOutFrames 449 dot1qTpVlanPortHCInDiscards 450 dot1qLearningConstraintsTable 12.10.3.1/3/4 read/set/delete 451 vlan learning constraints 452 12.10.3.2 read vlan learning 453 constraints for VID 454 dot1qConstraintVlan 455 dot1qConstraintSet 456 dot1qConstraintType 457 dot1qConstraintStatus 458 dot1qConstraintSetDefault 459 dot1qConstraintTypeDefault 461 The following IEEE 802.1Q management objects have not been included in 462 the Bridge MIB for the indicated reasons. 464 IEEE 802.1Q-1998 Operation Disposition 466 reset bridge (12.4.1.4) not considered useful 468 reset vlan bridge (12.10.1.5) not considered useful 470 read forwarding port counters (12.6.1.1) 471 discard on error details not considered useful 473 read permanent database (12.7.6.1) 474 permanent database size not considered useful 475 number of static filtering count rows in 476 entries dot1qStaticUnicastTable + 477 dot1qStaticMulticastTable 478 number of static VLAN count rows in 479 registration entries dot1qVlanStaticTable 481 read filtering entry range use GetNext operation. 482 (12.7.7.4) 484 read filtering database (12.7.1.1) 485 filtering database size not considered useful 486 number of dynamic group address count rows applicable to each 487 entries (12.7.1.3) FDB in dot1dTpGroupTable 489 read garp state (12.9.3.1) not considered useful 490 notify vlan registration failure not considered useful 491 (12.10.1.6) 493 notify learning constraint violation 494 (12.10.3.10) not considered useful 496 3.2.2. The dot1qBase Group 498 This mandatory group contains the objects which are applicable to all 499 bridges implementing IEEE 802.1Q virtual LANs. 501 3.2.3. The dot1qTp Group 503 This group contains objects that control the operation and report the 504 status of transparent bridging. This includes management of the dynamic 505 Filtering Databases for both unicast and multicast forwarding. This 506 group will be implemented by all bridges that perform destination- 507 address filtering. 509 3.2.4. The dot1qStatic Group 511 This group contains objects that control static configuration 512 information for transparent bridging. This includes management of the 513 static entries in the Filtering Databases for both unicast and multicast 514 forwarding. 516 3.2.5. The dot1qVlan Group 518 This group contains objects that control configuration and report status 519 of the Virtual LANs known to a bridge. This includes management of the 520 statically configured VLANs as well as reporting VLANs discovered by 521 other means e.g. GVRP. It also controls configuration and reports 522 status of per-port objects relating to VLANs and reports traffic 523 statistics. It also provides for management of the VLAN Learning 524 Constraints. 526 3.3. Textual Conventions 528 The datatypes MacAddress, BridgeId, Timeout, EnabledStatus, PortList, 529 VlanIndex and VlanId are used as textual conventions in this document. 530 These textual conventions have NO effect on either the syntax nor the 531 semantics of any managed object. Objects defined using these 532 conventions are always encoded by means of the rules that define their 533 primitive type. Hence, no changes to the SMI or the SNMP are necessary 534 to accommodate these textual conventions which are adopted merely for 535 the convenience of readers. 537 3.4. Relationship to Other MIBs 539 As described above, some IEEE 802.1D management objects have not been 540 included in this MIB because they overlap with objects in other MIBs 541 applicable to a bridge implementing this MIB. In particular, it is 542 assumed that a bridge implementing this MIB will also implement (at 543 least) the 'system' group defined in MIB-II [MIB2], the 'interfaces' 544 group defined in [INTERFACEMIB] and the original bridge MIB [BRIDGEMIB]. 546 3.4.1. Relationship to the 'system' group 548 In MIB-II, the 'system' group is defined as being mandatory for all 549 systems such that each managed entity contains one instance of each 550 object in the 'system' group. Thus, those objects apply to the entity 551 as a whole irrespective of whether the entity's sole functionality is 552 bridging, or whether bridging is only a subset of the entity's 553 functionality. 555 3.4.2. Relation to Interfaces MIB 557 The Interface MIB Evolution [INTERFACEMIB], requires that any MIB which 558 is an adjunct of the Interface MIB, clarify specific areas within the 559 Interface MIB. These areas were intentionally left vague in the 560 Interface MIB Evolution to avoid over-constraining the MIB, thereby 561 precluding management of certain media-types. 563 Section 3.3 of Interface MIB Evolution enumerates several areas which a 564 media-specific MIB must clarify. Each of these areas is addressed in a 565 following subsection. The implementor is referred to Interface MIB 566 Evolution in order to understand the general intent of these areas. 568 In Interface MIB Evolution, the 'interfaces' group is defined as being 569 mandatory for all systems and contains information on an entity's 570 interfaces, where each interface is thought of as being attached to a 571 `subnetwork'. (Note that this term is not to be confused with `subnet' 572 which refers to an addressing partitioning scheme used in the Internet 573 suite of protocols.) The term 'segment' is used in this memo to refer 574 to such a subnetwork, whether it be an Ethernet segment, a 'ring', a WAN 575 link, or even an X.25 virtual circuit. 577 Implicit in this Extended Bridge MIB is the notion of ports on a bridge. 578 Each of these ports is associated with one interface of the 'interfaces' 579 group (one row in ifTable) and, in most situations, each port is 580 associated with a different interface. However, there are situations in 581 which multiple ports are associated with the same interface. An example 582 of such a situation would be several ports each corresponding one-to-one 583 with several X.25 virtual circuits but all on the same interface. 585 Each port is uniquely identified by a port number. A port number has no 586 mandatory relationship to an interface number, but in the simple case a 587 port number will have the same value as the corresponding interface's 588 interface number. Port numbers are in the range (1..dot1dBaseNumPorts). 590 Some entities perform other functionality as well as bridging through 591 the sending and receiving of data on their interfaces. In such 592 situations, only a subset of the data sent/received on an interface is 593 within the domain of the entity's bridging functionality. This subset 594 is considered to be delineated according to a set of protocols, with 595 some protocols being bridged, and other protocols not being bridged. 596 For example, in an entity which exclusively performed bridging, all 597 protocols would be considered as being bridged, whereas in an entity 598 which performed IP routing on IP datagrams and only bridged other 599 protocols, only the non-IP data would be considered as being bridged. 600 Thus, this Extended Bridge MIB (and in particular, its counters) is 601 applicable only to that subset of the data on an entity's interfaces 602 which is sent/received for a protocol being bridged. All such data is 603 sent/received via the ports of the bridge. 605 3.4.2.1. Layering Model 607 This memo assumes the interpretation of the Interfaces Group to be in 608 accordance with Interface MIB Evolution [INTERFACEMIB] which states that 609 the interfaces table (ifTable) contains information on the managed 610 resource's interfaces and that each sub-layer below the internetwork 611 layer of a network interface is considered an interface. 613 This document recommends that, within an entity, VLANs which are 614 instantiated as an entry in dot1qVlanCurrentTable by either management 615 configuration through dot1qVlanStaticTable or by dynamic means (e.g. 616 through GVRP), are NOT also represented by an entry in ifTable. 618 Where an entity contains higher-layer protocol entities e.g. IP-layer 619 interfaces that transmit and receive traffic to/from a VLAN, these 620 should be represented in the ifTable as interfaces of type 621 propVirtual(53). Protocol-specific types such as l3ipxvlan(137) should 622 not be used here since there is no implication that the bridge will 623 perform any protocol filtering before delivering up to these virtual 624 interfaces. 626 3.4.2.2. ifStackTable 628 In addition, Interface MIB Evolution [INTERFACEMIB] defines a table 629 'ifStackTable' for describing the relationship between logical 630 interfaces within an entity. It is anticipated that implementors will 631 use this table to describe the binding of e.g. IP interfaces to physical 632 ports, although the presence of VLANs makes the representation less than 633 perfect for showing connectivity: the ifStackTable cannot represent the 634 full capability of the IEEE 802.1Q VLAN bridging standard since that 635 makes a distinction between VLAN bindings on 'ingress' to and 'egress' 636 from a port: these relationships may or may not be symmetrical whereas 637 Interface MIB Evolution assumes a symmetrical binding for transmit and 638 receive. This makes it necessary to define other manageable objects for 639 configuring which ports are members of which VLANs. 641 3.4.2.3. ifRcvAddressTable 643 This table contains all MAC addresses, unicast, multicast, and 644 broadcast, for which an interface will receive packets and forward them 645 up to a higher layer entity for local consumption. Note that this does 646 not include addresses for data-link layer control protocols such as 647 Spanning-Tree, GMRP or GVRP. The format of the address, contained in 648 ifRcvAddressAddress, is the same as for ifPhysAddress. 650 This table does not include unicast or multicast addresses which are 651 accepted for possible forwarding out some other port. This table is 652 explicitly not intended to provide a bridge address filtering mechanism. 654 3.4.3. Relation to Original Bridge MIB 656 This section defines how objects in the original bridge MIB module 657 [BRIDGEMIB] should be represented for devices which implement the 658 extensions: some of the old objects are less useful in such devices but 659 must still be implemented for reasons of backwards compatibility. Note 660 that formal conformance statements for that MIB module do not exist 661 since it is defined in SMIv1. 663 3.4.3.1. The dot1dBase Group 665 This mandatory group contains the objects which are applicable to all 666 types of bridges. Interpretation of this group is unchanged. 668 3.4.3.2. The dot1dStp Group 670 This group contains the objects that denote the bridge's state with 671 respect to the Spanning Tree Protocol. Interpretation of this group is 672 unchanged. 674 3.4.3.3. The dot1dTp Group 676 This group contains objects that describe the entity's state with 677 respect to transparent bridging. 679 In a device operating with a single Filtering Database, interpretation 680 of this group is unchanged. 682 In a device supporting multiple Filtering Databases, this group is 683 interpreted as follows: 685 dot1dTpLearnedEntryDiscards 686 The number of times that *any* of the FDBs became full. 688 dot1dTpAgingTime 689 This applies to all Filtering Databases. 691 dot1dTpFdbTable 692 Report MAC addresses learned on each port, regardless of which 693 Filtering Database they have been learnt in. If an address has 694 been learnt in multiple databases on a single port, report it only 695 once. If an address has been learnt in multiple databases on more 696 than one port, report the entry on any one of the valid ports. 698 dot1dTpPortTable 699 This table is port-based and is not affected by multiple Filtering 700 Databases or multiple VLANs. The counters should include frames 701 received or transmitted for all VLANs. Note that equivalent 64-bit 702 port statistics counters, as well as other objects to represent the 703 upper 32 bits of these counters, are defined in this document for 704 high capacity network interfaces. These have conformance statements 705 to indicate for which speeds of interface they are required. 707 3.4.3.4. The dot1dStatic Group 709 This optional group contains objects that describe the configuration of 710 destination-address filtering. 712 In a device operating with a single Filtering Database, interpretation 713 of this group is unchanged. 715 In a device supporting multiple Filtering Databases, this group is 716 interpreted as follows: 718 dot1dStaticTable 719 Entries read from this table include all static entries from all of 720 the Filtering Databases. Entries for the same MAC address and 721 receive port in more than one Filtering Database must appear only 722 once since these are the indices of this table. This table should 723 be implemented as read-only in devices that support multiple 724 Forwarding Databases - instead, write access should be provided 725 through dot1qStaticUnicastTable and dot1qStaticMulticastTable, as 726 defined in this document. 728 3.4.3.5. Additions to the Original Bridge MIB 730 In addition to the objects in the original bridge MIB [BRIDGEMIB], this 731 document contains: 733 (1) support for multiple traffic classes and dynamic multicast 734 filtering as per IEEE 802.1D-1998 [802.1D]. 736 (2) support for bridged Virtual LANs as per IEEE 802.1Q-1998 737 [802.1Q]. 739 (3) support for 64-bit versions of original bridge MIB [BRIDGEMIB] 740 port counters. 742 4. Definitions for Extended Bridge MIB 744 P-BRIDGE-MIB DEFINITIONS ::= BEGIN 746 -- ------------------------------------------------------------- 747 -- MIB for IEEE 802.1p devices 748 -- ------------------------------------------------------------- 750 IMPORTS 751 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64 752 FROM SNMPv2-SMI 753 TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION 754 FROM SNMPv2-TC 755 MODULE-COMPLIANCE, OBJECT-GROUP 756 FROM SNMPv2-CONF 757 dot1dTp, dot1dTpPort, dot1dBridge, 758 dot1dBasePortEntry, dot1dBasePort 759 FROM BRIDGE-MIB; 761 pBridgeMIB MODULE-IDENTITY 762 LAST-UPDATED "9906150000Z" 763 ORGANIZATION "IETF Bridge MIB Working Group" 764 CONTACT-INFO 765 " Les Bell 766 Postal: 3Com Europe Ltd. 767 3Com Centre, Boundary Way 768 Hemel Hempstead, Herts. HP2 7YU 769 UK 770 Phone: +44 1442 438025 771 Email: Les_Bell@3Com.com 773 Andrew Smith 774 Postal: Extreme Networks 775 3585 Monroe St. 776 Santa Clara CA 95051 777 USA 778 Phone: +1 408 579 2821 779 Email: andrew@extremenetworks.com 781 Paul Langille 782 Postal: Newbridge Networks 783 5 Corporate Drive 784 Andover, MA 01810 785 USA 787 Phone: +1 978 691 4665 788 Email: langille@newbridge.com 790 Anil Rijhsinghani 791 Postal: Cabletron Systems 792 50 Minuteman Road 793 Andover, MA 01810 794 USA 795 Phone: +1 978 684 1295 796 Email: anil@cabletron.com 798 Keith McCloghrie 799 Postal: cisco Systems, Inc. 800 170 West Tasman Drive 801 San Jose, CA 95134-1706 802 USA 803 Phone: +1 408 526 5260 804 Email: kzm@cisco.com" 806 DESCRIPTION 807 "The Bridge MIB Extension module for managing Priority 808 and Multicast Filtering, defined by IEEE 802.1D-1998." 810 -- revision history 812 REVISION "9906150000Z" 813 DESCRIPTION 814 "Initial version, published as RFC xxxx." 816 ::= { dot1dBridge 6 } 818 pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 } 820 -- ------------------------------------------------------------- 821 -- Textual Conventions 822 -- ------------------------------------------------------------- 824 EnabledStatus ::= TEXTUAL-CONVENTION 825 STATUS current 826 DESCRIPTION 827 "A simple status value for the object." 828 SYNTAX INTEGER { enabled(1), disabled(2) } 830 -- ------------------------------------------------------------- 831 -- ------------------------------------------------------------- 832 -- groups in the P-BRIDGE MIB 833 -- ------------------------------------------------------------- 835 dot1dExtBase OBJECT IDENTIFIER ::= { pBridgeMIBObjects 1 } 836 dot1dPriority OBJECT IDENTIFIER ::= { pBridgeMIBObjects 2 } 837 dot1dGarp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 3 } 838 dot1dGmrp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 4 } 840 -- ------------------------------------------------------------- 842 -- ------------------------------------------------------------- 843 -- the dot1dExtBase group 844 -- ------------------------------------------------------------- 846 dot1dDeviceCapabilities OBJECT-TYPE 847 SYNTAX BITS { 848 dot1dExtendedFilteringServices(0), 849 -- can perform filtering of 850 -- individual multicast addresses 851 -- controlled by GMRP. 852 dot1dTrafficClasses(1), 853 -- can map user priority to 854 -- multiple traffic classes. 855 dot1qStaticEntryIndividualPort(2), 856 -- dot1qStaticUnicastReceivePort & 857 -- dot1qStaticMulticastReceivePort 858 -- can represent non-zero entries. 859 dot1qIVLCapable(3), -- Independent VLAN Learning. 860 dot1qSVLCapable(4), -- Shared VLAN Learning. 861 dot1qHybridCapable(5), 862 -- both IVL & SVL simultaneously. 863 dot1qConfigurablePvidTagging(6), 864 -- whether the implementation 865 -- supports the ability to 866 -- override the default PVID 867 -- setting and its egress status 868 -- (VLAN-Tagged or Untagged) on 869 -- each port. 870 dot1dLocalVlanCapable(7) 871 -- can support multiple local 872 -- bridges, outside of the scope 873 -- of 802.1Q defined VLANs. 874 } 875 MAX-ACCESS read-only 876 STATUS current 877 DESCRIPTION 878 "Indicates the optional parts of IEEE 802.1D and 802.1Q 879 that are implemented by this device and are manageable 880 through this MIB. Capabilities that are allowed on a 881 per-port basis are indicated in dot1dPortCapabilities." 882 REFERENCE 883 "ISO/IEC 15802-3 Section 5.2, 884 IEEE 802.1Q/D11 Section 5.2, 12.10.1.1.3/b/2" 885 ::= { dot1dExtBase 1 } 887 dot1dTrafficClassesEnabled OBJECT-TYPE 888 SYNTAX TruthValue 889 MAX-ACCESS read-write 890 STATUS current 891 DESCRIPTION 892 "The value true(1) indicates that Traffic Classes are 893 enabled on this bridge. When false(2), the bridge 894 operates with a single priority level for all traffic." 895 DEFVAL { true } 896 ::= { dot1dExtBase 2 } 898 dot1dGmrpStatus OBJECT-TYPE 899 SYNTAX EnabledStatus 900 MAX-ACCESS read-write 901 STATUS current 902 DESCRIPTION 903 "The administrative status requested by management for 904 GMRP. The value enabled(1) indicates that GMRP should 905 be enabled on this device, in all VLANs, on all ports 906 for which it has not been specifically disabled. When 907 disabled(2), GMRP is disabled, in all VLANs, on all 908 ports and all GMRP packets will be forwarded 909 transparently. This object affects both Applicant and 910 Registrar state machines. A transition from disabled(2) 911 to enabled(1) will cause a reset of all GMRP state 912 machines on all ports." 913 DEFVAL { enabled } 914 ::= { dot1dExtBase 3 } 916 -- ------------------------------------------------------------- 917 -- Port Capabilities Table 918 -- ------------------------------------------------------------- 920 dot1dPortCapabilitiesTable OBJECT-TYPE 921 SYNTAX SEQUENCE OF Dot1dPortCapabilitiesEntry 922 MAX-ACCESS not-accessible 923 STATUS current 924 DESCRIPTION 925 "A table that contains capabilities information about 926 every port that is associated with this bridge." 927 ::= { dot1dExtBase 4 } 929 dot1dPortCapabilitiesEntry OBJECT-TYPE 930 SYNTAX Dot1dPortCapabilitiesEntry 931 MAX-ACCESS not-accessible 932 STATUS current 933 DESCRIPTION 934 "A set of capabilities information about this port 935 indexed by dot1dBasePort." 936 AUGMENTS { dot1dBasePortEntry } 937 ::= { dot1dPortCapabilitiesTable 1 } 939 Dot1dPortCapabilitiesEntry ::= 940 SEQUENCE { 941 dot1dPortCapabilities 942 BITS 943 } 945 dot1dPortCapabilities OBJECT-TYPE 946 SYNTAX BITS { 947 dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of 948 -- frames and GVRP. 949 dot1qConfigurableAcceptableFrameTypes(1), 950 -- allows modified values of 951 -- dot1qPortAcceptableFrameTypes. 952 dot1qIngressFiltering(2) 953 -- supports the discarding of any 954 -- frame received on a Port whose 955 -- VLAN classification does not 956 -- include that Port in its Member 957 -- set. 958 } 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "Indicates the parts of IEEE 802.1D and 802.1Q that are 963 optional on a per-port basis that are implemented by 964 this device and are manageable through this MIB." 965 REFERENCE 966 "ISO/IEC 15802-3 Section 5.2, 967 IEEE 802.1Q/D11 Section 5.2" 968 ::= { dot1dPortCapabilitiesEntry 1 } 970 -- ------------------------------------------------------------- 971 -- the dot1dPriority group 972 -- ------------------------------------------------------------- 974 -- ------------------------------------------------------------- 975 -- Port Priority Table 976 -- ------------------------------------------------------------- 978 dot1dPortPriorityTable OBJECT-TYPE 979 SYNTAX SEQUENCE OF Dot1dPortPriorityEntry 980 MAX-ACCESS not-accessible 981 STATUS current 982 DESCRIPTION 983 "A table that contains information about every port that 984 is associated with this transparent bridge." 985 ::= { dot1dPriority 1 } 987 dot1dPortPriorityEntry OBJECT-TYPE 988 SYNTAX Dot1dPortPriorityEntry 989 MAX-ACCESS not-accessible 990 STATUS current 991 DESCRIPTION 992 "A list of Default User Priorities for each port of a 993 transparent bridge. This is indexed by dot1dBasePort." 994 AUGMENTS { dot1dBasePortEntry } 995 ::= { dot1dPortPriorityTable 1 } 997 Dot1dPortPriorityEntry ::= 998 SEQUENCE { 999 dot1dPortDefaultUserPriority 1000 INTEGER, 1001 dot1dPortNumTrafficClasses 1002 INTEGER 1003 } 1005 dot1dPortDefaultUserPriority OBJECT-TYPE 1006 SYNTAX INTEGER (0..7) 1007 MAX-ACCESS read-write 1008 STATUS current 1009 DESCRIPTION 1010 "The default ingress User Priority for this port. This 1011 only has effect on media, such as Ethernet, that do not 1012 support native User Priority." 1013 ::= { dot1dPortPriorityEntry 1 } 1015 dot1dPortNumTrafficClasses OBJECT-TYPE 1016 SYNTAX INTEGER (1..8) 1017 MAX-ACCESS read-write 1018 STATUS current 1019 DESCRIPTION 1020 "The number of egress traffic classes supported on this 1021 port. This object may optionally be read-only." 1022 ::= { dot1dPortPriorityEntry 2 } 1024 -- ------------------------------------------------------------- 1025 -- User Priority Regeneration Table 1026 -- ------------------------------------------------------------- 1028 dot1dUserPriorityRegenTable OBJECT-TYPE 1029 SYNTAX SEQUENCE OF Dot1dUserPriorityRegenEntry 1030 MAX-ACCESS not-accessible 1031 STATUS current 1032 DESCRIPTION 1033 "A list of Regenerated User Priorities for each received 1034 User Priority on each port of a bridge. The Regenerated 1035 User Priority value may be used to index the Traffic 1036 Class Table for each input port. This only has effect 1037 on media that support native User Priority. The default 1038 values for Regenerated User Priorities are the same as 1039 the User Priorities." 1040 REFERENCE 1041 "ISO/IEC 15802-3 Section 6.4" 1042 ::= { dot1dPriority 2 } 1044 dot1dUserPriorityRegenEntry OBJECT-TYPE 1045 SYNTAX Dot1dUserPriorityRegenEntry 1046 MAX-ACCESS not-accessible 1047 STATUS current 1048 DESCRIPTION 1049 "A mapping of incoming User Priority to a Regenerated 1050 User Priority." 1051 INDEX { dot1dBasePort, dot1dUserPriority } 1052 ::= { dot1dUserPriorityRegenTable 1 } 1054 Dot1dUserPriorityRegenEntry ::= 1055 SEQUENCE { 1056 dot1dUserPriority 1057 INTEGER, 1058 dot1dRegenUserPriority 1059 INTEGER 1060 } 1062 dot1dUserPriority OBJECT-TYPE 1063 SYNTAX INTEGER (0..7) 1064 MAX-ACCESS not-accessible 1065 STATUS current 1066 DESCRIPTION 1067 "The User Priority for a frame received on this port." 1068 ::= { dot1dUserPriorityRegenEntry 1 } 1070 dot1dRegenUserPriority OBJECT-TYPE 1071 SYNTAX INTEGER (0..7) 1072 MAX-ACCESS read-write 1073 STATUS current 1074 DESCRIPTION 1075 "The Regenerated User Priority the incoming User 1076 Priority is mapped to for this port." 1077 ::= { dot1dUserPriorityRegenEntry 2 } 1079 -- ------------------------------------------------------------- 1080 -- Traffic Class Table 1081 -- ------------------------------------------------------------- 1083 dot1dTrafficClassTable OBJECT-TYPE 1084 SYNTAX SEQUENCE OF Dot1dTrafficClassEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "A table mapping evaluated User Priority to Traffic 1089 Class, for forwarding by the bridge. Traffic class is a 1090 number in the range (0..(dot1dPortNumTrafficClasses-1))." 1091 REFERENCE 1092 "ISO/IEC 15802-3 Table 7-2" 1093 ::= { dot1dPriority 3 } 1095 dot1dTrafficClassEntry OBJECT-TYPE 1096 SYNTAX Dot1dTrafficClassEntry 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "User Priority to Traffic Class mapping." 1102 INDEX { dot1dBasePort, dot1dTrafficClassPriority } 1103 ::= { dot1dTrafficClassTable 1 } 1105 Dot1dTrafficClassEntry ::= 1106 SEQUENCE { 1107 dot1dTrafficClassPriority 1108 INTEGER, 1109 dot1dTrafficClass 1110 INTEGER 1111 } 1113 dot1dTrafficClassPriority OBJECT-TYPE 1114 SYNTAX INTEGER (0..7) 1115 MAX-ACCESS not-accessible 1116 STATUS current 1117 DESCRIPTION 1118 "The Priority value determined for the received frame. 1119 This value is equivalent to the priority indicated in 1120 the tagged frame received, or one of the evaluated 1121 priorities, determined according to the media-type. 1123 For untagged frames received from Ethernet media, this 1124 value is equal to the dot1dPortDefaultUserPriority value 1125 for the ingress port. 1127 For untagged frames received from non-Ethernet media, 1128 this value is equal to the dot1dRegenUserPriority value 1129 for the ingress port and media-specific user priority." 1130 ::= { dot1dTrafficClassEntry 1 } 1132 dot1dTrafficClass OBJECT-TYPE 1133 SYNTAX INTEGER (0..7) 1134 MAX-ACCESS read-write 1135 STATUS current 1136 DESCRIPTION 1137 "The Traffic Class the received frame is mapped to." 1138 ::= { dot1dTrafficClassEntry 2 } 1140 -- ------------------------------------------------------------- 1141 -- Outbound Access Priority Table 1142 -- ------------------------------------------------------------- 1144 dot1dPortOutboundAccessPriorityTable OBJECT-TYPE 1145 SYNTAX SEQUENCE OF Dot1dPortOutboundAccessPriorityEntry 1146 MAX-ACCESS not-accessible 1147 STATUS current 1148 DESCRIPTION 1149 "A table mapping Regenerated User Priority to Outbound 1150 Access Priority. This is a fixed mapping for all port 1151 types, with two options for 802.5 Token Ring." 1152 REFERENCE 1153 "ISO/IEC 15802-3 Table 7-3" 1154 ::= { dot1dPriority 4 } 1156 dot1dPortOutboundAccessPriorityEntry OBJECT-TYPE 1157 SYNTAX Dot1dPortOutboundAccessPriorityEntry 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "Regenerated User Priority to Outbound Access Priority 1162 mapping." 1163 INDEX { dot1dBasePort, dot1dRegenUserPriority } 1164 ::= { dot1dPortOutboundAccessPriorityTable 1 } 1166 Dot1dPortOutboundAccessPriorityEntry ::= 1167 SEQUENCE { 1168 dot1dPortOutboundAccessPriority 1169 INTEGER 1170 } 1172 dot1dPortOutboundAccessPriority OBJECT-TYPE 1173 SYNTAX INTEGER (0..7) 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "The Outbound Access Priority the received frame is 1178 mapped to." 1179 ::= { dot1dPortOutboundAccessPriorityEntry 1 } 1181 -- ------------------------------------------------------------- 1182 -- the dot1dGarp group 1183 -- ------------------------------------------------------------- 1185 -- ------------------------------------------------------------- 1186 -- The GARP Port Table 1187 -- ------------------------------------------------------------- 1189 dot1dPortGarpTable OBJECT-TYPE 1190 SYNTAX SEQUENCE OF Dot1dPortGarpEntry 1191 MAX-ACCESS not-accessible 1192 STATUS current 1193 DESCRIPTION 1194 "A table of GARP control information about every bridge 1195 port. This is indexed by dot1dBasePort." 1196 ::= { dot1dGarp 1 } 1198 dot1dPortGarpEntry OBJECT-TYPE 1199 SYNTAX Dot1dPortGarpEntry 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "GARP control information for a bridge port." 1204 AUGMENTS { dot1dBasePortEntry } 1205 ::= { dot1dPortGarpTable 1 } 1207 Dot1dPortGarpEntry ::= 1208 SEQUENCE { 1209 dot1dPortGarpJoinTime 1210 TimeInterval, 1211 dot1dPortGarpLeaveTime 1212 TimeInterval, 1213 dot1dPortGarpLeaveAllTime 1214 TimeInterval 1215 } 1217 dot1dPortGarpJoinTime OBJECT-TYPE 1218 SYNTAX TimeInterval 1219 MAX-ACCESS read-write 1220 STATUS current 1221 DESCRIPTION 1222 "The GARP Join time, in centiseconds." 1223 DEFVAL { 20 } 1224 ::= { dot1dPortGarpEntry 1 } 1226 dot1dPortGarpLeaveTime OBJECT-TYPE 1227 SYNTAX TimeInterval 1228 MAX-ACCESS read-write 1229 STATUS current 1230 DESCRIPTION 1231 "The GARP Leave time, in centiseconds." 1232 DEFVAL { 60 } 1233 ::= { dot1dPortGarpEntry 2 } 1235 dot1dPortGarpLeaveAllTime OBJECT-TYPE 1236 SYNTAX TimeInterval 1237 MAX-ACCESS read-write 1238 STATUS current 1239 DESCRIPTION 1240 "The GARP LeaveAll time, in centiseconds." 1241 DEFVAL { 1000 } 1242 ::= { dot1dPortGarpEntry 3 } 1244 -- ------------------------------------------------------------- 1245 -- The GMRP Port Configuration and Status Table 1246 -- ------------------------------------------------------------- 1248 dot1dPortGmrpTable OBJECT-TYPE 1249 SYNTAX SEQUENCE OF Dot1dPortGmrpEntry 1250 MAX-ACCESS not-accessible 1251 STATUS current 1252 DESCRIPTION 1253 "A table of GMRP control and status information about 1254 every bridge port. Augments the dot1dBasePortTable." 1255 ::= { dot1dGmrp 1 } 1257 dot1dPortGmrpEntry OBJECT-TYPE 1258 SYNTAX Dot1dPortGmrpEntry 1259 MAX-ACCESS not-accessible 1260 STATUS current 1261 DESCRIPTION 1262 "GMRP control and status information for a bridge port." 1263 AUGMENTS { dot1dBasePortEntry } 1264 ::= { dot1dPortGmrpTable 1 } 1266 Dot1dPortGmrpEntry ::= 1267 SEQUENCE { 1268 dot1dPortGmrpStatus 1269 EnabledStatus, 1270 dot1dPortGmrpFailedRegistrations 1271 Counter32, 1272 dot1dPortGmrpLastPduOrigin 1273 MacAddress 1274 } 1276 dot1dPortGmrpStatus OBJECT-TYPE 1277 SYNTAX EnabledStatus 1278 MAX-ACCESS read-write 1279 STATUS current 1280 DESCRIPTION 1281 "The administrative state of GMRP operation on this port. The 1282 value enabled(1) indicates that GMRP is enabled on this port 1283 in all VLANs as long as dot1dGmrpStatus is also enabled(1). 1284 A value of disabled(2) indicates that GMRP is disabled on this 1285 port in all VLANs: any GMRP packets received will 1286 be silently discarded and no GMRP registrations will be 1287 propagated from other ports. Setting this to a value of 1288 enabled(1) will be stored by the agent but will only take effect 1289 on the GMRP protocol operation if dot1dGmrpStatus also 1290 indicates the value enabled(1). This object affects all 1291 GMRP Applicant and Registrar state machines on this 1292 port. A transition from disabled(2) to enabled(1) will 1293 cause a reset of all GMRP state machines on this port." 1294 DEFVAL { enabled } 1295 ::= { dot1dPortGmrpEntry 1 } 1297 dot1dPortGmrpFailedRegistrations OBJECT-TYPE 1298 SYNTAX Counter32 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "The total number of failed GMRP registrations, for any 1303 reason, in all VLANs, on this port." 1304 ::= { dot1dPortGmrpEntry 2 } 1306 dot1dPortGmrpLastPduOrigin OBJECT-TYPE 1307 SYNTAX MacAddress 1308 MAX-ACCESS read-only 1309 STATUS current 1310 DESCRIPTION 1311 "The Source MAC Address of the last GMRP message 1312 received on this port." 1313 ::= { dot1dPortGmrpEntry 3 } 1315 -- ------------------------------------------------------------- 1316 -- High Capacity Port Table for Transparent Bridges 1317 -- ------------------------------------------------------------- 1319 dot1dTpHCPortTable OBJECT-TYPE 1320 SYNTAX SEQUENCE OF Dot1dTpHCPortEntry 1321 MAX-ACCESS not-accessible 1322 STATUS current 1323 DESCRIPTION 1324 "A table that contains information about every high 1325 capacity port that is associated with this transparent 1326 bridge." 1328 ::= { dot1dTp 5 } 1330 dot1dTpHCPortEntry OBJECT-TYPE 1331 SYNTAX Dot1dTpHCPortEntry 1332 MAX-ACCESS not-accessible 1333 STATUS current 1334 DESCRIPTION 1335 "Statistics information for each high capacity port of a 1336 transparent bridge." 1337 INDEX { dot1dTpPort } 1338 ::= { dot1dTpHCPortTable 1 } 1340 Dot1dTpHCPortEntry ::= 1341 SEQUENCE { 1342 dot1dTpHCPortInFrames 1343 Counter64, 1344 dot1dTpHCPortOutFrames 1345 Counter64, 1346 dot1dTpHCPortInDiscards 1347 Counter64 1348 } 1350 dot1dTpHCPortInFrames OBJECT-TYPE 1351 SYNTAX Counter64 1352 MAX-ACCESS read-only 1353 STATUS current 1354 DESCRIPTION 1355 "The number of frames that have been received by this 1356 port from its segment. Note that a frame received on 1357 the interface corresponding to this port is only counted 1358 by this object if and only if it is for a protocol being 1359 processed by the local bridging function, including 1360 bridge management frames." 1361 REFERENCE 1362 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1363 ::= { dot1dTpHCPortEntry 1 } 1365 dot1dTpHCPortOutFrames OBJECT-TYPE 1366 SYNTAX Counter64 1367 MAX-ACCESS read-only 1368 STATUS current 1369 DESCRIPTION 1370 "The number of frames that have been transmitted by this 1371 port to its segment. Note that a frame transmitted on 1372 the interface corresponding to this port is only counted 1373 by this object if and only if it is for a protocol being 1374 processed by the local bridging function, including 1375 bridge management frames." 1376 REFERENCE 1377 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1378 ::= { dot1dTpHCPortEntry 2 } 1380 dot1dTpHCPortInDiscards OBJECT-TYPE 1381 SYNTAX Counter64 1382 MAX-ACCESS read-only 1383 STATUS current 1384 DESCRIPTION 1385 "Count of valid frames that have been received by this 1386 port from its segment which were discarded (i.e., 1387 filtered) by the Forwarding Process." 1388 REFERENCE 1389 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1390 ::= { dot1dTpHCPortEntry 3 } 1392 -- ---------------------------------------------------- 1393 -- Upper part of High Capacity Port Table for Transparent Bridges 1394 -- ---------------------------------------------------- 1396 dot1dTpPortOverflowTable OBJECT-TYPE 1397 SYNTAX SEQUENCE OF Dot1dTpPortOverflowEntry 1398 MAX-ACCESS not-accessible 1399 STATUS current 1400 DESCRIPTION 1401 "A table that contains the most-significant bits of statistics 1402 counters for ports that are associated with this transparent 1403 bridge that are on high capacity interfaces, as defined in the 1404 conformance clauses for this table. This table is provided as a 1405 way to read 64-bit counters for agents which support only SNMPv1. 1407 Note that the reporting of most-significant and least-significant 1408 counter bits separately runs the risk of missing an overflow of 1409 the lower bits in the interval between sampling. The manager 1410 must be aware of this possibility, even within the same 1411 varbindlist, when interpreting the results of a request or 1412 asynchronous notification." 1413 ::= { dot1dTp 6 } 1415 dot1dTpPortOverflowEntry OBJECT-TYPE 1416 SYNTAX Dot1dTpPortOverflowEntry 1417 MAX-ACCESS not-accessible 1418 STATUS current 1419 DESCRIPTION 1420 "The most significant bits of statistics counters for a high 1421 capacity interface of a transparent bridge. Each object is 1422 associated with a corresponding object in dot1dTpPortTable which 1423 indicates the least significant bits of the counter." 1424 INDEX { dot1dTpPort } 1425 ::= { dot1dTpPortOverflowTable 1 } 1427 Dot1dTpPortOverflowEntry ::= 1428 SEQUENCE { 1429 dot1dTpPortInOverflowFrames 1430 Counter32, 1431 dot1dTpPortOutOverflowFrames 1432 Counter32, 1433 dot1dTpPortInOverflowDiscards 1434 Counter32 1435 } 1437 dot1dTpPortInOverflowFrames OBJECT-TYPE 1438 SYNTAX Counter32 1439 MAX-ACCESS read-only 1440 STATUS current 1441 DESCRIPTION 1442 "The number of times the associated dot1dTpPortInFrames 1443 counter has overflowed." 1444 REFERENCE 1445 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1446 ::= { dot1dTpPortOverflowEntry 1 } 1448 dot1dTpPortOutOverflowFrames OBJECT-TYPE 1449 SYNTAX Counter32 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "The number of times the associated dot1dTpPortOutFrames 1454 counter has overflowed." 1455 REFERENCE 1456 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1457 ::= { dot1dTpPortOverflowEntry 2 } 1459 dot1dTpPortInOverflowDiscards OBJECT-TYPE 1460 SYNTAX Counter32 1461 MAX-ACCESS read-only 1462 STATUS current 1463 DESCRIPTION 1464 "The number of times the associated 1465 dot1dTpPortInDiscards counter has overflowed." 1466 REFERENCE 1467 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1468 ::= { dot1dTpPortOverflowEntry 3 } 1470 -- ------------------------------------------------------------- 1471 -- IEEE 802.1p MIB - Conformance Information 1472 -- ------------------------------------------------------------- 1474 pBridgeConformance OBJECT IDENTIFIER ::= { pBridgeMIB 2 } 1476 pBridgeGroups OBJECT IDENTIFIER ::= { pBridgeConformance 1 } 1478 pBridgeCompliances OBJECT IDENTIFIER 1479 ::= { pBridgeConformance 2 } 1481 -- ------------------------------------------------------------- 1482 -- units of conformance 1483 -- ------------------------------------------------------------- 1485 pBridgeExtCapGroup OBJECT-GROUP 1486 OBJECTS { 1487 dot1dDeviceCapabilities, 1488 dot1dPortCapabilities 1489 } 1490 STATUS current 1491 DESCRIPTION 1492 "A collection of objects indicating the optional 1493 capabilites of the device." 1494 ::= { pBridgeGroups 1 } 1496 pBridgeDeviceGmrpGroup OBJECT-GROUP 1497 OBJECTS { 1498 dot1dGmrpStatus 1499 } 1500 STATUS current 1501 DESCRIPTION 1502 "A collection of objects providing device-level control 1503 for the Multicast Filtering extended bridge services." 1504 ::= { pBridgeGroups 2 } 1506 pBridgeDevicePriorityGroup OBJECT-GROUP 1507 OBJECTS { 1508 dot1dTrafficClassesEnabled 1509 } 1510 STATUS current 1511 DESCRIPTION 1512 "A collection of objects providing device-level control 1513 for the Priority services." 1514 ::= { pBridgeGroups 3 } 1516 pBridgeDefaultPriorityGroup OBJECT-GROUP 1517 OBJECTS { 1518 dot1dPortDefaultUserPriority 1519 } 1520 STATUS current 1521 DESCRIPTION 1522 "A collection of objects defining the User Priority 1523 applicable to each port for media which do not support 1524 native User Priority." 1525 ::= { pBridgeGroups 4 } 1527 pBridgeRegenPriorityGroup OBJECT-GROUP 1528 OBJECTS { 1529 dot1dRegenUserPriority 1530 } 1531 STATUS current 1532 DESCRIPTION 1533 "A collection of objects defining the User Priorities 1534 applicable to each port for media which support native 1535 User Priority." 1536 ::= { pBridgeGroups 5 } 1538 pBridgePriorityGroup OBJECT-GROUP 1539 OBJECTS { 1540 dot1dPortNumTrafficClasses, 1541 dot1dTrafficClass 1542 } 1543 STATUS current 1544 DESCRIPTION 1545 "A collection of objects defining the traffic classes 1546 within a bridge for each evaluated User Priority." 1547 ::= { pBridgeGroups 6 } 1549 pBridgeAccessPriorityGroup OBJECT-GROUP 1550 OBJECTS { 1551 dot1dPortOutboundAccessPriority 1552 } 1553 STATUS current 1554 DESCRIPTION 1555 "A collection of objects defining the media dependent 1556 outbound access level for each priority." 1557 ::= { pBridgeGroups 7 } 1559 pBridgePortGarpGroup OBJECT-GROUP 1560 OBJECTS { 1561 dot1dPortGarpJoinTime, 1562 dot1dPortGarpLeaveTime, 1563 dot1dPortGarpLeaveAllTime 1564 } 1565 STATUS current 1566 DESCRIPTION 1567 "A collection of objects providing port level control 1568 and status information for GARP operation." 1569 ::= { pBridgeGroups 8 } 1571 pBridgePortGmrpGroup OBJECT-GROUP 1572 OBJECTS { 1573 dot1dPortGmrpStatus, 1574 dot1dPortGmrpFailedRegistrations, 1575 dot1dPortGmrpLastPduOrigin 1576 } 1577 STATUS current 1578 DESCRIPTION 1579 "A collection of objects providing port level control 1580 and status information for GMRP operation." 1581 ::= { pBridgeGroups 9 } 1583 pBridgeHCPortGroup OBJECT-GROUP 1584 OBJECTS { 1585 dot1dTpHCPortInFrames, 1586 dot1dTpHCPortOutFrames, 1587 dot1dTpHCPortInDiscards 1588 } 1589 STATUS current 1590 DESCRIPTION 1591 "A collection of objects providing 64-bit statistics 1592 counters for high capacity bridge ports." 1593 ::= { pBridgeGroups 10 } 1595 pBridgePortOverflowGroup OBJECT-GROUP 1596 OBJECTS { 1597 dot1dTpPortInOverflowFrames, 1598 dot1dTpPortOutOverflowFrames, 1599 dot1dTpPortInOverflowDiscards 1600 } 1601 STATUS current 1602 DESCRIPTION 1603 "A collection of objects providing overflow statistics 1604 counters for high capacity bridge ports." 1605 ::= { pBridgeGroups 11 } 1607 -- ------------------------------------------------------------- 1608 -- compliance statements 1609 -- ------------------------------------------------------------- 1611 pBridgeCompliance MODULE-COMPLIANCE 1612 STATUS current 1613 DESCRIPTION 1614 "The compliance statement for device support of Priority 1615 and Multicast Filtering extended bridging services." 1617 MODULE 1618 MANDATORY-GROUPS { pBridgeExtCapGroup } 1620 GROUP pBridgeDeviceGmrpGroup 1621 DESCRIPTION 1622 "This group is mandatory for devices supporting the GMRP 1623 application, defined by IEEE 802.1D Extended Filtering 1624 Services." 1626 GROUP pBridgeDevicePriorityGroup 1627 DESCRIPTION 1628 "This group is mandatory only for devices supporting 1629 the priority forwarding operations defined by IEEE 802.1D." 1631 GROUP pBridgeDefaultPriorityGroup 1632 DESCRIPTION 1633 "This group is mandatory only for devices supporting 1634 the priority forwarding operations defined by the 1635 extended bridge services with media types, such as 1636 Ethernet, that do not support native User Priority." 1638 GROUP pBridgeRegenPriorityGroup 1639 DESCRIPTION 1640 "This group is mandatory only for devices supporting 1641 the priority forwarding operations defined by IEEE 802.1D 1642 and which have interface media types that support 1643 native User Priority e.g. IEEE 802.5." 1645 GROUP pBridgePriorityGroup 1646 DESCRIPTION 1647 "This group is mandatory only for devices supporting 1648 the priority forwarding operations defined by IEEE 802.1D." 1650 GROUP pBridgeAccessPriorityGroup 1651 DESCRIPTION 1652 "This group is optional and is relevant only for devices 1653 supporting the priority forwarding operations defined by 1654 IEEE 802.1D and which have interface media types that support 1655 native Access Priority e.g. IEEE 802.5." 1657 GROUP pBridgePortGarpGroup 1658 DESCRIPTION 1659 "This group is mandatory for devices supporting any 1660 of the GARP applications: e.g. GMRP, defined by the 1661 extended filtering services of 802.1D; or GVRP, 1662 defined by 802.1Q (refer to the Q-BRIDGE-MIB for 1663 conformance statements for GVRP)." 1665 GROUP pBridgePortGmrpGroup 1666 DESCRIPTION 1667 "This group is mandatory for devices supporting the 1668 GMRP application, as defined by IEEE 802.1D Extended 1669 Filtering Services." 1671 GROUP pBridgeHCPortGroup 1672 DESCRIPTION 1673 "Support for this group in a device is mandatory for those 1674 bridge ports which map to network interfaces that have the 1675 value of the corresponding instance of ifSpeed 1676 greater than 650,000,000 bits/second." 1678 GROUP pBridgePortOverflowGroup 1679 DESCRIPTION 1680 "Support for this group in a device is mandatory for those 1681 bridge ports which map to network interfaces that have the 1682 value of the corresponding instance of ifSpeed 1683 greater than 650,000,000 bits/second." 1685 OBJECT dot1dPortNumTrafficClasses 1686 MIN-ACCESS read-only 1687 DESCRIPTION 1688 "Write access is not required." 1690 OBJECT dot1dTrafficClass 1691 MIN-ACCESS read-only 1692 DESCRIPTION 1693 "Write access is not required." 1695 OBJECT dot1dRegenUserPriority 1696 MIN-ACCESS read-only 1697 DESCRIPTION 1698 "Write access is not required." 1700 ::= { pBridgeCompliances 1 } 1702 END 1703 5. Definitions for Virtual Bridge MIB 1705 Q-BRIDGE-MIB DEFINITIONS ::= BEGIN 1707 -- ------------------------------------------------------------- 1708 -- MIB for IEEE 802.1Q Devices 1709 -- ------------------------------------------------------------- 1711 IMPORTS 1712 MODULE-IDENTITY, OBJECT-TYPE, 1713 Counter32, Counter64, Unsigned32, TimeTicks 1714 FROM SNMPv2-SMI 1715 RowStatus, TruthValue, TEXTUAL-CONVENTION, MacAddress 1716 FROM SNMPv2-TC 1717 SnmpAdminString 1718 FROM SNMP-FRAMEWORK-MIB 1719 MODULE-COMPLIANCE, OBJECT-GROUP 1720 FROM SNMPv2-CONF 1721 dot1dBridge, dot1dBasePortEntry, dot1dBasePort 1722 FROM BRIDGE-MIB 1723 EnabledStatus 1724 FROM P-BRIDGE-MIB 1725 TimeFilter 1726 FROM RMON2-MIB; 1728 qBridgeMIB MODULE-IDENTITY 1729 LAST-UPDATED "9906150000Z" 1730 ORGANIZATION "IETF Bridge MIB Working Group" 1731 CONTACT-INFO 1732 " Les Bell 1733 Postal: 3Com Europe Ltd. 1734 3Com Centre, Boundary Way 1735 Hemel Hempstead, Herts. HP2 7YU 1736 UK 1737 Phone: +44 1442 438025 1738 Email: Les_Bell@3Com.com 1740 Andrew Smith 1741 Postal: Extreme Networks 1742 3585 Monroe St. 1743 Santa Clara CA 95051 1744 USA 1745 Phone: +1 408 579 2821 1746 Email: andrew@extremenetworks.com 1747 Paul Langille 1748 Postal: Newbridge Networks 1749 5 Corporate Drive 1750 Andover, MA 01810 1751 USA 1752 Phone: +1 978 691 4665 1753 Email: langille@newbridge.com 1755 Anil Rijhsinghani 1756 Postal: Cabletron Systems 1757 50 Minuteman Road 1758 Andover, MA 01810 1759 USA 1760 Phone: +1 978 684 1295 1761 Email: anil@cabletron.com 1763 Keith McCloghrie 1764 Postal: cisco Systems, Inc. 1765 170 West Tasman Drive 1766 San Jose, CA 95134-1706 1767 USA 1768 Phone: +1 408 526 5260 1769 Email: kzm@cisco.com" 1770 DESCRIPTION 1771 "The VLAN Bridge MIB module for managing Virtual Bridged 1772 Local Area Networks, as defined by IEEE 802.1Q-1998." 1774 -- revision history 1776 REVISION "9906150000Z" 1777 DESCRIPTION 1778 "Initial version, published as RFC xxxx." 1780 ::= { dot1dBridge 7 } 1782 qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 } 1784 -- ------------------------------------------------------------- 1785 -- Textual Conventions 1786 -- ------------------------------------------------------------- 1788 PortList ::= TEXTUAL-CONVENTION 1789 STATUS current 1790 DESCRIPTION 1791 "Each octet within this value specifies a set of eight 1792 ports, with the first octet specifying ports 1 through 1793 8, the second octet specifying ports 9 through 16, etc. 1794 Within each octet, the most significant bit represents 1795 the lowest numbered port, and the least significant bit 1796 represents the highest numbered port. Thus, each port 1797 of the bridge is represented by a single bit within the 1798 value of this object. If that bit has a value of '1' 1799 then that port is included in the set of ports; the port 1800 is not included if its bit has a value of '0'." 1801 SYNTAX OCTET STRING 1803 VlanIndex ::= TEXTUAL-CONVENTION 1804 STATUS current 1805 DESCRIPTION 1806 "A value used to index per-VLAN tables: values of 0 and 1807 4095 are not permitted; if the value is between 1 and 1808 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with 1809 global scope within a given bridged domain (see VlanId 1810 textual convention). If the value is greater than 4095 1811 then it represents a VLAN with scope local to the 1812 particular agent, i.e. one without a global VLAN-ID 1813 assigned to it. Such VLANs are outside the scope of 1814 IEEE 802.1Q but it is convenient to be able to manage them 1815 in the same way using this MIB." 1816 SYNTAX Unsigned32 1818 VlanId ::= TEXTUAL-CONVENTION 1819 STATUS current 1820 DESCRIPTION 1821 "A 12-bit VLAN ID used in the VLAN Tag header." 1822 SYNTAX INTEGER (1..4094) 1824 -- ------------------------------------------------------------- 1825 -- groups in the Q-BRIDGE MIB 1826 -- ------------------------------------------------------------- 1828 dot1qBase OBJECT IDENTIFIER ::= { qBridgeMIBObjects 1 } 1829 dot1qTp OBJECT IDENTIFIER ::= { qBridgeMIBObjects 2 } 1830 dot1qStatic OBJECT IDENTIFIER ::= { qBridgeMIBObjects 3 } 1831 dot1qVlan OBJECT IDENTIFIER ::= { qBridgeMIBObjects 4 } 1833 -- ------------------------------------------------------------- 1835 -- ------------------------------------------------------------- 1836 -- dot1qBase group 1837 -- ------------------------------------------------------------- 1839 dot1qVlanVersionNumber OBJECT-TYPE 1840 SYNTAX INTEGER { 1841 version1(1) 1842 } 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "The version number of IEEE 802.1Q that this device 1847 supports." 1848 REFERENCE 1849 "IEEE 802.1Q/D11 Section 12.10.1.1" 1850 ::= { dot1qBase 1 } 1852 dot1qMaxVlanId OBJECT-TYPE 1853 SYNTAX VlanId 1854 MAX-ACCESS read-only 1855 STATUS current 1856 DESCRIPTION 1857 "The maximum IEEE 802.1Q VLAN ID that this device 1858 supports." 1859 REFERENCE 1860 "IEEE 802.1Q/D11 Section 9.3.2.3" 1861 ::= { dot1qBase 2 } 1863 dot1qMaxSupportedVlans OBJECT-TYPE 1864 SYNTAX Unsigned32 1865 MAX-ACCESS read-only 1866 STATUS current 1867 DESCRIPTION 1868 "The maximum number of IEEE 802.1Q VLANs that this 1869 device supports." 1870 REFERENCE 1871 "IEEE 802.1Q/D11 Section 12.10.1.1" 1872 ::= { dot1qBase 3 } 1874 dot1qNumVlans OBJECT-TYPE 1875 SYNTAX Unsigned32 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION 1879 "The current number of IEEE 802.1Q VLANs that are 1880 configured in this device." 1881 REFERENCE 1882 "IEEE 802.1Q/D11 Section 12.7.1.1" 1883 ::= { dot1qBase 4 } 1885 dot1qGvrpStatus OBJECT-TYPE 1886 SYNTAX EnabledStatus 1887 MAX-ACCESS read-write 1888 STATUS current 1889 DESCRIPTION 1890 "The administrative status requested by management for 1891 GVRP. The value enabled(1) indicates that GVRP should 1892 be enabled on this device, on all ports for which it has 1893 not been specifically disabled. When disabled(2), GVRP 1894 is disabled on all ports and all GVRP packets will be 1895 forwarded transparently. This object affects all GVRP 1896 Applicant and Registrar state machines. A transition 1897 from disabled(2) to enabled(1) will cause a reset of all 1898 GVRP state machines on all ports." 1899 DEFVAL { enabled } 1900 ::= { dot1qBase 5 } 1902 -- ------------------------------------------------------------- 1903 -- the dot1qTp group 1904 -- ------------------------------------------------------------- 1906 -- ------------------------------------------------------------- 1907 -- the current Filtering Database Table 1908 -- ------------------------------------------------------------- 1910 dot1qFdbTable OBJECT-TYPE 1911 SYNTAX SEQUENCE OF Dot1qFdbEntry 1912 MAX-ACCESS not-accessible 1913 STATUS current 1914 DESCRIPTION 1915 "A table that contains configuration and control 1916 information for each Filtering Database currently 1917 operating on this device. Entries in this table appear 1918 automatically when VLANs are assigned FDB IDs in the 1919 dot1qVlanCurrentTable." 1920 ::= { dot1qTp 1 } 1922 dot1qFdbEntry OBJECT-TYPE 1923 SYNTAX Dot1qFdbEntry 1924 MAX-ACCESS not-accessible 1925 STATUS current 1926 DESCRIPTION 1927 "Information about a specific Filtering Database." 1928 INDEX { dot1qFdbId } 1929 ::= { dot1qFdbTable 1 } 1931 Dot1qFdbEntry ::= 1932 SEQUENCE { 1933 dot1qFdbId 1934 Unsigned32, 1935 dot1qFdbDynamicCount 1936 Counter32 1937 } 1939 dot1qFdbId OBJECT-TYPE 1940 SYNTAX Unsigned32 1941 MAX-ACCESS not-accessible 1942 STATUS current 1943 DESCRIPTION 1944 "The identity of this Filtering Database." 1945 ::= { dot1qFdbEntry 1 } 1947 dot1qFdbDynamicCount OBJECT-TYPE 1948 SYNTAX Counter32 1949 MAX-ACCESS read-only 1950 STATUS current 1951 DESCRIPTION 1952 "The current number of dynamic entries in this 1953 Filtering Database." 1954 REFERENCE 1955 "IEEE 802.1Q/D11 Section 12.7.1.1.3" 1956 ::= { dot1qFdbEntry 2 } 1958 -- ------------------------------------------------------------- 1959 -- Multiple Forwarding Databases for 802.1Q Transparent devices 1960 -- This table is an alternative to the dot1dTpFdbTable, 1961 -- previously defined for 802.1D devices which only support a 1962 -- single Forwarding Database. 1963 -- ------------------------------------------------------------- 1965 dot1qTpFdbTable OBJECT-TYPE 1966 SYNTAX SEQUENCE OF Dot1qTpFdbEntry 1967 MAX-ACCESS not-accessible 1968 STATUS current 1969 DESCRIPTION 1970 "A table that contains information about unicast entries 1971 for which the device has forwarding and/or filtering 1972 information. This information is used by the 1973 transparent bridging function in determining how to 1974 propagate a received frame." 1975 REFERENCE 1976 "IEEE 802.1Q/D11 Section 12.7.7" 1977 ::= { dot1qTp 2 } 1979 dot1qTpFdbEntry OBJECT-TYPE 1980 SYNTAX Dot1qTpFdbEntry 1981 MAX-ACCESS not-accessible 1982 STATUS current 1983 DESCRIPTION 1984 "Information about a specific unicast MAC address for 1985 which the device has some forwarding and/or filtering 1986 information." 1987 INDEX { dot1qFdbId, dot1qTpFdbAddress } 1988 ::= { dot1qTpFdbTable 1 } 1990 Dot1qTpFdbEntry ::= 1991 SEQUENCE { 1992 dot1qTpFdbAddress 1993 MacAddress, 1994 dot1qTpFdbPort 1995 INTEGER, 1996 dot1qTpFdbStatus 1997 INTEGER 1998 } 2000 dot1qTpFdbAddress OBJECT-TYPE 2001 SYNTAX MacAddress 2002 MAX-ACCESS not-accessible 2003 STATUS current 2004 DESCRIPTION 2005 "A unicast MAC address for which the device has 2006 forwarding and/or filtering information." 2007 ::= { dot1qTpFdbEntry 1 } 2009 dot1qTpFdbPort OBJECT-TYPE 2010 SYNTAX INTEGER (0..65535) 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "Either the value '0', or the port number of the port on 2015 which a frame having a source address equal to the value 2016 of the corresponding instance of dot1qTpFdbAddress has 2017 been seen. A value of '0' indicates that the port 2018 number has not been learned but that the device does 2019 have some forwarding/filtering information about this 2020 address (e.g. in the dot1qStaticUnicastTable). 2021 Implementors are encouraged to assign the port value to 2022 this object whenever it is learned even for addresses 2023 for which the corresponding value of dot1qTpFdbStatus is 2024 not learned(3)." 2025 ::= { dot1qTpFdbEntry 2 } 2027 dot1qTpFdbStatus OBJECT-TYPE 2028 SYNTAX INTEGER { 2029 other(1), 2030 invalid(2), 2031 learned(3), 2032 self(4), 2033 mgmt(5) 2034 } 2035 MAX-ACCESS read-only 2036 STATUS current 2037 DESCRIPTION 2038 "The status of this entry. The meanings of the values 2039 are: 2040 other(1) - none of the following. This may include 2041 the case where some other MIB object (not the 2042 corresponding instance of dot1qTpFdbPort, nor an 2043 entry in the dot1qStaticUnicastTable) is being 2044 used to determine if and how frames addressed to 2045 the value of the corresponding instance of 2046 dot1qTpFdbAddress are being forwarded. 2047 invalid(2) - this entry is no longer valid (e.g., it 2048 was learned but has since aged out), but has not 2049 yet been flushed from the table. 2050 learned(3) - the value of the corresponding instance 2051 of dot1qTpFdbPort was learned and is being used. 2052 self(4) - the value of the corresponding instance of 2053 dot1qTpFdbAddress represents one of the device's 2054 addresses. The corresponding instance of 2055 dot1qTpFdbPort indicates which of the device's 2056 ports has this address. 2057 mgmt(5) - the value of the corresponding instance of 2058 dot1qTpFdbAddress is also the value of an 2059 existing instance of dot1qStaticAddress." 2060 ::= { dot1qTpFdbEntry 3 } 2062 -- ------------------------------------------------------------- 2063 -- Dynamic Group Registration Table 2064 -- ------------------------------------------------------------- 2066 dot1qTpGroupTable OBJECT-TYPE 2067 SYNTAX SEQUENCE OF Dot1qTpGroupEntry 2068 MAX-ACCESS not-accessible 2069 STATUS current 2070 DESCRIPTION 2071 "A table containing filtering information for VLANs 2072 configured into the bridge by (local or network) 2073 management, or learnt dynamically, specifying the set of 2074 ports to which frames received on a VLAN for this FDB 2075 and containing a specific Group destination address are 2076 allowed to be forwarded." 2077 ::= { dot1qTp 3 } 2079 dot1qTpGroupEntry OBJECT-TYPE 2080 SYNTAX Dot1qTpGroupEntry 2081 MAX-ACCESS not-accessible 2082 STATUS current 2083 DESCRIPTION 2084 "Filtering information configured into the bridge by 2085 management, or learnt dynamically, specifying the set of 2086 ports to which frames received on a VLAN and containing 2087 a specific Group destination address, are allowed to be 2088 forwarded. The subset of these ports learnt dynamically 2089 is also provided." 2090 INDEX { dot1qVlanIndex, dot1qTpGroupAddress } 2091 ::= { dot1qTpGroupTable 1 } 2093 Dot1qTpGroupEntry ::= 2094 SEQUENCE { 2095 dot1qTpGroupAddress 2096 MacAddress, 2097 dot1qTpGroupEgressPorts 2098 PortList, 2099 dot1qTpGroupLearnt 2100 PortList 2101 } 2103 dot1qTpGroupAddress OBJECT-TYPE 2104 SYNTAX MacAddress 2105 MAX-ACCESS not-accessible 2106 STATUS current 2107 DESCRIPTION 2108 "The destination Group MAC address in a frame to which 2109 this entry's filtering information applies." 2110 ::= { dot1qTpGroupEntry 1 } 2112 dot1qTpGroupEgressPorts OBJECT-TYPE 2113 SYNTAX PortList 2114 MAX-ACCESS read-only 2115 STATUS current 2116 DESCRIPTION 2117 "The complete set of ports, in this VLAN, to which 2118 frames destined for this Group MAC address are currently 2119 being explicitly forwarded. This does not include ports 2120 for which this address is only implicitly forwarded, in 2121 the dot1qForwardAllPorts list." 2122 ::= { dot1qTpGroupEntry 2 } 2124 dot1qTpGroupLearnt OBJECT-TYPE 2125 SYNTAX PortList 2126 MAX-ACCESS read-only 2127 STATUS current 2128 DESCRIPTION 2129 "The subset of ports in dot1qTpGroupEgressPorts which 2130 were learnt by GMRP or some other dynamic mechanism, in 2131 this Filtering database." 2132 ::= { dot1qTpGroupEntry 3 } 2134 -- ------------------------------------------------------------- 2135 -- Service Requirements Group 2136 -- ------------------------------------------------------------- 2138 dot1qForwardAllTable OBJECT-TYPE 2139 SYNTAX SEQUENCE OF Dot1qForwardAllEntry 2140 MAX-ACCESS not-accessible 2141 STATUS current 2142 DESCRIPTION 2143 "A table containing forwarding information for each 2144 VLAN, specifying the set of ports to which forwarding of 2145 all multicasts applies, configured statically by 2146 management or dynamically by GMRP. An entry appears in 2147 this table for all VLANs that are currently 2148 instantiated." 2149 REFERENCE 2150 "IEEE 802.1Q/D11 Section 12.7.2, 12.7.7" 2151 ::= { dot1qTp 4 } 2153 dot1qForwardAllEntry OBJECT-TYPE 2154 SYNTAX Dot1qForwardAllEntry 2155 MAX-ACCESS not-accessible 2156 STATUS current 2157 DESCRIPTION 2158 "Forwarding information for a VLAN, specifying the set 2159 of ports to which all multicasts should be forwarded, 2160 configured statically by management or dynamically by 2161 GMRP." 2162 INDEX { dot1qVlanIndex } 2163 ::= { dot1qForwardAllTable 1 } 2165 Dot1qForwardAllEntry ::= 2166 SEQUENCE { 2167 dot1qForwardAllPorts 2168 PortList, 2169 dot1qForwardAllStaticPorts 2170 PortList, 2171 dot1qForwardAllForbiddenPorts 2172 PortList 2173 } 2175 dot1qForwardAllPorts OBJECT-TYPE 2176 SYNTAX PortList 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 "The complete set of ports in this VLAN to which all 2181 multicast group-addressed frames are to be forwarded. 2182 This includes ports for which this need has been 2183 determined dynamically by GMRP, or configured statically 2184 by management." 2185 ::= { dot1qForwardAllEntry 1 } 2187 dot1qForwardAllStaticPorts OBJECT-TYPE 2188 SYNTAX PortList 2189 MAX-ACCESS read-write 2190 STATUS current 2191 DESCRIPTION 2192 "The set of ports configured by management in this VLAN 2193 to which all multicast group-addressed frames are to be 2194 forwarded. Ports entered in this list will also appear 2195 in the complete set shown by dot1qForwardAllPorts. This 2196 value will be restored after the device is reset. This 2197 only applies to ports that are members of the VLAN, 2198 defined by dot1qVlanCurrentEgressPorts. A port may not 2199 be added in this set if it is already a member of the 2200 set of ports in dot1qForwardAllForbiddenPorts. The 2201 default value is a string of ones of appropriate length, 2202 to indicate standard non-EFS behaviour, i.e. forward 2203 all multicasts to all ports." 2204 ::= { dot1qForwardAllEntry 2 } 2206 dot1qForwardAllForbiddenPorts OBJECT-TYPE 2207 SYNTAX PortList 2208 MAX-ACCESS read-write 2209 STATUS current 2210 DESCRIPTION 2211 "The set of ports configured by management in this VLAN 2212 for which the Service Requirement attribute Forward All 2213 Multicast Groups may not be dynamically registered by 2214 GMRP. This value will be restored after the device is 2215 reset. A port may not be added in this set if it is 2216 already a member of the set of ports in 2217 dot1qForwardAllStaticPorts. The default value is a 2218 string of zeros of appropriate length." 2219 ::= { dot1qForwardAllEntry 3 } 2221 dot1qForwardUnregisteredTable OBJECT-TYPE 2222 SYNTAX SEQUENCE OF Dot1qForwardUnregisteredEntry 2223 MAX-ACCESS not-accessible 2224 STATUS current 2225 DESCRIPTION 2226 "A table containing forwarding information for each 2227 VLAN, specifying the set of ports to which forwarding of 2228 multicast group-addressed frames for which there is no 2229 more specific forwarding information applies. This is 2230 configured statically by management and determined 2231 dynamically by GMRP. An entry appears in this table for 2232 all VLANs that are currently instantiated." 2233 REFERENCE 2234 "IEEE 802.1Q/D11 Section 12.7.2, 12.7.7" 2235 ::= { dot1qTp 5 } 2237 dot1qForwardUnregisteredEntry OBJECT-TYPE 2238 SYNTAX Dot1qForwardUnregisteredEntry 2239 MAX-ACCESS not-accessible 2240 STATUS current 2241 DESCRIPTION 2242 "Forwarding information for a VLAN, specifying the set 2243 of ports to which all multicasts for which there is no 2244 more specific forwarding information shall be forwarded. 2245 This is configured statically by management or 2246 dynamically by GMRP." 2247 INDEX { dot1qVlanIndex } 2248 ::= { dot1qForwardUnregisteredTable 1 } 2250 Dot1qForwardUnregisteredEntry ::= 2251 SEQUENCE { 2252 dot1qForwardUnregisteredPorts 2253 PortList, 2254 dot1qForwardUnregisteredStaticPorts 2255 PortList, 2256 dot1qForwardUnregisteredForbiddenPorts 2257 PortList 2258 } 2260 dot1qForwardUnregisteredPorts OBJECT-TYPE 2261 SYNTAX PortList 2262 MAX-ACCESS read-only 2263 STATUS current 2264 DESCRIPTION 2265 "The complete set of ports in this VLAN to which 2266 multicast group-addressed frames for which there is no 2267 more specific forwarding information will be forwarded. 2268 This includes ports for which this need has been 2269 determined dynamically by GMRP, or configured statically 2270 by management." 2271 ::= { dot1qForwardUnregisteredEntry 1 } 2273 dot1qForwardUnregisteredStaticPorts OBJECT-TYPE 2274 SYNTAX PortList 2275 MAX-ACCESS read-write 2276 STATUS current 2277 DESCRIPTION 2278 "The set of ports configured by management, in this 2279 VLAN, to which multicast group-addressed frames for 2280 which there is no more specific forwarding information 2281 are to be forwarded. Ports entered in this list will 2282 also appear in the complete set shown by 2283 dot1qForwardUnregisteredPorts. This value will be 2284 restored after the device is reset. A port may not be 2285 added in this set if it is already a member of the set 2286 of ports in dot1qForwardUnregisteredForbiddenPorts. The 2287 default value is a string of zeros of appropriate 2288 length, although this has no effect with the default 2289 value of dot1qForwardAllStaticPorts." 2290 ::= { dot1qForwardUnregisteredEntry 2 } 2292 dot1qForwardUnregisteredForbiddenPorts OBJECT-TYPE 2293 SYNTAX PortList 2294 MAX-ACCESS read-write 2295 STATUS current 2296 DESCRIPTION 2297 "The set of ports configured by management in this VLAN 2298 for which the Service Requirement attribute Forward 2299 Unregistered Multicast Groups may not be dynamically 2300 registered by GMRP. This value will be restored after 2301 the device is reset. A port may not be added in this 2302 set if it is already a member of the set of ports in 2303 dot1qForwardUnregisteredStaticPorts. The default value 2304 is a string of zeros of appropriate length." 2305 ::= { dot1qForwardUnregisteredEntry 3 } 2307 -- ------------------------------------------------------------- 2308 -- The Static (Destination-Address Filtering) Database 2309 -- ------------------------------------------------------------- 2311 dot1qStaticUnicastTable OBJECT-TYPE 2312 SYNTAX SEQUENCE OF Dot1qStaticUnicastEntry 2313 MAX-ACCESS not-accessible 2314 STATUS current 2315 DESCRIPTION 2316 "A table containing filtering information for Unicast 2317 MAC addresses for each Filtering Database, configured 2318 into the device by (local or network) management 2319 specifying the set of ports to which frames received 2320 from specific ports and containing specific unicast 2321 destination addresses are allowed to be forwarded. A 2322 value of zero in this table as the port number from 2323 which frames with a specific destination address are 2324 received, is used to specify all ports for which there 2325 is no specific entry in this table for that particular 2326 destination address. Entries are valid for unicast 2327 addresses only." 2328 REFERENCE 2329 "IEEE 802.1Q/D11 Section 12.7.7, 2330 ISO/IEC 15802-3 Section 7.9.1" 2331 ::= { dot1qStatic 1 } 2333 dot1qStaticUnicastEntry OBJECT-TYPE 2334 SYNTAX Dot1qStaticUnicastEntry 2335 MAX-ACCESS not-accessible 2336 STATUS current 2337 DESCRIPTION 2338 "Filtering information configured into the device by 2339 (local or network) management specifying the set of 2340 ports to which frames received from a specific port and 2341 containing a specific unicast destination address are 2342 allowed to be forwarded." 2343 INDEX { 2344 dot1qFdbId, 2345 dot1qStaticUnicastAddress, 2346 dot1qStaticUnicastReceivePort 2347 } 2348 ::= { dot1qStaticUnicastTable 1 } 2350 Dot1qStaticUnicastEntry ::= 2351 SEQUENCE { 2352 dot1qStaticUnicastAddress 2353 MacAddress, 2354 dot1qStaticUnicastReceivePort 2355 INTEGER, 2356 dot1qStaticUnicastAllowedToGoTo 2357 PortList, 2358 dot1qStaticUnicastStatus 2359 INTEGER 2360 } 2362 dot1qStaticUnicastAddress OBJECT-TYPE 2363 SYNTAX MacAddress 2364 MAX-ACCESS not-accessible 2365 STATUS current 2366 DESCRIPTION 2367 "The destination MAC address in a frame to which this 2368 entry's filtering information applies. This object must 2369 take the value of a unicast address." 2370 ::= { dot1qStaticUnicastEntry 1 } 2372 dot1qStaticUnicastReceivePort OBJECT-TYPE 2373 SYNTAX INTEGER (0..65535) 2374 MAX-ACCESS not-accessible 2375 STATUS current 2376 DESCRIPTION 2377 "Either the value '0', or the port number of the port 2378 from which a frame must be received in order for this 2379 entry's filtering information to apply. A value of zero 2380 indicates that this entry applies on all ports of the 2381 device for which there is no other applicable entry." 2382 ::= { dot1qStaticUnicastEntry 2 } 2384 dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE 2385 SYNTAX PortList 2386 MAX-ACCESS read-write 2387 STATUS current 2388 DESCRIPTION 2389 "The set of ports for which a frame with a specific 2390 unicast address will be flooded in the event that it 2391 has not been learned. It also specifies the set of 2392 ports a specific unicast address may be dynamically 2393 learnt on. The dot1qTpFdbTable will have an equivalent 2394 entry with a dot1qTpFdbPort value of '0' until this 2395 address has been learnt, when it will be updated with 2396 the port the address has been seen on. This only 2397 applies to ports that are members of the VLAN, defined 2398 by dot1qVlanCurrentEgressPorts. The default value of 2399 this object is a string of ones of appropriate length." 2400 REFERENCE 2401 "IEEE 802.1Q/D11 Table 8-5, ISO/IEC 15802-3 Table 7-5" 2402 ::= { dot1qStaticUnicastEntry 3 } 2404 dot1qStaticUnicastStatus OBJECT-TYPE 2405 SYNTAX INTEGER { 2406 other(1), 2407 invalid(2), 2408 permanent(3), 2409 deleteOnReset(4), 2410 deleteOnTimeout(5) 2411 } 2412 MAX-ACCESS read-write 2413 STATUS current 2414 DESCRIPTION 2415 "This object indicates the status of this entry. 2416 other(1) - this entry is currently in use but 2417 the conditions under which it will remain 2418 so differ from the following values. 2419 invalid(2) - writing this value to the object 2420 removes the corresponding entry. 2421 permanent(3) - this entry is currently in use 2422 and will remain so after the next reset of 2423 the bridge. 2424 deleteOnReset(4) - this entry is currently in 2425 use and will remain so until the next 2426 reset of the bridge. 2427 deleteOnTimeout(5) - this entry is currently in 2428 use and will remain so until it is aged out." 2429 DEFVAL { permanent } 2430 ::= { dot1qStaticUnicastEntry 4 } 2432 dot1qStaticMulticastTable OBJECT-TYPE 2433 SYNTAX SEQUENCE OF Dot1qStaticMulticastEntry 2434 MAX-ACCESS not-accessible 2435 STATUS current 2436 DESCRIPTION 2437 "A table containing filtering information for Multicast 2438 and Broadcast MAC addresses for each VLAN, configured 2439 into the device by (local or network) management 2440 specifying the set of ports to which frames received 2441 from specific ports and containing specific Multicast 2442 and Broadcast destination addresses are allowed to be 2443 forwarded. A value of zero in this table as the port 2444 number from which frames with a specific destination 2445 address are received, is used to specify all ports for 2446 which there is no specific entry in this table for that 2447 particular destination address. Entries are valid for 2448 Multicast and Broadcast addresses only." 2449 REFERENCE 2450 "IEEE 802.1Q/D11 Section 12.7.7, 2451 ISO/IEC 15802-3 Section 7.9.1" 2452 ::= { dot1qStatic 2 } 2454 dot1qStaticMulticastEntry OBJECT-TYPE 2455 SYNTAX Dot1qStaticMulticastEntry 2456 MAX-ACCESS not-accessible 2457 STATUS current 2458 DESCRIPTION 2459 "Filtering information configured into the device by 2460 (local or network) management specifying the set of 2461 ports to which frames received from this specific port 2462 for this VLAN and containing this Multicast or Broadcast 2463 destination address are allowed to be forwarded." 2464 INDEX { 2465 dot1qVlanIndex, 2466 dot1qStaticMulticastAddress, 2467 dot1qStaticMulticastReceivePort 2469 } 2470 ::= { dot1qStaticMulticastTable 1 } 2472 Dot1qStaticMulticastEntry ::= 2473 SEQUENCE { 2474 dot1qStaticMulticastAddress 2475 MacAddress, 2476 dot1qStaticMulticastReceivePort 2477 INTEGER, 2478 dot1qStaticMulticastStaticEgressPorts 2479 PortList, 2480 dot1qStaticMulticastForbiddenEgressPorts 2481 PortList, 2482 dot1qStaticMulticastStatus 2483 INTEGER 2484 } 2486 dot1qStaticMulticastAddress OBJECT-TYPE 2487 SYNTAX MacAddress 2488 MAX-ACCESS not-accessible 2489 STATUS current 2490 DESCRIPTION 2491 "The destination MAC address in a frame to which this 2492 entry's filtering information applies. This object must 2493 take the value of a Multicast or Broadcast address." 2494 ::= { dot1qStaticMulticastEntry 1 } 2496 dot1qStaticMulticastReceivePort OBJECT-TYPE 2497 SYNTAX INTEGER (0..65535) 2498 MAX-ACCESS not-accessible 2499 STATUS current 2500 DESCRIPTION 2501 "Either the value '0', or the port number of the port 2502 from which a frame must be received in order for this 2503 entry's filtering information to apply. A value of zero 2504 indicates that this entry applies on all ports of the 2505 device for which there is no other applicable entry." 2506 ::= { dot1qStaticMulticastEntry 2 } 2508 dot1qStaticMulticastStaticEgressPorts OBJECT-TYPE 2509 SYNTAX PortList 2510 MAX-ACCESS read-write 2511 STATUS current 2512 DESCRIPTION 2513 "The set of ports to which frames received from a 2514 specific port and destined for a specific Multicast or 2515 Broadcast MAC address must be forwarded, regardless of 2516 any dynamic information e.g. from GMRP. A port may not 2517 be added in this set if it is already a member of the 2518 set of ports in dot1qStaticMulticastForbiddenEgressPorts. 2519 The default value of this object is a string of ones of 2520 appropriate length." 2521 ::= { dot1qStaticMulticastEntry 3 } 2523 dot1qStaticMulticastForbiddenEgressPorts OBJECT-TYPE 2524 SYNTAX PortList 2525 MAX-ACCESS read-write 2526 STATUS current 2527 DESCRIPTION 2528 "The set of ports to which frames received from a 2529 specific port and destined for a specific Multicast or 2530 Broadcast MAC address must not be forwarded, regardless 2531 of any dynamic information e.g. from GMRP. A port may 2532 not be added in this set if it is already a member of the 2533 set of ports in dot1qStaticMulticastStaticEgressPorts. 2534 The default value of this object is a string of zeros of 2535 appropriate length." 2536 ::= { dot1qStaticMulticastEntry 4 } 2538 dot1qStaticMulticastStatus OBJECT-TYPE 2539 SYNTAX INTEGER { 2540 other(1), 2541 invalid(2), 2542 permanent(3), 2543 deleteOnReset(4), 2544 deleteOnTimeout(5) 2545 } 2546 MAX-ACCESS read-write 2547 STATUS current 2548 DESCRIPTION 2549 "This object indicates the status of this entry. 2550 other(1) - this entry is currently in use but 2551 the conditions under which it will remain 2552 so differ from the following values. 2553 invalid(2) - writing this value to the object 2554 removes the corresponding entry. 2555 permanent(3) - this entry is currently in use 2556 and will remain so after the next reset of 2557 the bridge. 2558 deleteOnReset(4) - this entry is currently in 2559 use and will remain so until the next 2560 reset of the bridge. 2561 deleteOnTimeout(5) - this entry is currently in 2562 use and will remain so until it is aged out." 2563 DEFVAL { permanent } 2564 ::= { dot1qStaticMulticastEntry 5 } 2566 -- ------------------------------------------------------------- 2567 -- The Current VLAN Database 2568 -- ------------------------------------------------------------- 2570 dot1qVlanNumDeletes OBJECT-TYPE 2571 SYNTAX Counter32 2572 MAX-ACCESS read-only 2573 STATUS current 2574 DESCRIPTION 2575 "The number of times a VLAN entry has been deleted from 2576 the dot1qVlanCurrentTable (for any reason). If an entry 2577 is deleted, then inserted, and then deleted, this 2578 counter will be incremented by 2." 2579 ::= { dot1qVlan 1 } 2581 dot1qVlanCurrentTable OBJECT-TYPE 2582 SYNTAX SEQUENCE OF Dot1qVlanCurrentEntry 2583 MAX-ACCESS not-accessible 2584 STATUS current 2585 DESCRIPTION 2586 "A table containing current configuration information 2587 for each VLAN currently configured into the device by 2588 (local or network) management, or dynamically created 2589 as a result of GVRP requests received." 2590 ::= { dot1qVlan 2 } 2592 dot1qVlanCurrentEntry OBJECT-TYPE 2593 SYNTAX Dot1qVlanCurrentEntry 2594 MAX-ACCESS not-accessible 2595 STATUS current 2596 DESCRIPTION 2597 "Information for a VLAN configured into the device by 2598 (local or network) management, or dynamically created 2599 as a result of GVRP requests received." 2600 INDEX { dot1qVlanTimeMark, dot1qVlanIndex } 2601 ::= { dot1qVlanCurrentTable 1 } 2603 Dot1qVlanCurrentEntry ::= 2604 SEQUENCE { 2605 dot1qVlanTimeMark 2606 TimeFilter, 2607 dot1qVlanIndex 2608 VlanIndex, 2609 dot1qVlanFdbId 2610 Unsigned32, 2611 dot1qVlanCurrentEgressPorts 2612 PortList, 2613 dot1qVlanCurrentUntaggedPorts 2614 PortList, 2615 dot1qVlanStatus 2616 INTEGER, 2617 dot1qVlanCreationTime 2618 TimeTicks 2619 } 2621 dot1qVlanTimeMark OBJECT-TYPE 2622 SYNTAX TimeFilter 2623 MAX-ACCESS not-accessible 2624 STATUS current 2625 DESCRIPTION 2626 "A TimeFilter for this entry. See the TimeFilter 2627 textual convention to see how this works." 2628 ::= { dot1qVlanCurrentEntry 1 } 2630 dot1qVlanIndex OBJECT-TYPE 2631 SYNTAX VlanIndex 2632 MAX-ACCESS not-accessible 2633 STATUS current 2634 DESCRIPTION 2635 "The VLAN-ID or other identifier refering to this VLAN." 2636 ::= { dot1qVlanCurrentEntry 2 } 2638 dot1qVlanFdbId OBJECT-TYPE 2639 SYNTAX Unsigned32 2640 MAX-ACCESS read-only 2641 STATUS current 2642 DESCRIPTION 2643 "The Filtering Database used by this VLAN. This is one 2644 of the dot1qFdbId values in the dot1qFdbTable. This 2645 value is allocated automatically by the device whenever 2646 the VLAN is created: either dynamically by GVRP, or by 2647 management, in dot1qVlanStaticTable. Allocation of this 2648 value follows the learning constraints defined for this 2649 VLAN in dot1qLearningConstraintsTable." 2650 ::= { dot1qVlanCurrentEntry 3 } 2652 dot1qVlanCurrentEgressPorts OBJECT-TYPE 2653 SYNTAX PortList 2654 MAX-ACCESS read-only 2655 STATUS current 2656 DESCRIPTION 2657 "The set of ports which are transmitting traffic for 2658 this VLAN as either tagged or untagged frames." 2659 REFERENCE 2660 "IEEE 802.1Q/D11 Section 12.10.2.1" 2661 ::= { dot1qVlanCurrentEntry 4 } 2663 dot1qVlanCurrentUntaggedPorts OBJECT-TYPE 2664 SYNTAX PortList 2665 MAX-ACCESS read-only 2666 STATUS current 2667 DESCRIPTION 2668 "The set of ports which are transmitting traffic for 2669 this VLAN as untagged frames." 2670 REFERENCE 2671 "IEEE 802.1Q/D11 Section 12.10.2.1" 2672 ::= { dot1qVlanCurrentEntry 5 } 2674 dot1qVlanStatus OBJECT-TYPE 2675 SYNTAX INTEGER { 2676 other(1), 2677 permanent(2), 2678 dynamicGvrp(3) 2679 } 2680 MAX-ACCESS read-only 2681 STATUS current 2682 DESCRIPTION 2683 "This object indicates the status of this entry. 2684 other(1) - this entry is currently in use but the 2685 conditions under which it will remain so differ 2686 from the following values. 2687 permanent(2) - this entry, corresponding to an entry 2688 in dot1qVlanStaticTable, is currently in use and 2689 will remain so after the next reset of the 2690 device. The port lists for this entry include 2691 ports from the equivalent dot1qVlanStaticTable 2692 entry and ports learnt dynamically. 2693 dynamicGvrp(3) - this entry is currently in use 2694 and will remain so until removed by GVRP. There 2695 is no static entry for this VLAN and it will be 2696 removed when the last port leaves the VLAN." 2697 ::= { dot1qVlanCurrentEntry 6 } 2699 dot1qVlanCreationTime OBJECT-TYPE 2700 SYNTAX TimeTicks 2701 MAX-ACCESS read-only 2702 STATUS current 2703 DESCRIPTION 2704 "The value of sysUpTime when this VLAN was created." 2705 ::= { dot1qVlanCurrentEntry 7 } 2707 -- ------------------------------------------------------------- 2708 -- The Static VLAN Database 2709 -- ------------------------------------------------------------- 2711 dot1qVlanStaticTable OBJECT-TYPE 2712 SYNTAX SEQUENCE OF Dot1qVlanStaticEntry 2713 MAX-ACCESS not-accessible 2714 STATUS current 2715 DESCRIPTION 2716 "A table containing static configuration information for 2717 each VLAN configured into the device by (local or 2718 network) management. All entries are permanent and will 2719 be restored after the device is reset." 2720 ::= { dot1qVlan 3 } 2722 dot1qVlanStaticEntry OBJECT-TYPE 2723 SYNTAX Dot1qVlanStaticEntry 2724 MAX-ACCESS not-accessible 2725 STATUS current 2726 DESCRIPTION 2727 "Static information for a VLAN configured into the 2728 device by (local or network) management." 2729 INDEX { dot1qVlanIndex } 2730 ::= { dot1qVlanStaticTable 1 } 2732 Dot1qVlanStaticEntry ::= 2733 SEQUENCE { 2734 dot1qVlanStaticName 2735 SnmpAdminString, 2736 dot1qVlanStaticEgressPorts 2737 PortList, 2738 dot1qVlanForbiddenEgressPorts 2739 PortList, 2740 dot1qVlanStaticUntaggedPorts 2741 PortList, 2742 dot1qVlanStaticRowStatus 2743 RowStatus 2744 } 2746 dot1qVlanStaticName OBJECT-TYPE 2747 SYNTAX SnmpAdminString (SIZE (0..32)) 2748 MAX-ACCESS read-create 2749 STATUS current 2750 DESCRIPTION 2751 "An administratively assigned string, which may be used 2752 to identify the VLAN." 2753 REFERENCE 2754 "IEEE 802.1Q/D11 Section 12.10.2.1" 2755 ::= { dot1qVlanStaticEntry 1 } 2757 dot1qVlanStaticEgressPorts OBJECT-TYPE 2758 SYNTAX PortList 2759 MAX-ACCESS read-create 2760 STATUS current 2761 DESCRIPTION 2762 "The set of ports which are permanently assigned to the 2763 egress list for this VLAN by management. Changes to a 2764 bit in this object affect the per-port per-VLAN 2765 Registrar control for Registration Fixed for the 2766 relevant GVRP state machine on each port. A port may 2767 not be added in this set if it is already a member of 2768 the set of ports in dot1qVlanForbiddenEgressPorts. The 2769 default value of this object is a string of zeros of 2770 appropriate length, indicating not fixed." 2771 REFERENCE 2772 "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" 2773 ::= { dot1qVlanStaticEntry 2 } 2775 dot1qVlanForbiddenEgressPorts OBJECT-TYPE 2776 SYNTAX PortList 2777 MAX-ACCESS read-create 2778 STATUS current 2779 DESCRIPTION 2780 "The set of ports which are prohibited by management 2781 from being included in the egress list for this VLAN. 2782 Changes to this object that cause a port to be included 2783 or excluded affect the per-port per-VLAN Registrar 2784 control for Registration Forbidden for the relevant GVRP 2785 state machine on each port. A port may not be added in 2786 this set if it is already a member of the set of ports 2787 in dot1qVlanStaticEgressPorts. The default value of 2788 this object is a string of zeros of appropriate length, 2789 excluding all ports from the forbidden set." 2790 REFERENCE 2791 "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" 2792 ::= { dot1qVlanStaticEntry 3 } 2794 dot1qVlanStaticUntaggedPorts OBJECT-TYPE 2795 SYNTAX PortList 2796 MAX-ACCESS read-create 2797 STATUS current 2798 DESCRIPTION 2799 "The set of ports which should transmit egress packets 2800 for this VLAN as untagged. The default value of this 2801 object for the default VLAN (dot1qVlanIndex = 1) is a string 2802 of appropriate length including all ports. There is no 2803 specified default for other VLANs. If a device agent cannot 2804 support the set of ports being set then it will reject the 2805 set operation with an error. An example might be if a 2806 manager attempts to set more than one VLAN to be untagged 2807 on egress where the device does not support this IEEE 802.1Q 2808 option." 2809 REFERENCE 2810 "IEEE 802.1Q/D11 Section 12.10.2.1" 2811 ::= { dot1qVlanStaticEntry 4 } 2813 dot1qVlanStaticRowStatus OBJECT-TYPE 2814 SYNTAX RowStatus 2815 MAX-ACCESS read-create 2816 STATUS current 2817 DESCRIPTION 2818 "This object indicates the status of this entry." 2819 ::= { dot1qVlanStaticEntry 5 } 2821 dot1qNextFreeLocalVlanIndex OBJECT-TYPE 2822 SYNTAX INTEGER (0|4096..2147483647) 2823 MAX-ACCESS read-only 2824 STATUS current 2825 DESCRIPTION 2826 "The next available value for dot1qVlanIndex of a local 2827 VLAN entry in dot1qVlanStaticTable. This will report 2828 values >=4096 if a new Local VLAN may be created or else 2829 the value 0 if this is not possible. 2831 A row creation operation in this table for an entry with a local 2832 VlanIndex value may fail if the current value of this object 2833 is not used as the index. Even if the value read is used, 2834 there is no guarantee that it will still be the valid index 2835 when the create operation is attempted - another manager may 2836 have already got in during the intervening time interval. 2837 In this case, dot1qNextFreeLocalVlanIndex should be re-read 2838 and the creation re-tried with the new value." 2840 This value will automatically change when the current value is 2841 used to create a new row." 2842 ::= { dot1qVlan 4 } 2844 -- ------------------------------------------------------------- 2845 -- The VLAN Port Configuration Table 2846 -- ------------------------------------------------------------- 2848 dot1qPortVlanTable OBJECT-TYPE 2849 SYNTAX SEQUENCE OF Dot1qPortVlanEntry 2850 MAX-ACCESS not-accessible 2851 STATUS current 2852 DESCRIPTION 2853 "A table containing per port control and status 2854 information for VLAN configuration in the device." 2855 ::= { dot1qVlan 5 } 2857 dot1qPortVlanEntry OBJECT-TYPE 2858 SYNTAX Dot1qPortVlanEntry 2859 MAX-ACCESS not-accessible 2860 STATUS current 2861 DESCRIPTION 2862 "Information controlling VLAN configuration for a port 2863 on the device. This is indexed by dot1dBasePort." 2864 AUGMENTS { dot1dBasePortEntry } 2865 ::= { dot1qPortVlanTable 1 } 2867 Dot1qPortVlanEntry ::= 2868 SEQUENCE { 2869 dot1qPvid 2870 VlanIndex, 2871 dot1qPortAcceptableFrameTypes 2872 INTEGER, 2873 dot1qPortIngressFiltering 2874 TruthValue, 2875 dot1qPortGvrpStatus 2876 EnabledStatus, 2877 dot1qPortGvrpFailedRegistrations 2878 Counter32, 2879 dot1qPortGvrpLastPduOrigin 2880 MacAddress 2881 } 2883 dot1qPvid OBJECT-TYPE 2884 SYNTAX VlanIndex 2885 MAX-ACCESS read-write 2886 STATUS current 2887 DESCRIPTION 2888 "The PVID, the VLAN ID assigned to untagged frames or 2889 Prority-Tagged frames received on this port." 2890 REFERENCE 2891 "IEEE 802.1Q/D11 Section 12.10.1.1" 2892 DEFVAL { 1 } 2893 ::= { dot1qPortVlanEntry 1 } 2895 dot1qPortAcceptableFrameTypes OBJECT-TYPE 2896 SYNTAX INTEGER { 2897 admitAll(1), 2898 admitOnlyVlanTagged(2) 2899 } 2900 MAX-ACCESS read-write 2901 STATUS current 2902 DESCRIPTION 2903 "When this is admitOnlyVlanTagged(2) the device will 2904 discard untagged frames or Prority-Tagged frames 2905 received on this port. When admitAll(1), untagged 2906 frames or Prority-Tagged frames received on this port 2907 will be accepted and assigned to the PVID for this port. 2909 This control does not affect VLAN independent BPDU 2910 frames, such as GVRP and STP. It does affect VLAN 2911 dependent BPDU frames, such as GMRP." 2912 REFERENCE 2913 "IEEE 802.1Q/D11 Section 12.10.1.3" 2914 DEFVAL { admitAll } 2915 ::= { dot1qPortVlanEntry 2 } 2917 dot1qPortIngressFiltering OBJECT-TYPE 2918 SYNTAX TruthValue 2919 MAX-ACCESS read-write 2920 STATUS current 2921 DESCRIPTION 2922 "When this is true(1) the device will discard incoming 2923 frames for VLANs which do not include this Port in its 2924 Member set. When false(2), the port will accept all 2925 incoming frames. 2927 This control does not affect VLAN independent BPDU 2928 frames, such as GVRP and STP. It does affect VLAN 2929 dependent BPDU frames, such as GMRP." 2930 REFERENCE 2931 "IEEE 802.1Q/D11 Section 12.10.1.4" 2932 DEFVAL { false } 2933 ::= { dot1qPortVlanEntry 3 } 2935 dot1qPortGvrpStatus OBJECT-TYPE 2936 SYNTAX EnabledStatus 2937 MAX-ACCESS read-write 2938 STATUS current 2939 DESCRIPTION 2940 "The state of GVRP operation on this port. The value 2941 enabled(1) indicates that GVRP is enabled on this port, 2942 as long as dot1qGvrpStatus is also enabled for this 2943 device. When disabled(2) but dot1qGvrpStatus is still 2944 enabled for the device, GVRP is disabled on this port: 2945 any GVRP packets received will be silently discarded and 2946 no GVRP registrations will be propagated from other 2947 ports. This object affects all GVRP Applicant and 2948 Registrar state machines on this port. A transition 2949 from disabled(2) to enabled(1) will cause a reset of all 2950 GVRP state machines on this port." 2951 DEFVAL { enabled } 2952 ::= { dot1qPortVlanEntry 4 } 2954 dot1qPortGvrpFailedRegistrations OBJECT-TYPE 2955 SYNTAX Counter32 2956 MAX-ACCESS read-only 2957 STATUS current 2958 DESCRIPTION 2959 "The total number of failed GVRP registrations, for any 2960 reason, on this port." 2961 ::= { dot1qPortVlanEntry 5 } 2963 dot1qPortGvrpLastPduOrigin OBJECT-TYPE 2964 SYNTAX MacAddress 2965 MAX-ACCESS read-only 2966 STATUS current 2967 DESCRIPTION 2968 "The Source MAC Address of the last GVRP message 2969 received on this port." 2970 ::= { dot1qPortVlanEntry 6 } 2972 -- ------------------------------------------------------------- 2973 -- Per port VLAN Statistics Table 2974 -- ------------------------------------------------------------- 2976 dot1qPortVlanStatisticsTable OBJECT-TYPE 2977 SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry 2978 MAX-ACCESS not-accessible 2979 STATUS current 2980 DESCRIPTION 2981 "A table containing per-port, per-VLAN statistics for 2982 traffic received. Separate objects are provided for both the 2983 most-significant and least-significant bits of statistics 2984 counters for ports that are associated with this transparent 2985 bridge. The most-significant bit objects are only required on 2986 high capacity interfaces, as defined in the conformance clauses 2987 for these objects. This mechanism is provided as a way to read 2988 64-bit counters for agents which support only SNMPv1. 2990 Note that the reporting of most-significant and least-significant 2991 counter bits separately runs the risk of missing an overflow of 2992 the lower bits in the interval between sampling. The manager 2993 must be aware of this possibility, even within the same 2994 varbindlist, when interpreting the results of a request or 2995 asynchronous notification." 2996 ::= { dot1qVlan 6 } 2998 dot1qPortVlanStatisticsEntry OBJECT-TYPE 2999 SYNTAX Dot1qPortVlanStatisticsEntry 3000 MAX-ACCESS not-accessible 3001 STATUS current 3002 DESCRIPTION 3003 "Traffic statistics for a VLAN on an interface." 3004 INDEX { dot1dBasePort, dot1qVlanIndex } 3005 ::= { dot1qPortVlanStatisticsTable 1 } 3007 Dot1qPortVlanStatisticsEntry ::= 3008 SEQUENCE { 3009 dot1qTpVlanPortInFrames 3010 Counter32, 3011 dot1qTpVlanPortOutFrames 3012 Counter32, 3013 dot1qTpVlanPortInDiscards 3014 Counter32, 3015 dot1qTpVlanPortInOverflowFrames 3016 Counter32, 3017 dot1qTpVlanPortOutOverflowFrames 3018 Counter32, 3019 dot1qTpVlanPortInOverflowDiscards 3020 Counter32 3021 } 3023 dot1qTpVlanPortInFrames OBJECT-TYPE 3024 SYNTAX Counter32 3025 MAX-ACCESS read-only 3026 STATUS current 3027 DESCRIPTION 3028 "The number of valid frames received by this port from 3029 its segment which were classified as belonging to this 3030 VLAN. Note that a frame received on this port is 3031 counted by this object if and only if it is for a 3032 protocol being processed by the local forwarding process 3033 for this VLAN. This object includes received bridge 3034 management frames classified as belonging to this VLAN 3035 (e.g. GMRP, but not GVRP or STP)." 3036 REFERENCE 3037 "IEEE 802.1Q/D11 Section 12.6.1.1.3(a)" 3038 ::= { dot1qPortVlanStatisticsEntry 1 } 3040 dot1qTpVlanPortOutFrames OBJECT-TYPE 3041 SYNTAX Counter32 3042 MAX-ACCESS read-only 3043 STATUS current 3044 DESCRIPTION 3045 "The number of valid frames transmitted by this port to 3046 its segment from the local forwarding process for this 3047 VLAN. This includes bridge management frames originated 3048 by this device which are classified as belonging to this 3049 VLAN (e.g. GMRP, but not GVRP or STP)." 3050 REFERENCE 3051 "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" 3052 ::= { dot1qPortVlanStatisticsEntry 2 } 3054 dot1qTpVlanPortInDiscards OBJECT-TYPE 3055 SYNTAX Counter32 3056 MAX-ACCESS read-only 3057 STATUS current 3058 DESCRIPTION 3059 "The number of valid frames received by this port from 3060 its segment which were classified as belonging to this 3061 VLAN which were discarded due to VLAN related reasons. 3062 Specifically, the IEEE 802.1Q counters for Discard 3063 Inbound and Discard on Ingress Filtering." 3064 REFERENCE 3065 "IEEE 802.1Q/D11 Section 12.6.1.1.3" 3066 ::= { dot1qPortVlanStatisticsEntry 3 } 3068 dot1qTpVlanPortInOverflowFrames OBJECT-TYPE 3069 SYNTAX Counter32 3070 MAX-ACCESS read-only 3071 STATUS current 3072 DESCRIPTION 3073 "The number of times the associated 3074 dot1qTpVlanPortInFrames counter has overflowed." 3075 REFERENCE 3076 "ISO/IEC 15802-3 Section 14.6.1.1.3" 3077 ::= { dot1qPortVlanStatisticsEntry 4 } 3079 dot1qTpVlanPortOutOverflowFrames OBJECT-TYPE 3080 SYNTAX Counter32 3081 MAX-ACCESS read-only 3082 STATUS current 3083 DESCRIPTION 3084 "The number of times the associated 3085 dot1qTpVlanPortOutFrames counter has overflowed." 3086 REFERENCE 3087 "ISO/IEC 15802-3 Section 14.6.1.1.3" 3088 ::= { dot1qPortVlanStatisticsEntry 5 } 3090 dot1qTpVlanPortInOverflowDiscards OBJECT-TYPE 3091 SYNTAX Counter32 3092 MAX-ACCESS read-only 3093 STATUS current 3094 DESCRIPTION 3095 "The number of times the associated 3096 dot1qTpVlanPortInDiscards counter has overflowed." 3097 REFERENCE 3098 "ISO/IEC 15802-3 Section 14.6.1.1.3" 3100 ::= { dot1qPortVlanStatisticsEntry 6 } 3102 dot1qPortVlanHCStatisticsTable OBJECT-TYPE 3103 SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry 3104 MAX-ACCESS not-accessible 3105 STATUS current 3106 DESCRIPTION 3107 "A table containing per port, per VLAN statistics for 3108 traffic received on high capacity interfaces." 3109 ::= { dot1qVlan 7 } 3111 dot1qPortVlanHCStatisticsEntry OBJECT-TYPE 3112 SYNTAX Dot1qPortVlanHCStatisticsEntry 3113 MAX-ACCESS not-accessible 3114 STATUS current 3115 DESCRIPTION 3116 "Traffic statistics for a VLAN on a high capacity 3117 interface." 3118 INDEX { dot1dBasePort, dot1qVlanIndex } 3119 ::= { dot1qPortVlanHCStatisticsTable 1 } 3121 Dot1qPortVlanHCStatisticsEntry ::= 3122 SEQUENCE { 3123 dot1qTpVlanPortHCInFrames 3124 Counter64, 3125 dot1qTpVlanPortHCOutFrames 3126 Counter64, 3127 dot1qTpVlanPortHCInDiscards 3128 Counter64 3129 } 3131 dot1qTpVlanPortHCInFrames OBJECT-TYPE 3132 SYNTAX Counter64 3133 MAX-ACCESS read-only 3134 STATUS current 3135 DESCRIPTION 3136 "The number of valid frames received by this port from 3137 its segment which were classified as belonging to this 3138 VLAN. Note that a frame received on this port is 3139 counted by this object if and only if it is for a 3140 protocol being processed by the local forwarding process 3141 for this VLAN. This object includes received bridge 3142 management frames classified as belonging to this VLAN 3143 (e.g. GMRP, but not GVRP or STP)." 3144 REFERENCE 3145 "IEEE 802.1Q/D11 Section 12.6.1.1.3(a)" 3146 ::= { dot1qPortVlanHCStatisticsEntry 1 } 3148 dot1qTpVlanPortHCOutFrames OBJECT-TYPE 3149 SYNTAX Counter64 3150 MAX-ACCESS read-only 3151 STATUS current 3152 DESCRIPTION 3153 "The number of valid frames transmitted by this port to 3154 its segment from the local forwarding process for this 3155 VLAN. This includes bridge management frames originated 3156 by this device which are classified as belonging to this 3157 VLAN (e.g. GMRP, but not GVRP or STP)." 3158 REFERENCE 3159 "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" 3160 ::= { dot1qPortVlanHCStatisticsEntry 2 } 3162 dot1qTpVlanPortHCInDiscards OBJECT-TYPE 3163 SYNTAX Counter64 3164 MAX-ACCESS read-only 3165 STATUS current 3166 DESCRIPTION 3167 "The number of valid frames received by this port from 3168 its segment which were classified as belonging to this 3169 VLAN which were discarded due to VLAN related reasons. 3170 Specifically, the IEEE 802.1Q counters for Discard 3171 Inbound and Discard on Ingress Filtering." 3172 REFERENCE 3173 "IEEE 802.1Q/D11 Section 12.6.1.1.3" 3174 ::= { dot1qPortVlanHCStatisticsEntry 3 } 3176 -- ------------------------------------------------------------- 3177 -- The VLAN Learning Constraints Table 3178 -- ------------------------------------------------------------- 3180 dot1qLearningConstraintsTable OBJECT-TYPE 3181 SYNTAX SEQUENCE OF Dot1qLearningConstraintsEntry 3182 MAX-ACCESS not-accessible 3183 STATUS current 3184 DESCRIPTION 3185 "A table containing learning constraints for sets of 3186 Shared and Independendent VLANs." 3187 REFERENCE 3188 "IEEE 802.1Q/D11 Section 12.10.3.1" 3189 ::= { dot1qVlan 8 } 3191 dot1qLearningConstraintsEntry OBJECT-TYPE 3192 SYNTAX Dot1qLearningConstraintsEntry 3193 MAX-ACCESS not-accessible 3194 STATUS current 3195 DESCRIPTION 3196 "A learning constraint defined for a VLAN." 3197 INDEX { dot1qConstraintVlan, dot1qConstraintSet } 3198 ::= { dot1qLearningConstraintsTable 1 } 3200 Dot1qLearningConstraintsEntry ::= 3201 SEQUENCE { 3202 dot1qConstraintVlan 3203 VlanIndex, 3204 dot1qConstraintSet 3205 INTEGER, 3206 dot1qConstraintType 3207 INTEGER, 3208 dot1qConstraintStatus 3209 RowStatus 3210 } 3212 dot1qConstraintVlan OBJECT-TYPE 3213 SYNTAX VlanIndex 3214 MAX-ACCESS not-accessible 3215 STATUS current 3216 DESCRIPTION 3217 "The index of the row in dot1qVlanCurrentTable for the 3218 VLAN constrained by this entry." 3219 ::= { dot1qLearningConstraintsEntry 1 } 3221 dot1qConstraintSet OBJECT-TYPE 3222 SYNTAX INTEGER (0..65535) 3223 MAX-ACCESS not-accessible 3224 STATUS current 3225 DESCRIPTION 3226 "The identity of the constraint set to which 3227 dot1qConstraintVlan belongs. These values may be chosen 3228 by the management station." 3229 ::= { dot1qLearningConstraintsEntry 2 } 3231 dot1qConstraintType OBJECT-TYPE 3232 SYNTAX INTEGER { 3233 independent(1), 3234 shared(2) 3235 } 3237 MAX-ACCESS read-create 3238 STATUS current 3239 DESCRIPTION 3240 "The type of constraint this entry defines. 3241 independent(1) - the VLAN, dot1qConstraintVlan, 3242 uses an independent filtering database from all 3243 other VLANs in the same set, defined by 3244 dot1qConstraintSet. 3245 shared(2) - the VLAN, dot1qConstraintVlan, shares 3246 the same filtering database as all other VLANs 3247 in the same set, defined by dot1qConstraintSet." 3248 ::= { dot1qLearningConstraintsEntry 3 } 3250 dot1qConstraintStatus OBJECT-TYPE 3251 SYNTAX RowStatus 3252 MAX-ACCESS read-create 3253 STATUS current 3254 DESCRIPTION 3255 "The status of this entry." 3256 ::= { dot1qLearningConstraintsEntry 4 } 3258 dot1qConstraintSetDefault OBJECT-TYPE 3259 SYNTAX INTEGER (0..65535) 3260 MAX-ACCESS read-write 3261 STATUS current 3262 DESCRIPTION 3263 "The identity of the constraint set to which a VLAN 3264 belongs, if there is not an explicit entry for that VLAN 3265 in dot1qLearningConstraintsTable." 3266 ::= { dot1qVlan 9 } 3268 dot1qConstraintTypeDefault OBJECT-TYPE 3269 SYNTAX INTEGER { 3270 independent(1), 3271 shared(2) 3272 } 3273 MAX-ACCESS read-write 3274 STATUS current 3275 DESCRIPTION 3276 "The type of constraint set to which a VLAN belongs, if 3277 there is not an explicit entry for that VLAN in 3278 dot1qLearningConstraintsTable. The types are as defined 3279 for dot1qConstraintType." 3280 ::= { dot1qVlan 10 } 3282 -- ------------------------------------------------------------- 3283 -- IEEE 802.1Q MIB - Conformance Information 3284 -- ------------------------------------------------------------- 3286 qBridgeConformance OBJECT IDENTIFIER ::= { qBridgeMIB 2 } 3288 qBridgeGroups OBJECT IDENTIFIER ::= { qBridgeConformance 1 } 3290 qBridgeCompliances OBJECT IDENTIFIER 3291 ::= { qBridgeConformance 2 } 3293 -- ------------------------------------------------------------- 3294 -- units of conformance 3295 -- ------------------------------------------------------------- 3297 qBridgeBaseGroup OBJECT-GROUP 3298 OBJECTS { 3299 dot1qVlanVersionNumber, 3300 dot1qMaxVlanId, 3301 dot1qMaxSupportedVlans, 3302 dot1qNumVlans, 3303 dot1qGvrpStatus 3304 } 3305 STATUS current 3306 DESCRIPTION 3307 "A collection of objects providing device level control 3308 and status information for the Virtual LAN bridge 3309 services." 3310 ::= { qBridgeGroups 1 } 3312 qBridgeFdbUnicastGroup OBJECT-GROUP 3313 OBJECTS { 3314 dot1qFdbDynamicCount, 3315 dot1qTpFdbPort, 3316 dot1qTpFdbStatus 3317 } 3318 STATUS current 3319 DESCRIPTION 3320 "A collection of objects providing information about all 3321 unicast addresses, learnt dynamically or statically 3322 configured by management, in each Filtering Database." 3323 ::= { qBridgeGroups 2 } 3325 qBridgeFdbMulticastGroup OBJECT-GROUP 3326 OBJECTS { 3327 dot1qTpGroupEgressPorts, 3328 dot1qTpGroupLearnt 3329 } 3330 STATUS current 3331 DESCRIPTION 3332 "A collection of objects providing information about all 3333 multicast addresses, learnt dynamically or statically 3334 configured by management, in each Filtering Database." 3335 ::= { qBridgeGroups 3 } 3337 qBridgeServiceRequirementsGroup OBJECT-GROUP 3338 OBJECTS { 3339 dot1qForwardAllPorts, 3340 dot1qForwardAllStaticPorts, 3341 dot1qForwardAllForbiddenPorts, 3342 dot1qForwardUnregisteredPorts, 3343 dot1qForwardUnregisteredStaticPorts, 3344 dot1qForwardUnregisteredForbiddenPorts 3345 } 3346 STATUS current 3347 DESCRIPTION 3348 "A collection of objects providing information about 3349 service requirements, learnt dynamically or statically 3350 configured by management, in each Filtering Database." 3351 ::= { qBridgeGroups 4 } 3353 qBridgeFdbStaticGroup OBJECT-GROUP 3354 OBJECTS { 3355 dot1qStaticUnicastAllowedToGoTo, 3356 dot1qStaticUnicastStatus, 3357 dot1qStaticMulticastStaticEgressPorts, 3358 dot1qStaticMulticastForbiddenEgressPorts, 3359 dot1qStaticMulticastStatus 3360 } 3361 STATUS current 3362 DESCRIPTION 3363 "A collection of objects providing information about 3364 unicast and multicast addresses statically configured by 3365 management, in each Filtering Database or VLAN." 3366 ::= { qBridgeGroups 5 } 3368 qBridgeVlanGroup OBJECT-GROUP 3369 OBJECTS { 3370 dot1qVlanNumDeletes, 3371 dot1qVlanFdbId, 3372 dot1qVlanCurrentEgressPorts, 3373 dot1qVlanCurrentUntaggedPorts, 3374 dot1qVlanStatus, 3375 dot1qVlanCreationTime 3376 } 3377 STATUS current 3378 DESCRIPTION 3379 "A collection of objects providing information about 3380 all VLANs currently configured on this device." 3381 ::= { qBridgeGroups 6 } 3383 qBridgeVlanStaticGroup OBJECT-GROUP 3384 OBJECTS { 3385 dot1qVlanStaticName, 3386 dot1qVlanStaticEgressPorts, 3387 dot1qVlanForbiddenEgressPorts, 3388 dot1qVlanStaticUntaggedPorts, 3389 dot1qVlanStaticRowStatus, 3390 dot1qNextFreeLocalVlanIndex 3391 } 3392 STATUS current 3393 DESCRIPTION 3394 "A collection of objects providing information about 3395 VLANs statically configured by management." 3396 ::= { qBridgeGroups 7 } 3398 qBridgePortGroup OBJECT-GROUP 3399 OBJECTS { 3400 dot1qPvid, 3401 dot1qPortAcceptableFrameTypes, 3402 dot1qPortIngressFiltering, 3403 dot1qPortGvrpStatus, 3404 dot1qPortGvrpFailedRegistrations, 3405 dot1qPortGvrpLastPduOrigin 3406 } 3407 STATUS current 3408 DESCRIPTION 3409 "A collection of objects providing port level VLAN 3410 control and status information for all ports." 3411 ::= { qBridgeGroups 8 } 3413 qBridgeVlanStatisticsGroup OBJECT-GROUP 3414 OBJECTS { 3415 dot1qTpVlanPortInFrames, 3416 dot1qTpVlanPortOutFrames, 3417 dot1qTpVlanPortInDiscards 3418 } 3419 STATUS current 3420 DESCRIPTION 3421 "A collection of objects providing per-port packet 3422 statistics for all VLANs currently configured on this 3423 device." 3424 ::= { qBridgeGroups 9 } 3426 qBridgeVlanStatisticsOverflowGroup OBJECT-GROUP 3427 OBJECTS { 3428 dot1qTpVlanPortInOverflowFrames, 3429 dot1qTpVlanPortOutOverflowFrames, 3430 dot1qTpVlanPortInOverflowDiscards 3431 } 3432 STATUS current 3433 DESCRIPTION 3434 "A collection of objects providing overflow counters for 3435 per-port packet statistics for all VLANs currently configured 3436 on this device for high capacity interfaces, defined as those 3437 that have the value of the corresponding instance of 3438 ifSpeed greater than 650,000,000 bits/second." 3439 ::= { qBridgeGroups 10 } 3441 qBridgeVlanHCStatisticsGroup OBJECT-GROUP 3442 OBJECTS { 3443 dot1qTpVlanPortHCInFrames, 3444 dot1qTpVlanPortHCOutFrames, 3445 dot1qTpVlanPortHCInDiscards 3446 } 3447 STATUS current 3448 DESCRIPTION 3449 "A collection of objects providing per-port packet 3450 statistics for all VLANs currently configured on this 3451 device for high capacity interfaces, defined as those 3452 that have the value of the corresponding instance of 3453 ifSpeed greater than 650,000,000 bits/second." 3454 ::= { qBridgeGroups 11 } 3456 qBridgeLearningConstraintsGroup OBJECT-GROUP 3457 OBJECTS { 3458 dot1qConstraintType, 3459 dot1qConstraintStatus 3460 } 3461 STATUS current 3462 DESCRIPTION 3463 "A collection of objects defining the Filtering Database 3464 constraints all VLANs have with each other." 3465 ::= { qBridgeGroups 12 } 3467 qBridgeLearningConstraintDefaultGroup OBJECT-GROUP 3468 OBJECTS { 3469 dot1qConstraintSetDefault, 3470 dot1qConstraintTypeDefault 3471 } 3472 STATUS current 3473 DESCRIPTION 3474 "A collection of objects defining the default Filtering 3475 Database constraints for VLANs which have no specific 3476 constraints defined." 3477 ::= { qBridgeGroups 13 } 3479 -- ------------------------------------------------------------- 3480 -- compliance statements 3481 -- ------------------------------------------------------------- 3483 qBridgeCompliance MODULE-COMPLIANCE 3484 STATUS current 3485 DESCRIPTION 3486 "The compliance statement for device support of Virtual 3487 LAN Bridge services." 3489 MODULE 3490 MANDATORY-GROUPS { 3491 qBridgeBaseGroup, 3492 qBridgeVlanGroup, 3493 qBridgeVlanStaticGroup, 3494 qBridgePortGroup 3495 } 3497 GROUP qBridgeFdbUnicastGroup 3498 DESCRIPTION 3499 "This group is mandatory for bridges that implement 3500 802.1Q transparent bridging." 3502 GROUP qBridgeFdbMulticastGroup 3503 DESCRIPTION 3504 "This group is mandatory for bridges that implement 3505 802.1Q transparent bridging." 3507 GROUP qBridgeServiceRequirementsGroup 3508 DESCRIPTION 3509 "This group is mandatory for bridges that implement 3510 extended filtering services. All objects must be 3511 read-write if extended-filtering services are 3512 enabled." 3514 GROUP qBridgeFdbStaticGroup 3515 DESCRIPTION 3516 "This group is optional." 3518 GROUP qBridgeVlanStatisticsGroup 3519 DESCRIPTION 3520 "This group is optional as there may be significant 3521 implementation cost associated with its support." 3523 GROUP qBridgeVlanStatisticsOverflowGroup 3524 DESCRIPTION 3525 "This group is optional as there may be significant 3526 implementation cost associated with its support. It is most 3527 relevant for high capacity interfaces where the SNMP agent 3528 supports only SNMPv1." 3530 GROUP qBridgeVlanHCStatisticsGroup 3531 DESCRIPTION 3532 "This group is optional as there may be significant 3533 implementation cost associated with its support. It is most 3534 relevant for high capacity interfaces." 3536 GROUP qBridgeLearningConstraintsGroup 3537 DESCRIPTION 3538 "This group is mandatory for devices implementing 3539 both Independent VLAN Learning (IVL) and Shared 3540 VLAN Learning (SVL) modes of operation of the 3541 filtering database, as defined by IEEE 802.1Q." 3543 GROUP qBridgeLearningConstraintDefaultGroup 3544 DESCRIPTION 3545 "This group is mandatory for devices implementing 3546 both Independent VLAN Learning (IVL) and Shared 3547 VLAN Learning (SVL) modes of operation of the 3548 filtering database, as defined by IEEE 802.1Q." 3550 OBJECT dot1qPortAcceptableFrameTypes 3551 MIN-ACCESS read-only 3552 DESCRIPTION 3553 "Write access is not required as this is an optional 3554 capability in IEEE 802.1Q." 3556 OBJECT dot1qPortIngressFiltering 3557 MIN-ACCESS read-only 3558 DESCRIPTION 3559 "Write access is not required as this is an optional 3560 capability in IEEE 802.1Q." 3562 OBJECT dot1qConstraintSetDefault 3563 MIN-ACCESS read-only 3564 DESCRIPTION 3565 "Write access is not required as this is an optional 3566 capability in IEEE 802.1Q." 3568 OBJECT dot1qConstraintTypeDefault 3569 MIN-ACCESS read-only 3570 DESCRIPTION 3571 "Write access is not required as this is an optional 3572 capability in IEEE 802.1Q." 3574 ::= { qBridgeCompliances 1 } 3576 END 3578 6. Acknowledgments 3580 This document expands upon previous work which resulted in the original 3581 bridge MIB [BRIDGEMIB]. 3583 Much of the groundwork for this document was performed by the IEEE 802.1 3584 working group during the definition of the IEEE 802.1D updates [802.1D] 3585 and IEEE 802.1Q [802.1Q]. 3587 The authors wish to thank the members of the Bridge Working Group and 3588 David Harrington in particular for their many comments and suggestions 3589 which improved this effort. 3591 7. Security Considerations 3593 There are a number of management objects defined in this MIB that have a 3594 MAX-ACCESS clause of read-write and/or read-create. Such objects may be 3595 considered sensitive or vulnerable in some network environments. The 3596 support for SET operations in a non-secure environment without proper 3597 protection can have a negative effect on network operations. 3599 SNMPv1 by itself is not a secure environment. Even if the network 3600 itself is secure (for example by using IPSec), even then, there is no 3601 control as to who on the secure network is allowed to access and GET/SET 3602 (read/change/create/delete) the objects in this MIB. 3604 It is recommended that the implementers consider the security features 3605 as provided by the SNMPv3 framework. Specifically, the use of the User- 3606 based Security Model [USM] and the View-based Access Control Model 3607 [VACM] is recommended. 3609 It is then a customer/user responsibility to ensure that the SNMP entity 3610 giving access to an instance of this MIB, is properly configured to give 3611 access to the objects only to those principals (users) that have 3612 legitimate rights to indeed GET or SET (change/create/delete) them. 3614 8. References 3616 [ARCH] 3617 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 3618 Describing SNMP Management Frameworks", RFC 2571, April 1999 3620 [V1PROTO] 3621 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 3622 Management Protocol", STD 15, RFC 1157, May 1990. 3624 [V1SMI] 3625 Rose, M., and K. McCloghrie, "Structure and Identification of 3626 Management Information for TCP/IP-based Internets", STD 16, RFC 3627 1155, May 1990 3629 [V1CONCISE] 3630 Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 3631 1212, March 1991 3633 [V1TRAPS] 3634 M. Rose, "A Convention for Defining Traps for use with the SNMP", 3635 RFC 1215, March 1991 3637 [V2SMI] 3638 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 3639 and S. Waldbusser, "Structure of Management Information Version 2 3640 (SMIv2)", STD 58, RFC 2578, April 1999. 3642 [V2TC] 3643 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 3644 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 3645 2579, April 1999. 3647 [V2CONFORM] 3648 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 3649 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 3650 2580, April 1999. 3652 [V2COMMUNITY] 3653 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction 3654 to Community-based SNMPv2", RFC 1901, January 1996. 3656 [V2TRANS] 3657 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 3658 Mappings for Version 2 of the Simple Network Management Protocol 3659 (SNMPv2)", RFC 1906, January 1996. 3661 [V2PROTO] 3662 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Protocol 3663 Operations for Version 2 of the Simple Network Management Protocol 3664 (SNMPv2)", RFC 1905, January 1996. 3666 [V3INTRO] 3667 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to 3668 Version 3 of the Internet-standard Network Management Framework", 3669 RFC 2570, April 1999. 3671 [V3MPC] 3672 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 3673 Processing and Dispatching for the Simple Network Management 3674 Protocol (SNMP)", RFC 2572, April 1999. 3676 [V3USM] 3677 Blumenthal, U. and B. Wijnen, "The User-Based Security Model (USM) 3678 for Version 3 of the Simple Network Management Protocol (SNMPv3)", 3679 RFC 2574, April 1999. 3681 [V3APPS] 3682 Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, 3683 April 1999. 3685 [V3VACM] 3686 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 3687 Control Model for the Simple Network Management Protocol (SNMP)", 3688 RFC 2575, April 1999. 3690 [ASN1] 3691 Information processing systems - Open Systems Interconnection - 3692 Specification of Abstract Syntax Notation One (ASN.1), 3693 International Organization for Standardization, International 3694 Standard 8824, December 1987. 3696 [ASN1BER] 3697 Information processing systems - Open Systems Interconnection - 3698 Specification of Basic Encoding Rules for Abstract Notation One 3699 (ASN.1), International Organization for Standardization, 3700 International Standard 8825, December 1987. 3702 [802.1D-ORIG] 3703 ISO/IEC 10038, ANSI/IEEE Std 802.1D-1993 "MAC Bridges". 3705 [802.1D] 3706 "Information technology - Telecommunications and information 3707 exchange between systems - Local and metropolitan area networks - 3708 Common specifications - Part 3: Media Access Control (MAC) Bridges: 3709 Revision. This is a revision of ISO/IEC 10038: 1993, 802.1j-1992 3710 and 802.6k-1992. It incorporates P802.11c, P802.1p and P802.12e." 3711 ISO/IEC 15802-3: 1998. 3713 [802.1Q] 3714 ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and 3715 Metropolitan Area Networks: Virtual Bridged Local Area Networks", 3716 1998. 3718 [BRIDGEMIB] 3719 Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K., 3720 "Definitions of Managed Objects for Bridges", RFC 1493, July 1993. 3722 [INTERFACEMIB] 3723 McCloghrie, K., Kastenholz, F. "Evolution of the Interfaces Group 3724 of MIB-II", RFC 1573, January 1994. 3726 [SRBRIDGEMIB] 3727 Decker, E., McCloghrie, K., Langille, P., Rijsinghani, A. 3728 "Definitions of Managed Objects for Source Routing Bridges", RFC 3729 1525, September 1993 3731 [MIB2] 3732 McCloghrie K., and M. Rose, Editors, "Management Information Base 3733 for Network Management of TCP/IP-based internets", STD 17, RFC 3734 1213, March 1991. 3736 9. Authors' Addresses 3738 Les Bell 3739 3Com Europe Limited 3740 3Com Centre, Boundary Way 3741 Hemel Hempstead 3742 Herts. HP2 7YU 3743 UK 3744 Phone: +44 1442 438025 3745 EMail: Les_Bell@3Com.com 3747 Andrew Smith 3748 Extreme Networks 3749 3585 Monroe St. 3750 Santa Clara, CA 95051 3751 USA 3752 Phone: +1 408 579 2821 3753 EMail: andrew@extremenetworks.com 3755 Paul Langille 3756 Newbridge Networks 3757 5 Corporate Drive 3758 Andover, MA 01810 3759 USA 3760 Phone: +1 978 691 4665 3761 EMail: langille@newbridge.com 3763 Anil Rijhsinghani 3764 Cabletron Systems 3765 50 Minuteman Road 3766 Andover, MA 01810 3767 USA 3768 Phone: +1 978 684 1295 3769 EMail: anil@cabletron.com 3771 Keith McCloghrie 3772 cisco Systems, Inc. 3773 170 West Tasman Drive 3774 San Jose, CA 95134-1706 3775 USA 3776 Phone: +1 408 526 5260 3777 EMail: kzm@cisco.com 3779 Table of Contents 3781 1 The SNMP Management Framework ................................... 2 3782 2 Overview ........................................................ 4 3783 2.1 Scope ......................................................... 4 3784 3 Structure of MIBs ............................................... 5 3785 3.1 Structure of Extended Bridge MIB module ....................... 6 3786 3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ......... 6 3787 3.1.2 Relationship to IEEE 802.1Q Manageable Objects .............. 7 3788 3.1.3 The dot1dExtBase Group ...................................... 8 3789 3.1.4 The dot1dPriority Group ..................................... 8 3790 3.1.5 The dot1dGarp Group ......................................... 8 3791 3.1.6 The dot1dGmrp Group ......................................... 9 3792 3.1.7 The dot1dTpHCPortTable ...................................... 9 3793 3.1.8 The dot1dTpPortOverflowTable ................................ 9 3794 3.2 Structure of Virtual Bridge MIB module ........................ 9 3795 3.2.1 Relationship to IEEE 802.1Q Manageable Objects .............. 9 3796 3.2.2 The dot1qBase Group ......................................... 13 3797 3.2.3 The dot1qTp Group ........................................... 13 3798 3.2.4 The dot1qStatic Group ....................................... 13 3799 3.2.5 The dot1qVlan Group ......................................... 13 3800 3.3 Textual Conventions ........................................... 14 3801 3.4 Relationship to Other MIBs .................................... 14 3802 3.4.1 Relationship to the 'system' group .......................... 14 3803 3.4.2 Relation to Interfaces MIB .................................. 14 3804 3.4.2.1 Layering Model ............................................ 15 3805 3.4.2.2 ifStackTable .............................................. 16 3806 3.4.2.3 ifRcvAddressTable ......................................... 16 3807 3.4.3 Relation to Original Bridge MIB ............................. 17 3808 3.4.3.1 The dot1dBase Group ....................................... 17 3809 3.4.3.2 The dot1dStp Group ........................................ 17 3810 3.4.3.3 The dot1dTp Group ......................................... 17 3811 3.4.3.4 The dot1dStatic Group ..................................... 18 3812 3.4.3.5 Additions to the Original Bridge MIB ...................... 18 3813 4 Definitions for Extended Bridge MIB ............................. 20 3814 5 Definitions for Virtual Bridge MIB .............................. 42 3815 6 Acknowledgments ................................................. 83 3816 7 Security Considerations ......................................... 84 3817 8 References ...................................................... 84 3818 9 Authors' Addresses .............................................. 88 3819 10. Full Copyright 3821 Copyright (C) The Internet Society (1999). All Rights Reserved. 3823 This document and translations of it may be copied and furnished 3824 to others, and derivative works that comment on or otherwise 3825 explain it or assist in its implmentation may be prepared, copied, 3826 published and distributed, in whole or in part, without 3827 restriction of any kind, provided that the above copyright notice 3828 and this paragraph are included on all such copies and derivative 3829 works. However, this document itself may not be modified in any 3830 way, such as by removing the copyright notice or references to the 3831 Internet Society or other Internet organizations, except as needed 3832 for the purpose of developing Internet standards in which case the 3833 procedures for copyrights defined in the Internet Standards 3834 process must be followed, or as required to translate it into 3835 languages other than English. 3837 The limited permissions granted above are perpetual and will not 3838 be revoked by the Internet Society or its successors or assigns. 3840 This document and the information contained herein is provided on 3841 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 3842 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 3843 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 3844 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3845 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.