idnits 2.17.1 draft-ietf-bridge-ext-v2-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 4642. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4653. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4660. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4666. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 38), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 38. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 34 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 1 instance of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 998: '...e of this object MUST be retained acro...' RFC 2119 keyword, line 1019: '...e of this object MUST be retained acro...' RFC 2119 keyword, line 1126: '...e of this object MUST be retained acro...' RFC 2119 keyword, line 1138: '...e of this object MUST be retained acro...' RFC 2119 keyword, line 1197: '...e of this object MUST be retained acro...' (28 more instances...) == The 'Obsoletes: ' line in the draft header should list only the _numbers_ of the RFCs which will be obsoleted by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 282 has weird spacing: '...failure not...' == Line 517 has weird spacing: '...address coun...' == Line 522 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 (August 2005) is 6800 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) == Unused Reference: 'RFC2674' is defined on line 4467, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1493 (ref. 'BRIDGE-MIB') (Obsoleted by RFC 4188) ** Obsolete normative reference: RFC 2674 (Obsoleted by RFC 4363) -- Duplicate reference: RFC1493, mentioned in 'RFC1493', was also mentioned in 'BRIDGE-MIB'. -- Obsolete informational reference (is this intentional?): RFC 1493 (Obsoleted by RFC 4188) Summary: 8 errors (**), 0 flaws (~~), 9 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Bridge MIB extensions 2 August 2005 4 Internet Draft D. Levi 5 Expires February 2006 Nortel Networks 6 draft-ietf-bridge-ext-v2-07.txt D.Harrington 7 Obsoletes: RFC 2674 Effective Software 8 August 2005 10 Definitions of Managed Objects for Bridges with Traffic 11 Classes, Multicast Filtering and Virtual LAN Extensions 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "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 Copyright Notice 38 Copyright (C) The Internet Society (2005). All Rights Reserved. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in TCP/IP based internets. 44 In particular, it defines two MIB modules for managing the 45 capabilities of MAC bridges defined by the IEEE 802.1D-1998 (TM) MAC 46 Bridges and the IEEE 802.1Q-2003 (TM) Virtual LAN (VLAN) standards 47 for bridging between Local Area Network (LAN) segments. One MIB 48 module defines objects for managing the 'Traffic Classes' and 49 'Enhanced Multicast Filtering' components of IEEE 802.1D-1998 and 50 P802.1t-2001 (TM). The other MIB module defines objects for managing 51 VLANs, as specified in IEEE 802.1Q-2003, P802.1u (TM) and P802.1v 52 (TM). 54 Provisions are made for support of transparent bridging. Provisions 55 are also made so that these objects apply to bridges connected by 56 subnetworks other than LAN segments. 58 This memo supplements RFC 1493bis, and obsoletes RFC 2674. 59 (NOTE for RFC Ed.: all instances of 'RFC 1493bis' will need to be 60 updated to reflect the new RFC number for draft-ietf-bridge- 61 bridgemib-smiv2-10.txt) 63 Table of Contents 65 1 The Internet-Standard Management Framework ................... 4 66 2 Overview ..................................................... 4 67 2.1 Scope ...................................................... 5 68 3 Structure of MIBs ............................................ 5 69 3.1 Structure of Extended Bridge MIB module .................... 6 70 3.1.1 Relationship to IEEE 802.1D-1998 Manageable Objects ...... 6 71 3.1.2 Relationship to IEEE 802.1Q Manageable Objects ........... 8 72 3.1.3 The dot1dExtBase Subtree ................................. 8 73 3.1.4 The dot1dPriority Subtree ................................ 8 74 3.1.5 The dot1dGarp Subtree .................................... 9 75 3.1.6 The dot1dGmrp Subtree .................................... 9 76 3.1.7 The dot1dTpHCPortTable ................................... 9 77 3.1.8 The dot1dTpPortOverflowTable ............................. 9 78 3.2 Structure of Virtual Bridge MIB module ..................... 9 79 3.2.1 Relationship to IEEE 802.1Q Manageable Objects ........... 9 80 3.2.2 The dot1qBase Subtree .................................... 13 81 3.2.3 The dot1qTp Subtree ...................................... 13 82 3.2.4 The dot1qStatic Subtree .................................. 13 83 3.2.5 The dot1qVlan Subtree .................................... 14 84 3.3 Textual Conventions ........................................ 14 85 3.4 Relationship to Other MIBs ................................. 14 86 3.4.1 Relationship to the SNMPv2-MIB ........................... 15 87 3.4.2 Relationship to the IF-MIB ............................... 15 88 3.4.2.1 Layering Model ......................................... 16 89 3.4.2.2 ifStackTable ........................................... 17 90 3.4.2.3 ifRcvAddressTable ...................................... 17 91 3.4.3 Relationship to the BRIDGE-MIB ........................... 17 92 3.4.3.1 The dot1dBase Subtree .................................. 18 93 3.4.3.2 The dot1dStp Subtree ................................... 18 94 3.4.3.3 The dot1dTp Subtree .................................... 18 95 3.4.3.4 The dot1dStatic Subtree ................................ 19 96 3.4.3.5 Additions to the BRIDGE-MIB ............................ 19 97 4 Definitions for Extended Bridge MIB .......................... 20 98 5 Definitions for Virtual Bridge MIB ........................... 45 99 6 Acknowledgments .............................................. 97 100 7 IANA Considerations .......................................... 97 101 8 Security Considerations ...................................... 97 102 9 Normative References ......................................... 100 103 10 Informative References ...................................... 101 104 11 Contact Information ......................................... 103 105 Appendix A. Email from Tony Jeffrey from IEEE .................. 105 106 Copyright Statement ........................................... 105 107 Disclaimer of Validity ........................................ 105 109 1. The Internet-Standard Management Framework 111 For a detailed overview of the documents that describe the current 112 Internet-Standard Management Framework, please refer to section 7 of 113 RFC 3410 [RFC3410]. 115 Managed objects are accessed via a virtual information store, termed 116 the Management Information Base or MIB. MIB objects are generally 117 accessed through the Simple Network Management Protocol (SNMP). 118 Objects in the MIB are defined using the mechanisms defined in the 119 Structure of Management Information (SMI). This memo specifies a MIB 120 module that is compliant to the SMIv2, which is described in STD 58, 121 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 122 [RFC2580]. 124 2. Overview 126 A common device present in many networks is the Bridge. This device 127 is used to connect Local Area Network segments below the network 128 layer. These devices are often known as 'layer 2 switches'. 130 The transparent method of bridging is defined by IEEE 802.1D-1998 131 [802.1D]. Managed objects for transparent bridging are defined in 132 the BRIDGE-MIB [BRIDGE-MIB]. 134 The original IEEE 802.1D is augmented by IEEE 802.1Q-2003 [802.1Q] to 135 provide support for 'virtual bridged LANs' where a single bridged 136 physical LAN network may be used to support multiple logical bridged 137 LANs, each of which offers a service approximately the same as that 138 defined by IEEE 802.1D. Such virtual LANs (VLANs) are an integral 139 feature of switched LAN networks. A VLAN can be viewed as a group of 140 end-stations on multiple LAN segments and can communicate as if they 141 were on a single LAN. IEEE 802.1Q defines port-based Virtual LANs 142 where membership is determined by the bridge port on which data 143 frames are received, and port-and-protocol-based Virtual LANs where 144 membership is determined by the bridge port on which frames are 145 received and the protocol identifier of the frame. This memo defines 146 the objects needed for the management of port-based VLANs in bridge 147 entities. 149 2.1. Scope 151 The MIB modules defined in this document include a comprehensive set 152 of managed objects which attempts to match the set defined in IEEE 153 802.1D and IEEE 802.1Q. However, to be consistent with the spirit of 154 the SNMP Framework, a subjective judgement was made to omit the 155 objects from those standards most 'costly' to implement in an agent 156 and least 'essential' for fault and configuration management. The 157 omissions are described in section 3 below. 159 Historical note: 161 The original BRIDGE-MIB [RFC1493] used the following principles for 162 determining inclusion of an object in the BRIDGE-MIB module: 164 (1) Start with a small set of essential objects and add only as 165 further objects are needed. 167 (2) Require objects be essential for either fault or configuration 168 management. 170 (3) Consider evidence of current use and/or utility. 172 (4) Limit the total number of objects. 174 (5) Exclude objects which are simply derivable from others in this 175 or other MIBs. 177 (6) Avoid causing critical sections to be heavily instrumented. 178 The guideline that was followed is one counter per critical 179 section per layer. 181 3. Structure of MIBs 183 This document defines objects which supplement those in the 184 BRIDGE-MIB module [BRIDGE-MIB]. Section 3.4.3 of the present document 185 contains some recommendations regarding usage of objects in the 186 BRIDGE-MIB by devices implementing the enhancements defined here. 188 An extended bridge MIB module P-BRIDGE-MIB defines managed objects 189 for the traffic class and multicast filtering enhancements defined by 190 IEEE 802.1D-1998 [802.1D], including the Restricted Group 191 Registration control defined by IEEE P802.1t [802.1t]. 193 A virtual bridge MIB module Q-BRIDGE-MIB defines managed objects for 194 the Virtual LAN bridging enhancements defined by IEEE 802.1Q-2003 195 [802.1Q], including the Restricted VLAN Registration control defined 196 by IEEE P802.1u [802.1u] and the VLAN Classification by Protocol and 197 Port enhancement defined by IEEE P802.1v [802.1v]. 199 3.1. Structure of Extended Bridge MIB module 201 Objects in this MIB are arranged into subtrees. Each subtree is 202 organized as a set of related objects. The overall structure and 203 assignment of objects to their subtrees is shown below. 205 3.1.1. Relationship to IEEE 802.1D-1998 Manageable Objects 207 This section contains a cross-reference to the objects defined in 208 IEEE 802.1D-1998 [802.1D]. It also details those objects that are 209 not considered necessary in this MIB module. 211 Some objects defined by IEEE 802.1D-1998 have been included in the 212 virtual bridge MIB module rather than this one: entries in 213 dot1qTpGroupTable, dot1qForwardAllTable and 214 dot1qForwardUnregisteredTable are required for virtual bridged LANs 215 with additional indexing (e.g. per-VLAN, per-FDB) and so are not 216 defined here. Instead, devices which do not implement virtual 217 bridged LANs but do implement the Extended Forwarding Services 218 defined by IEEE 802.1D (i.e. dynamic learning of multicast group 219 addresses and group service requirements in the filtering database) 220 should implement these tables with a fixed value for dot1qFdbId (the 221 value 1 is recommended) or dot1qVlanIndex (the value 1 is 222 recommended). Devices which support Extended Filtering Services 223 should support dot1qTpGroupTable, dot1qForwardAllTable and 224 dot1qForwardUnregisteredTable. 226 Extended Bridge MIB Name IEEE 802.1D-1998 Name 228 dot1dExtBase Bridge 229 dot1dDeviceCapabilities 230 dot1dExtendedFilteringServices 231 dot1dTrafficClasses 232 dot1dTrafficClassesEnabled 233 dot1dGmrpStatus .ApplicantAdministrativeControl 234 dot1dPriority 235 dot1dPortPriorityTable 236 dot1dPortDefaultUserPriority .UserPriority 237 dot1dPortNumTrafficClasses 238 dot1dUserPriorityRegenTable .UserPriorityRegenerationTable 239 dot1dUserPriority 240 dot1dRegenUserPriority 241 dot1dTrafficClassTable .TrafficClassTable 242 dot1dTrafficClassPriority 243 dot1dTrafficClass 244 dot1dPortOutboundAccessPriorityTable 245 .OutboundAccessPriorityTable 246 dot1dPortOutboundAccessPriority 247 dot1dGarp 248 dot1dPortGarpTable 249 dot1dPortGarpJoinTime .JoinTime 250 dot1dPortGarpLeaveTime .LeaveTime 251 dot1dPortGarpLeaveAllTime .LeaveAllTime 252 dot1dGmrp 253 dot1dPortGmrpTable 254 dot1dPortGmrpStatus .ApplicantAdministrativeControl 255 dot1dPortGmrpFailedRegistrations .FailedRegistrations 256 dot1dPortGmrpLastPduOrigin .OriginatorOfLastPDU 257 dot1dPortRestrictedGroupRegistration 258 Restricted Group Registration 259 (Ref. IEEE 802.1t 10.3.2.3) 260 dot1dTp 261 dot1dTpHCPortTable 262 dot1dTpHCPortInFrames .BridgePort.FramesReceived 263 dot1dTpHCPortOutFrames .ForwardOutBound 264 dot1dTpHCPortInDiscards .DiscardInbound 265 dot1dTpPortOverflowTable 266 dot1dTpPortInOverflowFrames .BridgePort.FramesReceived 267 dot1dTpPortOutOverflowFrames .ForwardOutBound 268 dot1dTpPortInOverflowDiscards .DiscardInbound 270 The following IEEE 802.1D-1998 management objects have not been 271 included in the Bridge MIB for the indicated reasons. 273 IEEE 802.1D-1998 Object Disposition 275 Bridge.StateValue not considered useful 276 Bridge.ApplicantAdministrativeControl 277 not provided per-attribute 278 (e.g. per-VLAN, per-Group). 279 Only per-{device,port,application} 280 control is provided in this MIB. 282 notify group registration failure not considered useful 283 (IEEE 802.1t 14.10.1.2) 285 3.1.2. Relationship to IEEE 802.1Q Manageable Objects 287 This section contains section number cross-references to manageable 288 objects defined in IEEE 802.1Q-2003 [802.1Q]. These objects have 289 been included in this MIB as they provide a natural fit with the IEEE 290 802.1D objects with which they are co-located. 292 Extended Bridge MIB Name IEEE 802.1Q-2003 Section and Name 294 dot1dExtBase Bridge 295 dot1dDeviceCapabilities 296 dot1qStaticEntryIndividualPort 5.2 implementation options 297 dot1qIVLCapable 298 dot1qSVLCapable 299 dot1qHybridCapable 300 dot1qConfigurablePvidTagging 12.10.1.1 read bridge vlan 301 config 302 dot1dLocalVlanCapable 303 dot1dPortCapabilitiesTable 304 dot1dPortCapabilities 305 dot1qDot1qTagging 5.2 implementation options 306 dot1qConfigurableAcceptableFrameTypes 307 5.2 implementation options 308 dot1qIngressFiltering 5.2 implementation options 310 3.1.3. The dot1dExtBase Subtree 312 This subtree contains the objects which are applicable to all bridges 313 implementing the traffic class and multicast filtering features of 314 IEEE 802.1D-1998 [802.1D]. It includes per-device configuration of 315 GARP and GMRP protocols. 317 3.1.4. The dot1dPriority Subtree 319 This subtree contains the objects for configuring and reporting 320 status of priority-based queuing mechanisms in a bridge. This 321 includes per-port user_priority treatment, mapping of user_priority 322 in frames into internal traffic classes and outbound user_priority 323 and access_priority. 325 3.1.5. The dot1dGarp Subtree 327 This subtree contains the objects for configuring and reporting on 328 operation of the Generic Attribute Registration Protocol (GARP). 330 3.1.6. The dot1dGmrp Subtree 332 This subtree contains the objects for configuring and reporting on 333 operation of the GARP Multicast Registration Protocol (GMRP). 335 3.1.7. The dot1dTpHCPortTable 337 This table extends the dot1dTp subtree from the BRIDGE-MIB 338 [BRIDGE-MIB] and contains the objects for reporting port bridging 339 statistics for high capacity network interfaces. 341 3.1.8. The dot1dTpPortOverflowTable 343 This table extends the dot1dTp subtree from the BRIDGE-MIB 344 [BRIDGE-MIB] and contains the objects for reporting the upper bits of 345 port bridging statistics for high capacity network interfaces for 346 when 32-bit counters are inadequate. 348 3.2. Structure of Virtual Bridge MIB module 350 Objects in this MIB are arranged into subtrees. Each subtree is 351 organized as a set of related objects. The overall structure and 352 assignment of objects to their subtrees is shown below. Some 353 manageable objects defined in the BRIDGE-MIB [BRIDGE-MIB] need to be 354 indexed differently when they are used in a VLAN bridging 355 environment: these objects are, therefore, effectively duplicated by 356 new objects with different indexing which are defined in the Virtual 357 Bridge MIB. 359 3.2.1. Relationship to IEEE 802.1Q Manageable Objects 361 This section contains section-number cross-references to manageable 362 objects defined in clause 12 of IEEE 802.1Q-2003 [802.1Q]. It also 363 details those objects that are not considered necessary in this MIB 364 module. 366 Note: unlike IEEE 802.1D-1998, IEEE 802.1Q-2003 [802.1Q] did not 367 define exact syntax for a set of managed objects: the following 368 cross-references indicate the section numbering of the descriptions 369 of management operations from clause 12 in the latter document. 371 Virtual Bridge MIB object IEEE 802.1Q-2003 Reference 373 dot1qBase 374 dot1qVlanVersionNumber 12.10.1.1 read bridge vlan config 375 dot1qMaxVlanId 12.10.1.1 read bridge vlan config 376 dot1qMaxSupportedVlans 12.10.1.1 read bridge vlan config 377 dot1qNumVlans 378 dot1qGvrpStatus 12.9.2.1/2 read/set garp 379 applicant controls 380 dot1qTp 381 dot1qFdbTable 382 dot1qFdbId 383 dot1qFdbDynamicCount 12.7.1.1.3 read filtering d/base 384 dot1qTpFdbTable 385 dot1qTpFdbAddress 386 dot1qTpFdbPort 387 dot1qTpFdbStatus 388 dot1qTpGroupTable 12.7.7.1 read filtering entry 389 dot1qTpGroupAddress 390 dot1qTpGroupEgressPorts 391 dot1qTpGroupLearnt 392 dot1qForwardAllTable 12.7.7.1 read filtering entry 393 dot1qForwardAllPorts 394 dot1qForwardAllStaticPorts 395 dot1qForwardAllForbiddenPorts 396 dot1qForwardUnregisteredTable 12.7.7.1 read filtering entry 397 dot1qForwardUnregisteredPorts 398 dot1qForwardUnregisteredStaticPorts 399 dot1qForwardUnregisteredForbiddenPorts 400 dot1qStatic 401 dot1qStaticUnicastTable 12.7.7.1 create/delete/read 402 filtering entry 403 12.7.6.1 read permanent database 404 dot1qStaticUnicastAddress 405 dot1qStaticUnicastReceivePort 406 dot1qStaticUnicastAllowedToGoTo 407 dot1qStaticUnicastStatus 408 dot1qStaticMulticastTable 12.7.7.1 create/delete/read 409 filtering entry 410 12.7.6.1 read permanent database 411 dot1qStaticMulticastAddress 412 dot1qStaticMulticastReceivePort 413 dot1qStaticMulticastStaticEgressPorts 414 dot1qStaticMulticastForbiddenEgressPorts 415 dot1qStaticMulticastStatus 416 dot1qVlan 417 dot1qVlanNumDeletes 418 dot1qVlanCurrentTable 12.10.2.1 read vlan configuration 419 12.10.3.5 read VID to FID 420 allocations 421 12.10.3.6 read FID allocated to 422 VID 423 12.10.3.7 read VIDs allocated to 424 FID 425 dot1qVlanTimeMark 426 dot1qVlanIndex 427 dot1qVlanFdbId 428 dot1qVlanCurrentEgressPorts 429 dot1qVlanCurrentUntaggedPorts 430 dot1qVlanStatus 431 dot1qVlanCreationTime 432 dot1qVlanStaticTable 12.7.7.1/2/3 create/delete/read 433 filtering entry 434 12.7.6.1 read permanent database 435 12.10.2.2 create vlan config 436 12.10.2.3 delete vlan config 437 dot1qVlanStaticName 12.4.1.3 set bridge name 438 dot1qVlanStaticEgressPorts 439 dot1qVlanForbiddenEgressPorts 440 dot1qVlanStaticUntaggedPorts 441 dot1qVlanStaticRowStatus 442 dot1qNextFreeLocalVlanIndex 443 dot1qPortVlanTable 12.10.1.1 read bridge vlan 444 configuration 445 dot1qPvid 12.10.1.2 configure PVID values 446 dot1qPortAcceptableFrameTypes 12.10.1.3 configure acceptable 447 frame types parameter 448 dot1qPortIngressFiltering 12.10.1.4 configure ingress 449 filtering parameters 450 dot1qPortGvrpStatus 12.9.2.2 read/set garp applicant 451 controls 452 dot1qPortGvrpFailedRegistrations 453 dot1qPortGvrpLastPduOrigin 454 dot1qPortRestrictedVlanRegistration 455 IEEE 802.1u 11.2.3.2.3 456 Restricted VLAN Registration 457 dot1qPortVlanStatisticsTable 12.6.1.1 read forwarding port 458 counters 459 dot1qTpVlanPortInFrames 460 dot1qTpVlanPortOutFrames 461 dot1qTpVlanPortInDiscards 462 dot1qTpVlanPortInOverflowFrames 463 dot1qTpVlanPortOutOverflowFrames 464 dot1qTpVlanPortInOverflowDiscards 465 dot1qPortVlanHCStatisticsTable 12.6.1.1 read forwarding port 466 counters 467 dot1qTpVlanPortHCInFrames 468 dot1qTpVlanPortHCOutFrames 469 dot1qTpVlanPortHCInDiscards 470 dot1qLearningConstraintsTable 12.10.3.1/3/4 read/set/delete 471 vlan learning constraints 472 12.10.3.2 read vlan learning 473 constraints for VID 474 dot1qConstraintVlan 475 dot1qConstraintSet 476 dot1qConstraintType 477 dot1qConstraintStatus 478 dot1qConstraintSetDefault 479 dot1qConstraintTypeDefault 481 dot1vProtocol IEEE 802.1v Reference: 482 dot1vProtocolGroupTable 8.6.4 Protocol Group Database, 483 8.6.2 Protocol Template 484 dot1vProtocolTemplateFrameType 485 dot1vProtocolTemplateProtocolValue 486 dot1vProtocolGroupId 8.6.3 Protocol Group Identifier 487 dot1vProtocolGroupRowStatus 488 dot1vProtocolPortTable 8.4.4 VID Set for each Port 489 dot1vProtocolPortGroupId 490 dot1vProtocolGroupVid 491 dot1vProtocolPortRowStatus 493 The following IEEE 802.1Q management objects have not been included 494 in the Bridge MIB for the indicated reasons. 496 IEEE 802.1Q-2003 Operation Disposition 498 reset bridge (12.4.1.4) not considered useful 500 reset vlan bridge (12.10.1.5) not considered useful 502 read forwarding port counters (12.6.1.1) 503 discard on error details not considered useful 505 read permanent database (12.7.6.1) 506 permanent database size not considered useful 507 number of static filtering count rows in 508 entries dot1qStaticUnicastTable + 509 dot1qStaticMulticastTable 510 number of static VLAN count rows in 511 registration entries dot1qVlanStaticTable 512 read filtering entry range use GetNext operation. 513 (12.7.7.4) 515 read filtering database (12.7.1.1) 516 filtering database size not considered useful 517 number of dynamic group address count rows applicable to each 518 entries (12.7.1.3) FDB in dot1dTpGroupTable 520 read garp state (12.9.3.1) not considered useful 522 notify vlan registration failure not considered useful 523 (12.10.1.6) 525 notify learning constraint violation 526 (12.10.3.10) not considered useful 528 3.2.2. The dot1qBase Subtree 530 This subtree contains the objects which are applicable to all bridges 531 implementing IEEE 802.1Q virtual LANs. 533 3.2.3. The dot1qTp Subtree 535 This subtree contains objects that control the operation and report 536 the status of transparent bridging. This includes management of the 537 dynamic Filtering Databases for both unicast and multicast 538 forwarding. This subtree will be implemented by all bridges that 539 perform destination-address filtering. 541 3.2.4. The dot1qStatic Subtree 543 This subtree contains objects that control static configuration 544 information for transparent bridging. This includes management of 545 the static entries in the Filtering Databases for both unicast and 546 multicast forwarding. 548 3.2.5. The dot1qVlan Subtree 550 This subtree contains objects that control configuration and report 551 status of the Virtual LANs known to a bridge. This includes 552 management of the statically configured VLANs as well as reporting 553 VLANs discovered by other means e.g. GVRP. It also controls 554 configuration and reports status of per-port objects relating to 555 VLANs and reports traffic statistics. It also provides for 556 management of the VLAN Learning Constraints. 558 3.3. Textual Conventions 560 Various Working Groups have defined standards-track MIB documents 561 (for example [RFC2613] and [RFC3318]), that contain objects and 562 Textual Conventions to represent a Virtual Local Area Network 563 Identifier (VLAN-ID) [802.1Q]. New definitions are showing up in 564 various Internet-Drafts (for example [I-D.ietf-ipcdn-qos-mib], 565 [I-D.ietf-rmonmib-sspm-mib]). Unfortunately the result is a set of 566 different definitions for the same piece of management information. 567 This may lead to confusion and unnecessary complexity. In order to 568 address this situation, three new textual conventions are defined in 569 the Q-BRIDGE-MIB, called VlanIdOrAny, VlanIdOrNone, and 570 VlanIdOrAnyOrNone. These new textual conventions should be (re-)used 571 in MIB modules, so that they all represent a VLAN-ID in the same way. 573 These textual conventions provide a means to specify MIB objects that 574 refer to either a specific VLAN, to any VLAN, or to no VLAN. For an 575 example of how these textual conventions might be used, consider a 576 MIB object, with SYNTAX of VlanIdOrAnyOrNone, that specifies the VLAN 577 on which to accept incoming packets of a particular protocol. Such 578 an object would allow the device to be configured to accept packets 579 of this protocol received with a specific 802.1q tag value, with any 580 802.1q tag value, or with no 802.1q tag. Note that a MIB object that 581 is defined using one of these textual conventions should clarify the 582 meaning of 'any VLAN' and/or 'no VLAN' in its DESCRIPTION clause. 584 3.4. Relationship to Other MIBs 586 As described above, some IEEE 802.1D management objects have not been 587 included in this MIB because they overlap with objects in other MIBs 588 applicable to a bridge implementing this MIB module. 590 3.4.1. Relationship to the SNMPv2-MIB 592 The SNMPv2-MIB [RFC3418] defines objects that are generally 593 applicable to managed devices. These objects apply to the device as 594 a whole irrespective of whether the device's sole functionality is 595 bridging, or whether bridging is only a subset of the device's 596 functionality. 598 Full support for the 802.1D management objects requires that the 599 SNMPv2-MIB objects sysDescr and sysUpTime are implemented. Note that 600 compliance to the current SNMPv2-MIB module requires additional 601 objects and notifications to be implemented as specified in RFC 3418 602 [RFC3418]. 604 3.4.2. Relationship to the IF-MIB 606 The IF-MIB, [RFC2863], requires that any MIB which is an adjunct of 607 the IF-MIB clarify specific areas within the IF-MIB. These areas 608 were intentionally left vague in the IF-MIB in order to avoid 609 over-constraining the MIB, thereby precluding management of certain 610 media-types. 612 The IF-MIB enumerates several areas which a media-specific MIB must 613 clarify. Each of these areas is addressed in a following subsection. 614 The implementor is referred to the IF-MIB in order to understand the 615 general intent of these areas. 617 The IF-MIB [RFC2863] defines managed objects for managing network 618 interfaces. A network interface is thought of as being attached to a 619 `subnetwork'. (Note that this term is not to be confused with 620 `subnet' which refers to an addressing partitioning scheme used in 621 the Internet suite of protocols.) The term 'segment' is used in this 622 memo to refer to such a subnetwork, whether it be an Ethernet 623 segment, a 'ring', a WAN link, or even an X.25 virtual circuit. 625 Full support for the 802.1D management objects requires that the 626 IF-MIB objects ifIndex, ifType, ifDescr, ifPhysAddress, and 627 ifLastChange are implemented. Note that compliance to the current 628 IF-MIB module requires additional objects and notifications to be 629 implemented as specified in RFC 2863 [RFC2863]. 631 Implicit in this Extended Bridge MIB is the notion of ports on a 632 bridge. Each of these ports is associated with one interface of the 633 'interfaces' subtree (one row in ifTable) and, in most situations, 634 each port is associated with a different interface. However, there 635 are situations in which multiple ports are associated with the same 636 interface. An example of such a situation would be several ports 637 each corresponding one-to-one with several X.25 virtual circuits but 638 all on the same interface. 640 Each port is uniquely identified by a port number. A port number has 641 no mandatory relationship to an interface number, but in the simple 642 case a port number will have the same value as the corresponding 643 interface's interface number. Port numbers are in the range 644 (1..dot1dBaseNumPorts). 646 Some entities perform other functionality as well as bridging through 647 the sending and receiving of data on their interfaces. In such 648 situations, only a subset of the data sent/received on an interface 649 is within the domain of the entity's bridging functionality. This 650 subset is considered to be delineated according to a set of 651 protocols, with some protocols being bridged, and other protocols not 652 being bridged. For example, in an entity which exclusively performed 653 bridging, all protocols would be considered as being bridged, whereas 654 in an entity which performed IP routing on IP datagrams and only 655 bridged other protocols, only the non-IP data would be considered as 656 being bridged. 658 Thus, this Extended Bridge MIB (and in particular, its counters) is 659 applicable only to that subset of the data on an entity's interfaces 660 which is sent/received for a protocol being bridged. All such data 661 is sent/received via the ports of the bridge. 663 3.4.2.1. Layering Model 665 This memo assumes the interpretation of the Interfaces Subtree to be 666 in accordance with the IF-MIB [RFC2863] which states that the 667 interfaces table (ifTable) contains information on the managed 668 resource's interfaces and that each sub-layer below the internetwork 669 layer of a network interface is considered an interface. 671 This document does not make any assumption that within an entity, 672 VLANs which are instantiated as an entry in dot1qVlanCurrentTable by 673 either management configuration through dot1qVlanStaticTable or by 674 dynamic means (e.g. through GVRP), are also represented by an entry 675 in ifTable. 677 Where an entity contains higher-layer protocol entities e.g. IP-layer 678 interfaces that transmit and receive traffic to/from a VLAN, these 679 should be represented in the ifTable as interfaces of type 680 propVirtual(53). Protocol-specific types such as l3ipxvlan(137) 681 should not be used here since there is no implication that the bridge 682 will perform any protocol filtering before delivering up to these 683 virtual interfaces. 685 3.4.2.2. ifStackTable 687 In addition, the IF-MIB [RFC2863] defines a table 'ifStackTable' for 688 describing the relationship between logical interfaces within an 689 entity. It is anticipated that implementors will use this table to 690 describe the binding of e.g. IP interfaces to physical ports, 691 although the presence of VLANs makes the representation less than 692 perfect for showing connectivity: the ifStackTable cannot represent 693 the full capability of the IEEE 802.1Q VLAN bridging standard since 694 that makes a distinction between VLAN bindings on 'ingress' to and 695 'egress' from a port: these relationships may or may not be 696 symmetrical whereas Interface MIB Evolution assumes a symmetrical 697 binding for transmit and receive. This makes it necessary to define 698 other manageable objects for configuring which ports are members of 699 which VLANs. 701 3.4.2.3. ifRcvAddressTable 703 This table contains all MAC addresses, unicast, multicast, and 704 broadcast, for which an interface will receive packets and forward 705 them up to a higher layer entity for local consumption. Note that 706 this does not include addresses for data-link layer control protocols 707 such as Spanning-Tree, GMRP or GVRP. The format of the address, 708 contained in ifRcvAddressAddress, is the same as for ifPhysAddress. 710 This table does not include unicast or multicast addresses which are 711 accepted for possible forwarding out some other port. This table is 712 explicitly not intended to provide a bridge address filtering 713 mechanism. 715 3.4.3. Relationship to the BRIDGE-MIB 717 This section defines how objects in the BRIDGE-MIB module 718 [BRIDGE-MIB] should be represented for devices which implement the 719 extensions: some of the old objects are less useful in such devices 720 but must still be implemented for reasons of backwards compatibility. 722 3.4.3.1. The dot1dBase Subtree 724 This subtree contains objects which are applicable to all types of 725 bridges. Interpretation of this subtree is unchanged. 727 3.4.3.2. The dot1dStp Subtree 729 This subtree contains the objects that denote the bridge's state with 730 respect to the Spanning Tree Protocol. Interpretation of this 731 subtree is unchanged. 733 3.4.3.3. The dot1dTp Subtree 735 This subtree contains objects that describe the entity's state with 736 respect to transparent bridging. 738 In a device operating with a single Filtering Database, 739 interpretation of this subtree is unchanged. 741 In a device supporting multiple Filtering Databases, this subtree is 742 interpreted as follows: 744 dot1dTpLearnedEntryDiscards 745 The number of times that *any* of the FDBs became full. 747 dot1dTpAgingTime 749 This applies to all Filtering Databases. 751 dot1dTpFdbTable 753 Report MAC addresses learned on each port, regardless of which 754 Filtering Database they have been learnt in. If an address has 755 been learnt in multiple databases on a single port, report it 756 only once. If an address has been learnt in multiple databases 757 on more than one port, report the entry on any one of the valid 758 ports. 760 dot1dTpPortTable 762 This table is port-based and is not affected by multiple 763 Filtering Databases or multiple VLANs. The counters should 764 include frames received or transmitted for all VLANs. Note that 765 equivalent 64-bit port statistics counters, as well as other 766 objects to represent the upper 32 bits of these counters, are 767 defined in this document for high capacity network interfaces. 768 These have conformance statements to indicate for which speeds 769 of interface they are required. 771 3.4.3.4. The dot1dStatic Subtree 773 This optional subtree contains objects that describe the 774 configuration of destination-address filtering. 776 In a device operating with a single Filtering Database, 777 interpretation of this subtree is unchanged. 779 In a device supporting multiple Filtering Databases, this subtree is 780 interpreted as follows: 782 dot1dStaticTable 784 Entries read from this table include all static entries from all 785 of the Filtering Databases. Entries for the same MAC address 786 and receive port in more than one Filtering Database must appear 787 only once since these are the indices of this table. This table 788 should be implemented as read-only in devices that support 789 multiple Forwarding Databases - instead, write access should be 790 provided through dot1qStaticUnicastTable and 791 dot1qStaticMulticastTable, as defined in this document. 793 3.4.3.5. Additions to the BRIDGE-MIB 795 To supplement the BRIDGE-MIB [BRIDGE-MIB], this module contains: 797 (1) support for multiple traffic classes and dynamic multicast 798 filtering as per IEEE 802.1D-1998 [802.1D]. 800 (2) support for bridged Virtual LANs as per IEEE 802.1Q-2003 801 [802.1Q]. 803 (3) support for 64-bit versions of BRIDGE-MIB [BRIDGE-MIB] port 804 counters. 806 4. Definitions for Extended Bridge MIB 808 P-BRIDGE-MIB DEFINITIONS ::= BEGIN 810 -- ------------------------------------------------------------- 811 -- MIB for IEEE 802.1p devices 812 -- ------------------------------------------------------------- 814 IMPORTS 815 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, Counter64 816 FROM SNMPv2-SMI 817 TruthValue, TimeInterval, MacAddress, TEXTUAL-CONVENTION 818 FROM SNMPv2-TC 819 MODULE-COMPLIANCE, OBJECT-GROUP 820 FROM SNMPv2-CONF 821 dot1dTp, dot1dTpPort, dot1dBridge, 822 dot1dBasePortEntry, dot1dBasePort 823 FROM BRIDGE-MIB; 825 pBridgeMIB MODULE-IDENTITY 826 LAST-UPDATED "200507290000Z" 827 ORGANIZATION "IETF Bridge MIB Working Group" 828 CONTACT-INFO 829 "Email: bridge-mib@ietf.org 830 ietfmibs@ops.ietf.org 832 David Levi 833 Postal: Nortel Networks 834 4655 Great America Parkway 835 Santa Clara, CA 95054 836 USA 837 Phone: +1 865 686 0432 838 Email: dlevi@nortel.com 840 David Harrington 841 Postal: Effective Software 842 50 Harding Rd. 843 Portsmouth, NH 03801 844 USA 845 Phone: +1 603 436 8634 846 Email: ietfdbh@comcast.net 848 Les Bell 849 Postal: Hemel Hempstead, Herts. HP2 7YU 850 UK 851 Email: elbell@ntlworld.com 852 Vivian Ngai 853 Email: vivian_ngai@acm.org 855 Andrew Smith 856 Postal: Beijing Harbour Networks 857 Jiuling Building 858 21 North Xisanhuan Ave. 859 Beijing, 100089 860 PRC 861 Fax: +1 415 345 1827 862 Email: ah_smith@acm.org 864 Paul Langille 865 Postal: Newbridge Networks 866 5 Corporate Drive 867 Andover, MA 01810 868 USA 869 Phone: +1 978 691 4665 870 Email: langille@newbridge.com 872 Anil Rijhsinghani 873 Postal: Accton Technology Corporation 874 5 Mount Royal Ave 875 Marlboro, MA 01752 876 USA 877 Phone: 878 Email: anil@accton.com 880 Keith McCloghrie 881 Postal: Cisco Systems, Inc. 882 170 West Tasman Drive 883 San Jose, CA 95134-1706 884 USA 885 Phone: +1 408 526 5260 886 Email: kzm@cisco.com" 887 DESCRIPTION 888 "The Bridge MIB Extension module for managing Priority 889 and Multicast Filtering, defined by IEEE 802.1D-1998, 890 including Restricted Group Registration defined by 891 IEEE 802.1t-2001. 893 Copyright (C) The Internet Society (2005). This version of 894 this MIB module is part of RFC XXXX; See the RFC itself for 895 full legal notices." 896 -- NOTE to RFC editor: replace XXXX with actual RFC number 897 -- for this document and remove this note 899 REVISION "200507290000Z" 900 DESCRIPTION 901 "Added dot1dPortRestrictedGroupRegistration. 902 Deprecated pBridgePortGmrpGroup and pBridgeCompliance 903 and added pBridgePortGmrpGroup2 and pBridgeCompliance2." 905 REVISION "199908250000Z" 906 DESCRIPTION 907 "The Bridge MIB Extension module for managing Priority 908 and Multicast Filtering, defined by IEEE 802.1D-1998. 910 Initial version, published as RFC 2674." 912 ::= { dot1dBridge 6 } 914 pBridgeMIBObjects OBJECT IDENTIFIER ::= { pBridgeMIB 1 } 916 -- ------------------------------------------------------------- 917 -- Textual Conventions 918 -- ------------------------------------------------------------- 920 EnabledStatus ::= TEXTUAL-CONVENTION 921 STATUS current 922 DESCRIPTION 923 "A simple status value for the object." 924 SYNTAX INTEGER { enabled(1), disabled(2) } 926 -- ------------------------------------------------------------- 927 -- subtrees in the P-BRIDGE MIB 928 -- ------------------------------------------------------------- 930 dot1dExtBase OBJECT IDENTIFIER ::= { pBridgeMIBObjects 1 } 931 dot1dPriority OBJECT IDENTIFIER ::= { pBridgeMIBObjects 2 } 932 dot1dGarp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 3 } 933 dot1dGmrp OBJECT IDENTIFIER ::= { pBridgeMIBObjects 4 } 935 -- ------------------------------------------------------------- 936 -- the dot1dExtBase subtree 937 -- ------------------------------------------------------------- 939 dot1dDeviceCapabilities OBJECT-TYPE 940 SYNTAX BITS { 941 dot1dExtendedFilteringServices(0), 942 dot1dTrafficClasses(1), 943 dot1qStaticEntryIndividualPort(2), 944 dot1qIVLCapable(3), 945 dot1qSVLCapable(4), 946 dot1qHybridCapable(5), 947 dot1qConfigurablePvidTagging(6), 948 dot1dLocalVlanCapable(7) 949 } 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "Indicates the optional parts of IEEE 802.1D and 802.1Q 954 that are implemented by this device and are manageable 955 through this MIB. Capabilities that are allowed on a 956 per-port basis are indicated in dot1dPortCapabilities. 958 dot1dExtendedFilteringServices(0), 959 -- can perform filtering of 960 -- individual multicast addresses 961 -- controlled by GMRP. 962 dot1dTrafficClasses(1), 963 -- can map user priority to 964 -- multiple traffic classes. 965 dot1qStaticEntryIndividualPort(2), 966 -- dot1qStaticUnicastReceivePort & 967 -- dot1qStaticMulticastReceivePort 968 -- can represent non-zero entries. 969 dot1qIVLCapable(3), -- Independent VLAN Learning. 970 dot1qSVLCapable(4), -- Shared VLAN Learning. 971 dot1qHybridCapable(5), 972 -- both IVL & SVL simultaneously. 973 dot1qConfigurablePvidTagging(6), 974 -- whether the implementation 975 -- supports the ability to 976 -- override the default PVID 977 -- setting and its egress status 978 -- (VLAN-Tagged or Untagged) on 979 -- each port. 980 dot1dLocalVlanCapable(7) 981 -- can support multiple local 982 -- bridges, outside of the scope 983 -- of 802.1Q defined VLANs." 984 REFERENCE 985 "ISO/IEC 15802-3 Section 5.2, 986 IEEE 802.1Q/D11 Section 5.2, 12.10.1.1.3/b/2" 987 ::= { dot1dExtBase 1 } 989 dot1dTrafficClassesEnabled OBJECT-TYPE 990 SYNTAX TruthValue 991 MAX-ACCESS read-write 992 STATUS current 993 DESCRIPTION 994 "The value true(1) indicates that Traffic Classes are 995 enabled on this bridge. When false(2), the bridge 996 operates with a single priority level for all traffic. 998 The value of this object MUST be retained across 999 reinitializations of the management system." 1000 DEFVAL { true } 1001 ::= { dot1dExtBase 2 } 1003 dot1dGmrpStatus OBJECT-TYPE 1004 SYNTAX EnabledStatus 1005 MAX-ACCESS read-write 1006 STATUS current 1007 DESCRIPTION 1008 "The administrative status requested by management for 1009 GMRP. The value enabled(1) indicates that GMRP should 1010 be enabled on this device, in all VLANs, on all ports 1011 for which it has not been specifically disabled. When 1012 disabled(2), GMRP is disabled, in all VLANs, on all 1013 ports and all GMRP packets will be forwarded 1014 transparently. This object affects both Applicant and 1015 Registrar state machines. A transition from disabled(2) 1016 to enabled(1) will cause a reset of all GMRP state 1017 machines on all ports. 1019 The value of this object MUST be retained across 1020 reinitializations of the management system." 1021 DEFVAL { enabled } 1022 ::= { dot1dExtBase 3 } 1024 -- ------------------------------------------------------------- 1025 -- Port Capabilities Table 1026 -- ------------------------------------------------------------- 1028 dot1dPortCapabilitiesTable OBJECT-TYPE 1029 SYNTAX SEQUENCE OF Dot1dPortCapabilitiesEntry 1030 MAX-ACCESS not-accessible 1031 STATUS current 1032 DESCRIPTION 1033 "A table that contains capabilities information about 1034 every port that is associated with this bridge." 1035 ::= { dot1dExtBase 4 } 1037 dot1dPortCapabilitiesEntry OBJECT-TYPE 1038 SYNTAX Dot1dPortCapabilitiesEntry 1039 MAX-ACCESS not-accessible 1040 STATUS current 1041 DESCRIPTION 1042 "A set of capabilities information about this port 1043 indexed by dot1dBasePort." 1044 AUGMENTS { dot1dBasePortEntry } 1045 ::= { dot1dPortCapabilitiesTable 1 } 1047 Dot1dPortCapabilitiesEntry ::= 1048 SEQUENCE { 1049 dot1dPortCapabilities 1050 BITS 1051 } 1053 dot1dPortCapabilities OBJECT-TYPE 1054 SYNTAX BITS { 1055 dot1qDot1qTagging(0), 1056 dot1qConfigurableAcceptableFrameTypes(1), 1057 dot1qIngressFiltering(2) 1058 } 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "Indicates the parts of IEEE 802.1D and 802.1Q that are 1063 optional on a per-port basis that are implemented by 1064 this device and are manageable through this MIB. 1066 dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of 1067 -- frames and GVRP. 1068 dot1qConfigurableAcceptableFrameTypes(1), 1069 -- allows modified values of 1070 -- dot1qPortAcceptableFrameTypes. 1071 dot1qIngressFiltering(2) 1072 -- supports the discarding of any 1073 -- frame received on a Port whose 1074 -- VLAN classification does not 1075 -- include that Port in its Member 1076 -- set." 1077 REFERENCE 1078 "ISO/IEC 15802-3 Section 5.2, 1079 IEEE 802.1Q/D11 Section 5.2" 1080 ::= { dot1dPortCapabilitiesEntry 1 } 1082 -- ------------------------------------------------------------- 1083 -- the dot1dPriority subtree 1084 -- ------------------------------------------------------------- 1086 -- ------------------------------------------------------------- 1087 -- Port Priority Table 1088 -- ------------------------------------------------------------- 1090 dot1dPortPriorityTable OBJECT-TYPE 1091 SYNTAX SEQUENCE OF Dot1dPortPriorityEntry 1092 MAX-ACCESS not-accessible 1093 STATUS current 1094 DESCRIPTION 1095 "A table that contains information about every port that 1096 is associated with this transparent bridge." 1097 ::= { dot1dPriority 1 } 1099 dot1dPortPriorityEntry OBJECT-TYPE 1100 SYNTAX Dot1dPortPriorityEntry 1101 MAX-ACCESS not-accessible 1102 STATUS current 1103 DESCRIPTION 1104 "A list of Default User Priorities for each port of a 1105 transparent bridge. This is indexed by dot1dBasePort." 1106 AUGMENTS { dot1dBasePortEntry } 1107 ::= { dot1dPortPriorityTable 1 } 1109 Dot1dPortPriorityEntry ::= 1110 SEQUENCE { 1111 dot1dPortDefaultUserPriority 1112 Integer32, 1113 dot1dPortNumTrafficClasses 1114 Integer32 1115 } 1117 dot1dPortDefaultUserPriority OBJECT-TYPE 1118 SYNTAX Integer32 (0..7) 1119 MAX-ACCESS read-write 1120 STATUS current 1121 DESCRIPTION 1122 "The default ingress User Priority for this port. This 1123 only has effect on media, such as Ethernet, that do not 1124 support native User Priority. 1126 The value of this object MUST be retained across 1127 reinitializations of the management system." 1128 ::= { dot1dPortPriorityEntry 1 } 1130 dot1dPortNumTrafficClasses OBJECT-TYPE 1131 SYNTAX Integer32 (1..8) 1132 MAX-ACCESS read-write 1133 STATUS current 1134 DESCRIPTION 1135 "The number of egress traffic classes supported on this 1136 port. This object may optionally be read-only. 1138 The value of this object MUST be retained across 1139 reinitializations of the management system." 1140 ::= { dot1dPortPriorityEntry 2 } 1142 -- ------------------------------------------------------------- 1143 -- User Priority Regeneration Table 1144 -- ------------------------------------------------------------- 1146 dot1dUserPriorityRegenTable OBJECT-TYPE 1147 SYNTAX SEQUENCE OF Dot1dUserPriorityRegenEntry 1148 MAX-ACCESS not-accessible 1149 STATUS current 1150 DESCRIPTION 1151 "A list of Regenerated User Priorities for each received 1152 User Priority on each port of a bridge. The Regenerated 1153 User Priority value may be used to index the Traffic 1154 Class Table for each input port. This only has effect 1155 on media that support native User Priority. The default 1156 values for Regenerated User Priorities are the same as 1157 the User Priorities." 1158 REFERENCE 1159 "ISO/IEC 15802-3 Section 6.4" 1160 ::= { dot1dPriority 2 } 1162 dot1dUserPriorityRegenEntry OBJECT-TYPE 1163 SYNTAX Dot1dUserPriorityRegenEntry 1164 MAX-ACCESS not-accessible 1165 STATUS current 1166 DESCRIPTION 1167 "A mapping of incoming User Priority to a Regenerated 1168 User Priority." 1169 INDEX { dot1dBasePort, dot1dUserPriority } 1170 ::= { dot1dUserPriorityRegenTable 1 } 1172 Dot1dUserPriorityRegenEntry ::= 1173 SEQUENCE { 1174 dot1dUserPriority 1175 Integer32, 1177 dot1dRegenUserPriority 1178 Integer32 1179 } 1181 dot1dUserPriority OBJECT-TYPE 1182 SYNTAX Integer32 (0..7) 1183 MAX-ACCESS not-accessible 1184 STATUS current 1185 DESCRIPTION 1186 "The User Priority for a frame received on this port." 1187 ::= { dot1dUserPriorityRegenEntry 1 } 1189 dot1dRegenUserPriority OBJECT-TYPE 1190 SYNTAX Integer32 (0..7) 1191 MAX-ACCESS read-write 1192 STATUS current 1193 DESCRIPTION 1194 "The Regenerated User Priority that the incoming User 1195 Priority is mapped to for this port. 1197 The value of this object MUST be retained across 1198 reinitializations of the management system." 1199 ::= { dot1dUserPriorityRegenEntry 2 } 1201 -- ------------------------------------------------------------- 1202 -- Traffic Class Table 1203 -- ------------------------------------------------------------- 1205 dot1dTrafficClassTable OBJECT-TYPE 1206 SYNTAX SEQUENCE OF Dot1dTrafficClassEntry 1207 MAX-ACCESS not-accessible 1208 STATUS current 1209 DESCRIPTION 1210 "A table mapping evaluated User Priority to Traffic 1211 Class, for forwarding by the bridge. Traffic class is a 1212 number in the range (0..(dot1dPortNumTrafficClasses-1))." 1213 REFERENCE 1214 "ISO/IEC 15802-3 Table 7-2" 1215 ::= { dot1dPriority 3 } 1217 dot1dTrafficClassEntry OBJECT-TYPE 1218 SYNTAX Dot1dTrafficClassEntry 1219 MAX-ACCESS not-accessible 1220 STATUS current 1221 DESCRIPTION 1222 "User Priority to Traffic Class mapping." 1224 INDEX { dot1dBasePort, dot1dTrafficClassPriority } 1225 ::= { dot1dTrafficClassTable 1 } 1227 Dot1dTrafficClassEntry ::= 1228 SEQUENCE { 1229 dot1dTrafficClassPriority 1230 Integer32, 1231 dot1dTrafficClass 1232 Integer32 1233 } 1235 dot1dTrafficClassPriority OBJECT-TYPE 1236 SYNTAX Integer32 (0..7) 1237 MAX-ACCESS not-accessible 1238 STATUS current 1239 DESCRIPTION 1240 "The Priority value determined for the received frame. 1241 This value is equivalent to the priority indicated in 1242 the tagged frame received, or one of the evaluated 1243 priorities, determined according to the media-type. 1245 For untagged frames received from Ethernet media, this 1246 value is equal to the dot1dPortDefaultUserPriority value 1247 for the ingress port. 1249 For untagged frames received from non-Ethernet media, 1250 this value is equal to the dot1dRegenUserPriority value 1251 for the ingress port and media-specific user priority." 1252 ::= { dot1dTrafficClassEntry 1 } 1254 dot1dTrafficClass OBJECT-TYPE 1255 SYNTAX Integer32 (0..7) 1256 MAX-ACCESS read-write 1257 STATUS current 1258 DESCRIPTION 1259 "The Traffic Class the received frame is mapped to. 1261 The value of this object MUST be retained across 1262 reinitializations of the management system." 1263 ::= { dot1dTrafficClassEntry 2 } 1265 -- ------------------------------------------------------------- 1266 -- Outbound Access Priority Table 1267 -- ------------------------------------------------------------- 1269 dot1dPortOutboundAccessPriorityTable OBJECT-TYPE 1270 SYNTAX SEQUENCE OF Dot1dPortOutboundAccessPriorityEntry 1271 MAX-ACCESS not-accessible 1272 STATUS current 1273 DESCRIPTION 1274 "A table mapping Regenerated User Priority to Outbound 1275 Access Priority. This is a fixed mapping for all port 1276 types, with two options for 802.5 Token Ring." 1277 REFERENCE 1278 "ISO/IEC 15802-3 Table 7-3" 1279 ::= { dot1dPriority 4 } 1281 dot1dPortOutboundAccessPriorityEntry OBJECT-TYPE 1282 SYNTAX Dot1dPortOutboundAccessPriorityEntry 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "Regenerated User Priority to Outbound Access Priority 1287 mapping." 1288 INDEX { dot1dBasePort, dot1dRegenUserPriority } 1289 ::= { dot1dPortOutboundAccessPriorityTable 1 } 1291 Dot1dPortOutboundAccessPriorityEntry ::= 1292 SEQUENCE { 1293 dot1dPortOutboundAccessPriority 1294 Integer32 1295 } 1297 dot1dPortOutboundAccessPriority OBJECT-TYPE 1298 SYNTAX Integer32 (0..7) 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "The Outbound Access Priority the received frame is 1303 mapped to." 1304 ::= { dot1dPortOutboundAccessPriorityEntry 1 } 1306 -- ------------------------------------------------------------- 1307 -- the dot1dGarp subtree 1308 -- ------------------------------------------------------------- 1310 -- ------------------------------------------------------------- 1311 -- The GARP Port Table 1312 -- ------------------------------------------------------------- 1314 dot1dPortGarpTable OBJECT-TYPE 1315 SYNTAX SEQUENCE OF Dot1dPortGarpEntry 1316 MAX-ACCESS not-accessible 1317 STATUS current 1318 DESCRIPTION 1319 "A table of GARP control information about every bridge 1320 port. This is indexed by dot1dBasePort." 1321 ::= { dot1dGarp 1 } 1323 dot1dPortGarpEntry OBJECT-TYPE 1324 SYNTAX Dot1dPortGarpEntry 1325 MAX-ACCESS not-accessible 1326 STATUS current 1327 DESCRIPTION 1328 "GARP control information for a bridge port." 1329 AUGMENTS { dot1dBasePortEntry } 1330 ::= { dot1dPortGarpTable 1 } 1332 Dot1dPortGarpEntry ::= 1333 SEQUENCE { 1334 dot1dPortGarpJoinTime 1335 TimeInterval, 1336 dot1dPortGarpLeaveTime 1337 TimeInterval, 1338 dot1dPortGarpLeaveAllTime 1339 TimeInterval 1340 } 1342 dot1dPortGarpJoinTime OBJECT-TYPE 1343 SYNTAX TimeInterval 1344 MAX-ACCESS read-write 1345 STATUS current 1346 DESCRIPTION 1347 "The GARP Join time, in centiseconds. 1349 The value of this object MUST be retained across 1350 reinitializations of the management system." 1351 DEFVAL { 20 } 1352 ::= { dot1dPortGarpEntry 1 } 1354 dot1dPortGarpLeaveTime OBJECT-TYPE 1355 SYNTAX TimeInterval 1356 MAX-ACCESS read-write 1357 STATUS current 1358 DESCRIPTION 1359 "The GARP Leave time, in centiseconds. 1361 The value of this object MUST be retained across 1362 reinitializations of the management system." 1363 DEFVAL { 60 } 1364 ::= { dot1dPortGarpEntry 2 } 1366 dot1dPortGarpLeaveAllTime OBJECT-TYPE 1367 SYNTAX TimeInterval 1368 MAX-ACCESS read-write 1369 STATUS current 1370 DESCRIPTION 1371 "The GARP LeaveAll time, in centiseconds. 1373 The value of this object MUST be retained across 1374 reinitializations of the management system." 1375 DEFVAL { 1000 } 1376 ::= { dot1dPortGarpEntry 3 } 1378 -- ------------------------------------------------------------- 1379 -- The GMRP Port Configuration and Status Table 1380 -- ------------------------------------------------------------- 1382 dot1dPortGmrpTable OBJECT-TYPE 1383 SYNTAX SEQUENCE OF Dot1dPortGmrpEntry 1384 MAX-ACCESS not-accessible 1385 STATUS current 1386 DESCRIPTION 1387 "A table of GMRP control and status information about 1388 every bridge port. Augments the dot1dBasePortTable." 1389 ::= { dot1dGmrp 1 } 1391 dot1dPortGmrpEntry OBJECT-TYPE 1392 SYNTAX Dot1dPortGmrpEntry 1393 MAX-ACCESS not-accessible 1394 STATUS current 1395 DESCRIPTION 1396 "GMRP control and status information for a bridge port." 1397 AUGMENTS { dot1dBasePortEntry } 1398 ::= { dot1dPortGmrpTable 1 } 1400 Dot1dPortGmrpEntry ::= 1401 SEQUENCE { 1402 dot1dPortGmrpStatus 1403 EnabledStatus, 1404 dot1dPortGmrpFailedRegistrations 1405 Counter32, 1406 dot1dPortGmrpLastPduOrigin 1407 MacAddress, 1409 dot1dPortRestrictedGroupRegistration 1410 TruthValue 1411 } 1413 dot1dPortGmrpStatus OBJECT-TYPE 1414 SYNTAX EnabledStatus 1415 MAX-ACCESS read-write 1416 STATUS current 1417 DESCRIPTION 1418 "The administrative state of GMRP operation on this port. The 1419 value enabled(1) indicates that GMRP is enabled on this port 1420 in all VLANs as long as dot1dGmrpStatus is also enabled(1). 1421 A value of disabled(2) indicates that GMRP is disabled on 1422 this port in all VLANs: any GMRP packets received will 1423 be silently discarded and no GMRP registrations will be 1424 propagated from other ports. Setting this to a value of 1425 enabled(1) will be stored by the agent but will only take 1426 effect on the GMRP protocol operation if dot1dGmrpStatus 1427 also indicates the value enabled(1). This object affects 1428 all GMRP Applicant and Registrar state machines on this 1429 port. A transition from disabled(2) to enabled(1) will 1430 cause a reset of all GMRP state machines on this port. 1432 The value of this object MUST be retained across 1433 reinitializations of the management system." 1434 DEFVAL { enabled } 1435 ::= { dot1dPortGmrpEntry 1 } 1437 dot1dPortGmrpFailedRegistrations OBJECT-TYPE 1438 SYNTAX Counter32 1439 MAX-ACCESS read-only 1440 STATUS current 1441 DESCRIPTION 1442 "The total number of failed GMRP registrations, for any 1443 reason, in all VLANs, on this port." 1444 ::= { dot1dPortGmrpEntry 2 } 1446 dot1dPortGmrpLastPduOrigin OBJECT-TYPE 1447 SYNTAX MacAddress 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "The Source MAC Address of the last GMRP message 1452 received on this port." 1453 ::= { dot1dPortGmrpEntry 3 } 1455 dot1dPortRestrictedGroupRegistration OBJECT-TYPE 1456 SYNTAX TruthValue 1457 MAX-ACCESS read-write 1458 STATUS current 1459 DESCRIPTION 1460 "The state of Restricted Group Registration on this port. 1461 If the value of this control is true(1), then creation 1462 of a new dynamic entry is permitted only if there is a 1463 Static Filtering Entry for the VLAN concerned, in which 1464 the Registrar Administrative Control value is Normal 1465 Registration. 1467 The value of this object MUST be retained across 1468 reinitializations of the management system." 1469 REFERENCE 1470 "IEEE 802.1t clause 10.3.2.3, 14.10.1.3." 1471 DEFVAL { false } 1472 ::= { dot1dPortGmrpEntry 4 } 1474 -- ------------------------------------------------------------- 1475 -- High Capacity Port Table for Transparent Bridges 1476 -- ------------------------------------------------------------- 1478 dot1dTpHCPortTable OBJECT-TYPE 1479 SYNTAX SEQUENCE OF Dot1dTpHCPortEntry 1480 MAX-ACCESS not-accessible 1481 STATUS current 1482 DESCRIPTION 1483 "A table that contains information about every high 1484 capacity port that is associated with this transparent 1485 bridge." 1486 ::= { dot1dTp 5 } 1488 dot1dTpHCPortEntry OBJECT-TYPE 1489 SYNTAX Dot1dTpHCPortEntry 1490 MAX-ACCESS not-accessible 1491 STATUS current 1492 DESCRIPTION 1493 "Statistics information for each high capacity port of a 1494 transparent bridge." 1495 INDEX { dot1dTpPort } 1496 ::= { dot1dTpHCPortTable 1 } 1498 Dot1dTpHCPortEntry ::= 1499 SEQUENCE { 1500 dot1dTpHCPortInFrames 1501 Counter64, 1502 dot1dTpHCPortOutFrames 1503 Counter64, 1504 dot1dTpHCPortInDiscards 1505 Counter64 1506 } 1508 dot1dTpHCPortInFrames OBJECT-TYPE 1509 SYNTAX Counter64 1510 MAX-ACCESS read-only 1511 STATUS current 1512 DESCRIPTION 1513 "The number of frames that have been received by this 1514 port from its segment. Note that a frame received on 1515 the interface corresponding to this port is only counted 1516 by this object if and only if it is for a protocol being 1517 processed by the local bridging function, including 1518 bridge management frames." 1519 REFERENCE 1520 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1521 ::= { dot1dTpHCPortEntry 1 } 1523 dot1dTpHCPortOutFrames OBJECT-TYPE 1524 SYNTAX Counter64 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "The number of frames that have been transmitted by this 1529 port to its segment. Note that a frame transmitted on 1530 the interface corresponding to this port is only counted 1531 by this object if and only if it is for a protocol being 1532 processed by the local bridging function, including 1533 bridge management frames." 1534 REFERENCE 1535 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1536 ::= { dot1dTpHCPortEntry 2 } 1538 dot1dTpHCPortInDiscards OBJECT-TYPE 1539 SYNTAX Counter64 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "Count of valid frames that have been received by this 1544 port from its segment which were discarded (i.e., 1545 filtered) by the Forwarding Process." 1546 REFERENCE 1547 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1548 ::= { dot1dTpHCPortEntry 3 } 1550 -- ---------------------------------------------------- 1551 -- Upper part of High Capacity Port Table for Transparent Bridges 1552 -- ---------------------------------------------------- 1554 dot1dTpPortOverflowTable OBJECT-TYPE 1555 SYNTAX SEQUENCE OF Dot1dTpPortOverflowEntry 1556 MAX-ACCESS not-accessible 1557 STATUS current 1558 DESCRIPTION 1559 "A table that contains the most-significant bits of 1560 statistics counters for ports that are associated with this 1561 transparent bridge that are on high capacity interfaces, as 1562 defined in the conformance clauses for this table. This table 1563 is provided as a way to read 64-bit counters for agents which 1564 support only SNMPv1. 1566 Note that the reporting of most-significant and 1567 least-significant counter bits separately runs the risk of 1568 missing an overflow of the lower bits in the interval between 1569 sampling. The manager must be aware of this possibility, even 1570 within the same varbindlist, when interpreting the results of 1571 a request or asynchronous notification." 1572 ::= { dot1dTp 6 } 1574 dot1dTpPortOverflowEntry OBJECT-TYPE 1575 SYNTAX Dot1dTpPortOverflowEntry 1576 MAX-ACCESS not-accessible 1577 STATUS current 1578 DESCRIPTION 1579 "The most significant bits of statistics counters for a high 1580 capacity interface of a transparent bridge. Each object is 1581 associated with a corresponding object in dot1dTpPortTable 1582 which indicates the least significant bits of the counter." 1583 INDEX { dot1dTpPort } 1584 ::= { dot1dTpPortOverflowTable 1 } 1586 Dot1dTpPortOverflowEntry ::= 1587 SEQUENCE { 1588 dot1dTpPortInOverflowFrames 1589 Counter32, 1590 dot1dTpPortOutOverflowFrames 1591 Counter32, 1592 dot1dTpPortInOverflowDiscards 1593 Counter32 1594 } 1596 dot1dTpPortInOverflowFrames OBJECT-TYPE 1597 SYNTAX Counter32 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "The number of times the associated dot1dTpPortInFrames 1602 counter has overflowed." 1603 REFERENCE 1604 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1605 ::= { dot1dTpPortOverflowEntry 1 } 1607 dot1dTpPortOutOverflowFrames OBJECT-TYPE 1608 SYNTAX Counter32 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "The number of times the associated dot1dTpPortOutFrames 1613 counter has overflowed." 1614 REFERENCE 1615 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1616 ::= { dot1dTpPortOverflowEntry 2 } 1618 dot1dTpPortInOverflowDiscards OBJECT-TYPE 1619 SYNTAX Counter32 1620 MAX-ACCESS read-only 1621 STATUS current 1622 DESCRIPTION 1623 "The number of times the associated 1624 dot1dTpPortInDiscards counter has overflowed." 1625 REFERENCE 1626 "ISO/IEC 15802-3 Section 14.6.1.1.3" 1627 ::= { dot1dTpPortOverflowEntry 3 } 1629 -- ------------------------------------------------------------- 1630 -- IEEE 802.1p MIB - Conformance Information 1631 -- ------------------------------------------------------------- 1633 pBridgeConformance OBJECT IDENTIFIER ::= { pBridgeMIB 2 } 1635 pBridgeGroups OBJECT IDENTIFIER ::= { pBridgeConformance 1 } 1637 pBridgeCompliances OBJECT IDENTIFIER 1638 ::= { pBridgeConformance 2 } 1640 -- ------------------------------------------------------------- 1641 -- units of conformance 1642 -- ------------------------------------------------------------- 1644 pBridgeExtCapGroup OBJECT-GROUP 1645 OBJECTS { 1646 dot1dDeviceCapabilities, 1647 dot1dPortCapabilities 1648 } 1649 STATUS current 1650 DESCRIPTION 1651 "A collection of objects indicating the optional 1652 capabilities of the device." 1653 ::= { pBridgeGroups 1 } 1655 pBridgeDeviceGmrpGroup OBJECT-GROUP 1656 OBJECTS { 1657 dot1dGmrpStatus 1658 } 1659 STATUS current 1660 DESCRIPTION 1661 "A collection of objects providing device-level control 1662 for the Multicast Filtering extended bridge services." 1663 ::= { pBridgeGroups 2 } 1665 pBridgeDevicePriorityGroup OBJECT-GROUP 1666 OBJECTS { 1667 dot1dTrafficClassesEnabled 1668 } 1669 STATUS current 1670 DESCRIPTION 1671 "A collection of objects providing device-level control 1672 for the Priority services." 1673 ::= { pBridgeGroups 3 } 1675 pBridgeDefaultPriorityGroup OBJECT-GROUP 1676 OBJECTS { 1677 dot1dPortDefaultUserPriority 1678 } 1679 STATUS current 1680 DESCRIPTION 1681 "A collection of objects defining the User Priority 1682 applicable to each port for media which do not support 1683 native User Priority." 1684 ::= { pBridgeGroups 4 } 1686 pBridgeRegenPriorityGroup OBJECT-GROUP 1687 OBJECTS { 1688 dot1dRegenUserPriority 1689 } 1690 STATUS current 1691 DESCRIPTION 1692 "A collection of objects defining the User Priorities 1693 applicable to each port for media which support native 1694 User Priority." 1695 ::= { pBridgeGroups 5 } 1697 pBridgePriorityGroup OBJECT-GROUP 1698 OBJECTS { 1699 dot1dPortNumTrafficClasses, 1700 dot1dTrafficClass 1701 } 1702 STATUS current 1703 DESCRIPTION 1704 "A collection of objects defining the traffic classes 1705 within a bridge for each evaluated User Priority." 1706 ::= { pBridgeGroups 6 } 1708 pBridgeAccessPriorityGroup OBJECT-GROUP 1709 OBJECTS { 1710 dot1dPortOutboundAccessPriority 1711 } 1712 STATUS current 1713 DESCRIPTION 1714 "A collection of objects defining the media dependent 1715 outbound access level for each priority." 1716 ::= { pBridgeGroups 7 } 1718 pBridgePortGarpGroup OBJECT-GROUP 1719 OBJECTS { 1720 dot1dPortGarpJoinTime, 1721 dot1dPortGarpLeaveTime, 1722 dot1dPortGarpLeaveAllTime 1723 } 1724 STATUS current 1725 DESCRIPTION 1726 "A collection of objects providing port level control 1727 and status information for GARP operation." 1728 ::= { pBridgeGroups 8 } 1730 pBridgePortGmrpGroup OBJECT-GROUP 1731 OBJECTS { 1732 dot1dPortGmrpStatus, 1733 dot1dPortGmrpFailedRegistrations, 1734 dot1dPortGmrpLastPduOrigin 1735 } 1736 STATUS deprecated 1737 DESCRIPTION 1738 "A collection of objects providing port level control 1739 and status information for GMRP operation." 1740 ::= { pBridgeGroups 9 } 1742 pBridgeHCPortGroup OBJECT-GROUP 1743 OBJECTS { 1744 dot1dTpHCPortInFrames, 1745 dot1dTpHCPortOutFrames, 1746 dot1dTpHCPortInDiscards 1747 } 1748 STATUS current 1749 DESCRIPTION 1750 "A collection of objects providing 64-bit statistics 1751 counters for high capacity bridge ports." 1752 ::= { pBridgeGroups 10 } 1754 pBridgePortOverflowGroup OBJECT-GROUP 1755 OBJECTS { 1756 dot1dTpPortInOverflowFrames, 1757 dot1dTpPortOutOverflowFrames, 1758 dot1dTpPortInOverflowDiscards 1759 } 1760 STATUS current 1761 DESCRIPTION 1762 "A collection of objects providing overflow statistics 1763 counters for high capacity bridge ports." 1764 ::= { pBridgeGroups 11 } 1766 pBridgePortGmrpGroup2 OBJECT-GROUP 1767 OBJECTS { 1768 dot1dPortGmrpStatus, 1769 dot1dPortGmrpFailedRegistrations, 1770 dot1dPortGmrpLastPduOrigin, 1771 dot1dPortRestrictedGroupRegistration 1772 } 1773 STATUS current 1774 DESCRIPTION 1775 "A collection of objects providing port level control 1776 and status information for GMRP operation." 1777 ::= { pBridgeGroups 12 } 1779 -- ------------------------------------------------------------- 1780 -- compliance statements 1781 -- ------------------------------------------------------------- 1783 pBridgeCompliance MODULE-COMPLIANCE 1784 STATUS deprecated 1785 DESCRIPTION 1786 "The compliance statement for device support of Priority 1787 and Multicast Filtering extended bridging services." 1789 MODULE 1790 MANDATORY-GROUPS { pBridgeExtCapGroup } 1792 GROUP pBridgeDeviceGmrpGroup 1793 DESCRIPTION 1794 "This group is mandatory for devices supporting the GMRP 1795 application, defined by IEEE 802.1D Extended Filtering 1796 Services." 1798 GROUP pBridgeDevicePriorityGroup 1799 DESCRIPTION 1800 "This group is mandatory only for devices supporting 1801 the priority forwarding operations defined by IEEE 1802 802.1D." 1804 GROUP pBridgeDefaultPriorityGroup 1805 DESCRIPTION 1806 "This group is mandatory only for devices supporting 1807 the priority forwarding operations defined by the 1808 extended bridge services with media types, such as 1809 Ethernet, that do not support native User Priority." 1811 GROUP pBridgeRegenPriorityGroup 1812 DESCRIPTION 1813 "This group is mandatory only for devices supporting 1814 the priority forwarding operations defined by IEEE 802.1D 1815 and which have interface media types that support 1816 native User Priority e.g. IEEE 802.5." 1818 GROUP pBridgePriorityGroup 1819 DESCRIPTION 1820 "This group is mandatory only for devices supporting 1821 the priority forwarding operations defined by IEEE 802.1D." 1823 GROUP pBridgeAccessPriorityGroup 1824 DESCRIPTION 1825 "This group is optional and is relevant only for devices 1826 supporting the priority forwarding operations defined by 1827 IEEE 802.1D and which have interface media types that 1828 support native Access Priority e.g. IEEE 802.5." 1830 GROUP pBridgePortGarpGroup 1831 DESCRIPTION 1832 "This group is mandatory for devices supporting any 1833 of the GARP applications: e.g. GMRP, defined by the 1834 extended filtering services of 802.1D; or GVRP, 1835 defined by 802.1Q (refer to the Q-BRIDGE-MIB for 1836 conformance statements for GVRP)." 1838 GROUP pBridgePortGmrpGroup 1839 DESCRIPTION 1840 "This group is mandatory for devices supporting the 1841 GMRP application, as defined by IEEE 802.1D Extended 1842 Filtering Services." 1844 GROUP pBridgeHCPortGroup 1845 DESCRIPTION 1846 "Support for this group in a device is mandatory for those 1847 bridge ports which map to network interfaces that have the 1848 value of the corresponding instance of ifSpeed 1849 greater than 650,000,000 bits/second." 1851 GROUP pBridgePortOverflowGroup 1852 DESCRIPTION 1853 "Support for this group in a device is mandatory for those 1854 bridge ports which map to network interfaces that have the 1855 value of the corresponding instance of ifSpeed 1856 greater than 650,000,000 bits/second." 1858 OBJECT dot1dPortNumTrafficClasses 1859 MIN-ACCESS read-only 1860 DESCRIPTION 1861 "Write access is not required." 1863 OBJECT dot1dTrafficClass 1864 MIN-ACCESS read-only 1865 DESCRIPTION 1866 "Write access is not required." 1868 OBJECT dot1dRegenUserPriority 1869 MIN-ACCESS read-only 1870 DESCRIPTION 1871 "Write access is not required." 1873 ::= { pBridgeCompliances 1 } 1875 pBridgeCompliance2 MODULE-COMPLIANCE 1876 STATUS current 1877 DESCRIPTION 1878 "The compliance statement for device support of Priority 1879 and Multicast Filtering extended bridging services." 1881 MODULE 1882 MANDATORY-GROUPS { pBridgeExtCapGroup } 1884 GROUP pBridgeDeviceGmrpGroup 1885 DESCRIPTION 1886 "This group is mandatory for devices supporting the GMRP 1887 application, defined by IEEE 802.1D Extended Filtering 1888 Services." 1890 GROUP pBridgeDevicePriorityGroup 1891 DESCRIPTION 1892 "This group is mandatory only for devices supporting 1893 the priority forwarding operations defined by IEEE 1894 802.1D." 1896 GROUP pBridgeDefaultPriorityGroup 1897 DESCRIPTION 1898 "This group is mandatory only for devices supporting 1899 the priority forwarding operations defined by the 1900 extended bridge services with media types, such as 1901 Ethernet, that do not support native User Priority." 1903 GROUP pBridgeRegenPriorityGroup 1904 DESCRIPTION 1905 "This group is mandatory only for devices supporting 1906 the priority forwarding operations defined by IEEE 802.1D 1907 and which have interface media types that support 1908 native User Priority e.g. IEEE 802.5." 1910 GROUP pBridgePriorityGroup 1911 DESCRIPTION 1912 "This group is mandatory only for devices supporting 1913 the priority forwarding operations defined by IEEE 802.1D." 1915 GROUP pBridgeAccessPriorityGroup 1916 DESCRIPTION 1917 "This group is optional and is relevant only for devices 1918 supporting the priority forwarding operations defined by 1919 IEEE 802.1D and which have interface media types that 1920 support native Access Priority e.g. IEEE 802.5." 1922 GROUP pBridgePortGarpGroup 1923 DESCRIPTION 1924 "This group is mandatory for devices supporting any 1925 of the GARP applications: e.g. GMRP, defined by the 1926 extended filtering services of 802.1D; or GVRP, 1927 defined by 802.1Q (refer to the Q-BRIDGE-MIB for 1928 conformance statements for GVRP)." 1930 GROUP pBridgePortGmrpGroup2 1931 DESCRIPTION 1932 "This group is mandatory for devices supporting the 1933 GMRP application, as defined by IEEE 802.1D Extended 1934 Filtering Services." 1936 GROUP pBridgeHCPortGroup 1937 DESCRIPTION 1938 "Support for this group in a device is mandatory for those 1939 bridge ports which map to network interfaces that have the 1940 value of the corresponding instance of ifSpeed 1941 greater than 650,000,000 bits/second." 1943 GROUP pBridgePortOverflowGroup 1944 DESCRIPTION 1945 "Support for this group in a device is mandatory for those 1946 bridge ports which map to network interfaces that have the 1947 value of the corresponding instance of ifSpeed 1948 greater than 650,000,000 bits/second." 1950 OBJECT dot1dPortNumTrafficClasses 1951 MIN-ACCESS read-only 1952 DESCRIPTION 1953 "Write access is not required." 1955 OBJECT dot1dTrafficClass 1956 MIN-ACCESS read-only 1957 DESCRIPTION 1958 "Write access is not required." 1960 OBJECT dot1dRegenUserPriority 1961 MIN-ACCESS read-only 1962 DESCRIPTION 1963 "Write access is not required." 1965 ::= { pBridgeCompliances 2 } 1967 END 1969 5. Definitions for Virtual Bridge MIB 1971 Q-BRIDGE-MIB DEFINITIONS ::= BEGIN 1973 -- ------------------------------------------------------------- 1974 -- MIB for IEEE 802.1Q Devices 1975 -- ------------------------------------------------------------- 1977 IMPORTS 1978 MODULE-IDENTITY, OBJECT-TYPE, 1979 Counter32, Counter64, Unsigned32, TimeTicks, Integer32 1980 FROM SNMPv2-SMI 1981 RowStatus, TruthValue, TEXTUAL-CONVENTION, MacAddress 1982 FROM SNMPv2-TC 1983 SnmpAdminString 1984 FROM SNMP-FRAMEWORK-MIB 1985 MODULE-COMPLIANCE, OBJECT-GROUP 1986 FROM SNMPv2-CONF 1987 dot1dBridge, dot1dBasePortEntry, dot1dBasePort 1988 FROM BRIDGE-MIB 1989 EnabledStatus 1990 FROM P-BRIDGE-MIB 1991 TimeFilter 1992 FROM RMON2-MIB; 1994 qBridgeMIB MODULE-IDENTITY 1995 LAST-UPDATED "200507290000Z" 1996 ORGANIZATION "IETF Bridge MIB Working Group" 1997 CONTACT-INFO 1998 "Email: Bridge-mib@ietf.org 1999 ietfmibs@ops.ietf.org 2001 David Levi 2002 Postal: Nortel Networks 2003 4655 Great America Parkway 2004 Santa Clara, CA 95054 2005 USA 2006 Phone: +1 865 686 0432 2007 Email: dlevi@nortel.com 2009 David Harrington 2010 Postal: Effective Software 2011 50 Harding Rd. 2012 Portsmouth, NH 03801 2013 USA 2014 Phone: +1 603 436 8634 2015 Email: ietfdbh@comcast.net 2017 Les Bell 2018 Postal: Hemel Hempstead, Herts. HP2 7YU 2019 UK 2020 Email: elbell@ntlworld.com 2022 Andrew Smith 2023 Postal: Beijing Harbour Networks 2024 Jiuling Building 2025 21 North Xisanhuan Ave. 2026 Beijing, 100089 2027 PRC 2028 Fax: +1 415 345 1827 2029 Email: ah_smith@acm.org 2031 Paul Langille 2032 Postal: Newbridge Networks 2033 5 Corporate Drive 2034 Andover, MA 01810 2035 USA 2036 Phone: +1 978 691 4665 2037 Email: langille@newbridge.com 2039 Anil Rijhsinghani 2040 Postal: Accton Technology Corporation 2041 5 Mount Royal Ave 2042 Marlboro, MA 01752 2043 USA 2044 Phone: 2045 Email: anil@accton.com 2047 Keith McCloghrie 2048 Postal: Cisco Systems, Inc. 2049 170 West Tasman Drive 2050 San Jose, CA 95134-1706 2051 USA 2052 Phone: +1 408 526 5260 2053 Email: kzm@cisco.com" 2054 DESCRIPTION 2055 "The VLAN Bridge MIB module for managing Virtual Bridged 2056 Local Area Networks, as defined by IEEE 802.1Q-2003, 2057 including Restricted Vlan Registration defined by 2058 IEEE 802.1u-2001 and Vlan Classification defined by 2059 IEEE 802.1v-2001. 2061 Copyright (C) The Internet Society (2005). This version of 2062 this MIB module is part of RFC XXXX; See the RFC itself for 2063 full legal notices." 2064 -- NOTE to RFC editor: replace XXXX with actual RFC number 2065 -- for this document and remove this note 2067 REVISION "200507290000Z" 2068 DESCRIPTION 2069 "Added Vlan TEXTUAL-CONVENTIONs, 2070 dot1qPortRestrictedVlanRegistration, dot1vProtocol subtree, 2071 qBridgeClassificationDeviceGroup, qBridgePortGroup2, 2072 qBridgeClassificationPortGroup, and qBridgeCompliance2. 2073 Clarified dot1qForwardAllStaticPorts, 2074 qPortAcceptableFrameTypes, and qBridgeCompliance. 2075 Deprecated qBridgePortGroup and qBridgeCompliance. " 2077 REVISION "199908250000Z" 2078 DESCRIPTION 2079 "The VLAN Bridge MIB module for managing Virtual Bridged 2080 Local Area Networks, as defined by IEEE 802.1Q-1998. 2082 Initial version, published as RFC 2674." 2084 ::= { dot1dBridge 7 } 2086 qBridgeMIBObjects OBJECT IDENTIFIER ::= { qBridgeMIB 1 } 2088 -- ------------------------------------------------------------- 2089 -- Textual Conventions 2090 -- ------------------------------------------------------------- 2092 PortList ::= TEXTUAL-CONVENTION 2093 STATUS current 2094 DESCRIPTION 2095 "Each octet within this value specifies a set of eight 2096 ports, with the first octet specifying ports 1 through 2097 8, the second octet specifying ports 9 through 16, etc. 2098 Within each octet, the most significant bit represents 2099 the lowest numbered port, and the least significant bit 2100 represents the highest numbered port. Thus, each port 2101 of the bridge is represented by a single bit within the 2102 value of this object. If that bit has a value of '1' 2103 then that port is included in the set of ports; the port 2104 is not included if its bit has a value of '0'." 2105 SYNTAX OCTET STRING 2107 VlanIndex ::= TEXTUAL-CONVENTION 2108 DISPLAY-HINT "d" 2109 STATUS current 2110 DESCRIPTION 2111 "A value used to index per-VLAN tables: values of 0 and 2112 4095 are not permitted; if the value is between 1 and 2113 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with 2114 global scope within a given bridged domain (see VlanId 2115 textual convention). If the value is greater than 4095 2116 then it represents a VLAN with scope local to the 2117 particular agent, i.e. one without a global VLAN-ID 2118 assigned to it. Such VLANs are outside the scope of 2119 IEEE 802.1Q but it is convenient to be able to manage them 2120 in the same way using this MIB." 2121 SYNTAX Unsigned32 2123 VlanId ::= TEXTUAL-CONVENTION 2124 DISPLAY-HINT "d" 2125 STATUS current 2126 DESCRIPTION 2127 "The VLAN ID that uniquely identifies a VLAN. This 2128 is the 12-bit VLAN ID used in the VLAN Tag header. 2129 The range is defined by the REFERENCEd specification." 2130 REFERENCE 2131 "IEEE Std 802.1Q 2003 Edition, Virtual Bridged 2132 Local Area Networks." 2133 SYNTAX Integer32 (1..4094) 2135 VlanIdOrAny ::= TEXTUAL-CONVENTION 2136 DISPLAY-HINT "d" 2137 STATUS current 2138 DESCRIPTION 2139 "The VLAN ID that uniquely identifies a specific VLAN, 2140 or any VLAN. The special value of 4095 is used to 2141 indicate a wildcard, i.e. any VLAN. This can be used 2142 in any situation where an object or table entry must 2143 refer either to a specific VLAN or to any VLAN. 2145 Note that a MIB object that is defined using this 2146 TEXTUAL-CONVENTION should clarify the meaning of 2147 'any VLAN' (i.e., the special value 4095)." 2148 SYNTAX Integer32 (1..4094 | 4095) 2150 VlanIdOrNone ::= TEXTUAL-CONVENTION 2151 DISPLAY-HINT "d" 2152 STATUS current 2153 DESCRIPTION 2154 "The VLAN ID that uniquely identifies a specific VLAN, 2155 or no VLAN. The special value of zero is used to 2156 indicate that no VLAN ID is present or used. This can 2157 be used in any situation where an object or a table entry 2158 must refer either to a specific VLAN, or to no VLAN. 2160 Note that a MIB object that is defined using this 2161 TEXTUAL-CONVENTION should clarify the meaning of 2162 'no VLAN' (i.e., the special value 0)." 2163 SYNTAX Integer32 (0 | 1..4094) 2165 VlanIdOrAnyOrNone ::= TEXTUAL-CONVENTION 2166 DISPLAY-HINT "d" 2167 STATUS current 2168 DESCRIPTION 2169 "The VLAN ID that uniquely identifies a specific VLAN, 2170 any VLAN, or no VLAN. The special values 0 and 4095 2171 have the same meaning as described in the VlanIdOrAny 2172 and VlanIdOrNone TEXTUAL-CONVENTIONs. 2174 Note that a MIB object that is defined using this 2175 TEXTUAL-CONVENTION should clarify the meaning of 2176 'any VLAN' and 'no VLAN' (i.e., the special values 2177 0 and 4095)." 2178 SYNTAX Integer32 (0 | 1..4094 | 4095) 2180 -- ------------------------------------------------------------- 2181 -- subtrees in the Q-BRIDGE MIB 2182 -- ------------------------------------------------------------- 2184 dot1qBase OBJECT IDENTIFIER ::= { qBridgeMIBObjects 1 } 2185 dot1qTp OBJECT IDENTIFIER ::= { qBridgeMIBObjects 2 } 2186 dot1qStatic OBJECT IDENTIFIER ::= { qBridgeMIBObjects 3 } 2187 dot1qVlan OBJECT IDENTIFIER ::= { qBridgeMIBObjects 4 } 2188 dot1vProtocol OBJECT IDENTIFIER ::= { qBridgeMIBObjects 5 } 2190 -- ------------------------------------------------------------- 2191 -- dot1qBase subtree 2192 -- ------------------------------------------------------------- 2194 dot1qVlanVersionNumber OBJECT-TYPE 2195 SYNTAX INTEGER { 2196 version1(1) 2197 } 2198 MAX-ACCESS read-only 2199 STATUS current 2200 DESCRIPTION 2201 "The version number of IEEE 802.1Q that this device 2202 supports." 2203 REFERENCE 2204 "IEEE 802.1Q/D11 Section 12.10.1.1" 2205 ::= { dot1qBase 1 } 2207 dot1qMaxVlanId OBJECT-TYPE 2208 SYNTAX VlanId 2209 MAX-ACCESS read-only 2210 STATUS current 2211 DESCRIPTION 2212 "The maximum IEEE 802.1Q VLAN ID that this device 2213 supports." 2214 REFERENCE 2215 "IEEE 802.1Q/D11 Section 9.3.2.3" 2216 ::= { dot1qBase 2 } 2218 dot1qMaxSupportedVlans OBJECT-TYPE 2219 SYNTAX Unsigned32 2220 MAX-ACCESS read-only 2221 STATUS current 2222 DESCRIPTION 2223 "The maximum number of IEEE 802.1Q VLANs that this 2224 device supports." 2225 REFERENCE 2226 "IEEE 802.1Q/D11 Section 12.10.1.1" 2227 ::= { dot1qBase 3 } 2229 dot1qNumVlans OBJECT-TYPE 2230 SYNTAX Unsigned32 2231 MAX-ACCESS read-only 2232 STATUS current 2233 DESCRIPTION 2234 "The current number of IEEE 802.1Q VLANs that are 2235 configured in this device." 2236 REFERENCE 2237 "IEEE 802.1Q/D11 Section 12.7.1.1" 2238 ::= { dot1qBase 4 } 2240 dot1qGvrpStatus OBJECT-TYPE 2241 SYNTAX EnabledStatus 2242 MAX-ACCESS read-write 2243 STATUS current 2244 DESCRIPTION 2245 "The administrative status requested by management for 2246 GVRP. The value enabled(1) indicates that GVRP should 2247 be enabled on this device, on all ports for which it has 2248 not been specifically disabled. When disabled(2), GVRP 2249 is disabled on all ports and all GVRP packets will be 2250 forwarded transparently. This object affects all GVRP 2251 Applicant and Registrar state machines. A transition 2252 from disabled(2) to enabled(1) will cause a reset of all 2253 GVRP state machines on all ports. 2255 The value of this object MUST be retained across 2256 reinitializations of the management system." 2257 DEFVAL { enabled } 2258 ::= { dot1qBase 5 } 2260 -- ------------------------------------------------------------- 2261 -- the dot1qTp subtree 2262 -- ------------------------------------------------------------- 2264 -- ------------------------------------------------------------- 2265 -- the current Filtering Database Table 2266 -- ------------------------------------------------------------- 2268 dot1qFdbTable OBJECT-TYPE 2269 SYNTAX SEQUENCE OF Dot1qFdbEntry 2270 MAX-ACCESS not-accessible 2271 STATUS current 2272 DESCRIPTION 2273 "A table that contains configuration and control 2274 information for each Filtering Database currently 2275 operating on this device. Entries in this table appear 2276 automatically when VLANs are assigned FDB IDs in the 2277 dot1qVlanCurrentTable." 2278 ::= { dot1qTp 1 } 2280 dot1qFdbEntry OBJECT-TYPE 2281 SYNTAX Dot1qFdbEntry 2282 MAX-ACCESS not-accessible 2283 STATUS current 2284 DESCRIPTION 2285 "Information about a specific Filtering Database." 2286 INDEX { dot1qFdbId } 2287 ::= { dot1qFdbTable 1 } 2289 Dot1qFdbEntry ::= 2290 SEQUENCE { 2291 dot1qFdbId 2292 Unsigned32, 2293 dot1qFdbDynamicCount 2294 Counter32 2295 } 2297 dot1qFdbId OBJECT-TYPE 2298 SYNTAX Unsigned32 2299 MAX-ACCESS not-accessible 2300 STATUS current 2301 DESCRIPTION 2302 "The identity of this Filtering Database." 2303 ::= { dot1qFdbEntry 1 } 2305 dot1qFdbDynamicCount OBJECT-TYPE 2306 SYNTAX Counter32 2307 MAX-ACCESS read-only 2308 STATUS current 2309 DESCRIPTION 2310 "The current number of dynamic entries in this 2311 Filtering Database." 2312 REFERENCE 2313 "IEEE 802.1Q/D11 Section 12.7.1.1.3" 2314 ::= { dot1qFdbEntry 2 } 2316 -- ------------------------------------------------------------- 2317 -- Multiple Forwarding Databases for 802.1Q Transparent devices 2318 -- This table is an alternative to the dot1dTpFdbTable, 2319 -- previously defined for 802.1D devices which only support a 2320 -- single Forwarding Database. 2321 -- ------------------------------------------------------------- 2323 dot1qTpFdbTable OBJECT-TYPE 2324 SYNTAX SEQUENCE OF Dot1qTpFdbEntry 2325 MAX-ACCESS not-accessible 2326 STATUS current 2327 DESCRIPTION 2328 "A table that contains information about unicast entries 2329 for which the device has forwarding and/or filtering 2330 information. This information is used by the 2331 transparent bridging function in determining how to 2332 propagate a received frame." 2333 REFERENCE 2334 "IEEE 802.1Q/D11 Section 12.7.7" 2335 ::= { dot1qTp 2 } 2337 dot1qTpFdbEntry OBJECT-TYPE 2338 SYNTAX Dot1qTpFdbEntry 2339 MAX-ACCESS not-accessible 2340 STATUS current 2341 DESCRIPTION 2342 "Information about a specific unicast MAC address for 2343 which the device has some forwarding and/or filtering 2344 information." 2345 INDEX { dot1qFdbId, dot1qTpFdbAddress } 2346 ::= { dot1qTpFdbTable 1 } 2348 Dot1qTpFdbEntry ::= 2349 SEQUENCE { 2350 dot1qTpFdbAddress 2351 MacAddress, 2352 dot1qTpFdbPort 2353 Integer32, 2354 dot1qTpFdbStatus 2355 INTEGER 2356 } 2358 dot1qTpFdbAddress OBJECT-TYPE 2359 SYNTAX MacAddress 2360 MAX-ACCESS not-accessible 2361 STATUS current 2362 DESCRIPTION 2363 "A unicast MAC address for which the device has 2364 forwarding and/or filtering information." 2365 ::= { dot1qTpFdbEntry 1 } 2367 dot1qTpFdbPort OBJECT-TYPE 2368 SYNTAX Integer32 (0..65535) 2369 MAX-ACCESS read-only 2370 STATUS current 2371 DESCRIPTION 2372 "Either the value '0', or the port number of the port on 2373 which a frame having a source address equal to the value 2374 of the corresponding instance of dot1qTpFdbAddress has 2375 been seen. A value of '0' indicates that the port 2376 number has not been learned but that the device does 2377 have some forwarding/filtering information about this 2378 address (e.g. in the dot1qStaticUnicastTable). 2379 Implementors are encouraged to assign the port value to 2380 this object whenever it is learned even for addresses 2381 for which the corresponding value of dot1qTpFdbStatus is 2382 not learned(3)." 2383 ::= { dot1qTpFdbEntry 2 } 2385 dot1qTpFdbStatus OBJECT-TYPE 2386 SYNTAX INTEGER { 2387 other(1), 2388 invalid(2), 2389 learned(3), 2390 self(4), 2391 mgmt(5) 2392 } 2393 MAX-ACCESS read-only 2394 STATUS current 2395 DESCRIPTION 2396 "The status of this entry. The meanings of the values 2397 are: 2398 other(1) - none of the following. This may include 2399 the case where some other MIB object (not the 2400 corresponding instance of dot1qTpFdbPort, nor an 2401 entry in the dot1qStaticUnicastTable) is being 2402 used to determine if and how frames addressed to 2403 the value of the corresponding instance of 2404 dot1qTpFdbAddress are being forwarded. 2405 invalid(2) - this entry is no longer valid (e.g., it 2406 was learned but has since aged out), but has not 2407 yet been flushed from the table. 2408 learned(3) - the value of the corresponding instance 2409 of dot1qTpFdbPort was learned and is being used. 2410 self(4) - the value of the corresponding instance of 2411 dot1qTpFdbAddress represents one of the device's 2412 addresses. The corresponding instance of 2413 dot1qTpFdbPort indicates which of the device's 2414 ports has this address. 2415 mgmt(5) - the value of the corresponding instance of 2416 dot1qTpFdbAddress is also the value of an 2417 existing instance of dot1qStaticAddress." 2418 ::= { dot1qTpFdbEntry 3 } 2420 -- ------------------------------------------------------------- 2421 -- Dynamic Group Registration Table 2422 -- ------------------------------------------------------------- 2424 dot1qTpGroupTable OBJECT-TYPE 2425 SYNTAX SEQUENCE OF Dot1qTpGroupEntry 2426 MAX-ACCESS not-accessible 2427 STATUS current 2428 DESCRIPTION 2429 "A table containing filtering information for VLANs 2430 configured into the bridge by (local or network) 2431 management, or learnt dynamically, specifying the set of 2432 ports to which frames received on a VLAN for this FDB 2433 and containing a specific Group destination address are 2434 allowed to be forwarded." 2435 ::= { dot1qTp 3 } 2437 dot1qTpGroupEntry OBJECT-TYPE 2438 SYNTAX Dot1qTpGroupEntry 2439 MAX-ACCESS not-accessible 2440 STATUS current 2441 DESCRIPTION 2442 "Filtering information configured into the bridge by 2443 management, or learnt dynamically, specifying the set of 2444 ports to which frames received on a VLAN and containing 2445 a specific Group destination address, are allowed to be 2446 forwarded. The subset of these ports learnt dynamically 2447 is also provided." 2448 INDEX { dot1qVlanIndex, dot1qTpGroupAddress } 2449 ::= { dot1qTpGroupTable 1 } 2451 Dot1qTpGroupEntry ::= 2452 SEQUENCE { 2453 dot1qTpGroupAddress 2454 MacAddress, 2455 dot1qTpGroupEgressPorts 2456 PortList, 2457 dot1qTpGroupLearnt 2458 PortList 2459 } 2461 dot1qTpGroupAddress OBJECT-TYPE 2462 SYNTAX MacAddress 2463 MAX-ACCESS not-accessible 2464 STATUS current 2465 DESCRIPTION 2466 "The destination Group MAC address in a frame to which 2467 this entry's filtering information applies." 2468 ::= { dot1qTpGroupEntry 1 } 2470 dot1qTpGroupEgressPorts OBJECT-TYPE 2471 SYNTAX PortList 2472 MAX-ACCESS read-only 2473 STATUS current 2474 DESCRIPTION 2475 "The complete set of ports, in this VLAN, to which 2476 frames destined for this Group MAC address are currently 2477 being explicitly forwarded. This does not include ports 2478 for which this address is only implicitly forwarded, in 2479 the dot1qForwardAllPorts list." 2480 ::= { dot1qTpGroupEntry 2 } 2482 dot1qTpGroupLearnt OBJECT-TYPE 2483 SYNTAX PortList 2484 MAX-ACCESS read-only 2485 STATUS current 2486 DESCRIPTION 2487 "The subset of ports in dot1qTpGroupEgressPorts which 2488 were learnt by GMRP or some other dynamic mechanism, in 2489 this Filtering database." 2490 ::= { dot1qTpGroupEntry 3 } 2492 -- ------------------------------------------------------------- 2493 -- Service Requirements subtree 2494 -- ------------------------------------------------------------- 2496 dot1qForwardAllTable OBJECT-TYPE 2497 SYNTAX SEQUENCE OF Dot1qForwardAllEntry 2498 MAX-ACCESS not-accessible 2499 STATUS current 2500 DESCRIPTION 2501 "A table containing forwarding information for each 2502 VLAN, specifying the set of ports to which forwarding of 2503 all multicasts applies, configured statically by 2504 management or dynamically by GMRP. An entry appears in 2505 this table for all VLANs that are currently 2506 instantiated." 2507 REFERENCE 2508 "IEEE 802.1Q/D11 Section 12.7.2, 12.7.7" 2509 ::= { dot1qTp 4 } 2511 dot1qForwardAllEntry OBJECT-TYPE 2512 SYNTAX Dot1qForwardAllEntry 2513 MAX-ACCESS not-accessible 2514 STATUS current 2515 DESCRIPTION 2516 "Forwarding information for a VLAN, specifying the set 2517 of ports to which all multicasts should be forwarded, 2518 configured statically by management or dynamically by 2519 GMRP." 2520 INDEX { dot1qVlanIndex } 2521 ::= { dot1qForwardAllTable 1 } 2523 Dot1qForwardAllEntry ::= 2524 SEQUENCE { 2525 dot1qForwardAllPorts 2526 PortList, 2527 dot1qForwardAllStaticPorts 2528 PortList, 2529 dot1qForwardAllForbiddenPorts 2530 PortList 2531 } 2533 dot1qForwardAllPorts OBJECT-TYPE 2534 SYNTAX PortList 2535 MAX-ACCESS read-only 2536 STATUS current 2537 DESCRIPTION 2538 "The complete set of ports in this VLAN to which all 2539 multicast group-addressed frames are to be forwarded. 2540 This includes ports for which this need has been 2541 determined dynamically by GMRP, or configured statically 2542 by management." 2543 ::= { dot1qForwardAllEntry 1 } 2545 dot1qForwardAllStaticPorts OBJECT-TYPE 2546 SYNTAX PortList 2547 MAX-ACCESS read-write 2548 STATUS current 2549 DESCRIPTION 2550 "The set of ports configured by management in this VLAN 2551 to which all multicast group-addressed frames are to be 2552 forwarded. Ports entered in this list will also appear 2553 in the complete set shown by dot1qForwardAllPorts. This 2554 value will be restored after the device is reset. This 2555 only applies to ports that are members of the VLAN, 2556 defined by dot1qVlanCurrentEgressPorts. A port may not 2557 be added in this set if it is already a member of the 2558 set of ports in dot1qForwardAllForbiddenPorts. The 2559 default value is a string of ones of appropriate length, 2560 to indicate the standard behaviour of using basic 2561 filtering services, i.e. forward all multicasts to all 2562 ports. 2564 The value of this object MUST be retained across 2565 reinitializations of the management system." 2566 ::= { dot1qForwardAllEntry 2 } 2568 dot1qForwardAllForbiddenPorts OBJECT-TYPE 2569 SYNTAX PortList 2570 MAX-ACCESS read-write 2571 STATUS current 2572 DESCRIPTION 2573 "The set of ports configured by management in this VLAN 2574 for which the Service Requirement attribute Forward All 2575 Multicast Groups may not be dynamically registered by 2576 GMRP. This value will be restored after the device is 2577 reset. A port may not be added in this set if it is 2578 already a member of the set of ports in 2579 dot1qForwardAllStaticPorts. The default value is a 2580 string of zeros of appropriate length. 2582 The value of this object MUST be retained across 2583 reinitializations of the management system." 2584 ::= { dot1qForwardAllEntry 3 } 2586 dot1qForwardUnregisteredTable OBJECT-TYPE 2587 SYNTAX SEQUENCE OF Dot1qForwardUnregisteredEntry 2588 MAX-ACCESS not-accessible 2589 STATUS current 2590 DESCRIPTION 2591 "A table containing forwarding information for each 2592 VLAN, specifying the set of ports to which forwarding of 2593 multicast group-addressed frames for which there is no 2594 more specific forwarding information applies. This is 2595 configured statically by management and determined 2596 dynamically by GMRP. An entry appears in this table for 2597 all VLANs that are currently instantiated." 2598 REFERENCE 2599 "IEEE 802.1Q/D11 Section 12.7.2, 12.7.7" 2600 ::= { dot1qTp 5 } 2602 dot1qForwardUnregisteredEntry OBJECT-TYPE 2603 SYNTAX Dot1qForwardUnregisteredEntry 2604 MAX-ACCESS not-accessible 2605 STATUS current 2606 DESCRIPTION 2607 "Forwarding information for a VLAN, specifying the set 2608 of ports to which all multicasts for which there is no 2609 more specific forwarding information shall be forwarded. 2610 This is configured statically by management or 2611 dynamically by GMRP." 2612 INDEX { dot1qVlanIndex } 2613 ::= { dot1qForwardUnregisteredTable 1 } 2615 Dot1qForwardUnregisteredEntry ::= 2616 SEQUENCE { 2617 dot1qForwardUnregisteredPorts 2618 PortList, 2619 dot1qForwardUnregisteredStaticPorts 2620 PortList, 2621 dot1qForwardUnregisteredForbiddenPorts 2622 PortList 2623 } 2625 dot1qForwardUnregisteredPorts OBJECT-TYPE 2626 SYNTAX PortList 2627 MAX-ACCESS read-only 2628 STATUS current 2629 DESCRIPTION 2630 "The complete set of ports in this VLAN to which 2631 multicast group-addressed frames for which there is no 2632 more specific forwarding information will be forwarded. 2633 This includes ports for which this need has been 2634 determined dynamically by GMRP, or configured statically 2635 by management." 2636 ::= { dot1qForwardUnregisteredEntry 1 } 2638 dot1qForwardUnregisteredStaticPorts OBJECT-TYPE 2639 SYNTAX PortList 2640 MAX-ACCESS read-write 2641 STATUS current 2642 DESCRIPTION 2643 "The set of ports configured by management, in this 2644 VLAN, to which multicast group-addressed frames for 2645 which there is no more specific forwarding information 2646 are to be forwarded. Ports entered in this list will 2647 also appear in the complete set shown by 2648 dot1qForwardUnregisteredPorts. This value will be 2649 restored after the device is reset. A port may not be 2650 added in this set if it is already a member of the set 2651 of ports in dot1qForwardUnregisteredForbiddenPorts. The 2652 default value is a string of zeros of appropriate 2653 length, although this has no effect with the default 2654 value of dot1qForwardAllStaticPorts. 2656 The value of this object MUST be retained across 2657 reinitializations of the management system." 2658 ::= { dot1qForwardUnregisteredEntry 2 } 2660 dot1qForwardUnregisteredForbiddenPorts OBJECT-TYPE 2661 SYNTAX PortList 2662 MAX-ACCESS read-write 2663 STATUS current 2664 DESCRIPTION 2665 "The set of ports configured by management in this VLAN 2666 for which the Service Requirement attribute Forward 2667 Unregistered Multicast Groups may not be dynamically 2668 registered by GMRP. This value will be restored after 2669 the device is reset. A port may not be added in this 2670 set if it is already a member of the set of ports in 2671 dot1qForwardUnregisteredStaticPorts. The default value 2672 is a string of zeros of appropriate length. 2674 The value of this object MUST be retained across 2675 reinitializations of the management system." 2676 ::= { dot1qForwardUnregisteredEntry 3 } 2678 -- ------------------------------------------------------------- 2679 -- The Static (Destination-Address Filtering) Database 2680 -- ------------------------------------------------------------- 2682 dot1qStaticUnicastTable OBJECT-TYPE 2683 SYNTAX SEQUENCE OF Dot1qStaticUnicastEntry 2684 MAX-ACCESS not-accessible 2685 STATUS current 2686 DESCRIPTION 2687 "A table containing filtering information for Unicast 2688 MAC addresses for each Filtering Database, configured 2689 into the device by (local or network) management 2690 specifying the set of ports to which frames received 2691 from specific ports and containing specific unicast 2692 destination addresses are allowed to be forwarded. A 2693 value of zero in this table as the port number from 2694 which frames with a specific destination address are 2695 received, is used to specify all ports for which there 2696 is no specific entry in this table for that particular 2697 destination address. Entries are valid for unicast 2698 addresses only." 2699 REFERENCE 2700 "IEEE 802.1Q/D11 Section 12.7.7, 2701 ISO/IEC 15802-3 Section 7.9.1" 2702 ::= { dot1qStatic 1 } 2704 dot1qStaticUnicastEntry OBJECT-TYPE 2705 SYNTAX Dot1qStaticUnicastEntry 2706 MAX-ACCESS not-accessible 2707 STATUS current 2708 DESCRIPTION 2709 "Filtering information configured into the device by 2710 (local or network) management specifying the set of 2711 ports to which frames received from a specific port and 2712 containing a specific unicast destination address are 2713 allowed to be forwarded." 2714 INDEX { 2715 dot1qFdbId, 2716 dot1qStaticUnicastAddress, 2717 dot1qStaticUnicastReceivePort 2718 } 2719 ::= { dot1qStaticUnicastTable 1 } 2721 Dot1qStaticUnicastEntry ::= 2722 SEQUENCE { 2723 dot1qStaticUnicastAddress 2724 MacAddress, 2725 dot1qStaticUnicastReceivePort 2726 Integer32, 2727 dot1qStaticUnicastAllowedToGoTo 2728 PortList, 2729 dot1qStaticUnicastStatus 2730 INTEGER 2731 } 2733 dot1qStaticUnicastAddress OBJECT-TYPE 2734 SYNTAX MacAddress 2735 MAX-ACCESS not-accessible 2736 STATUS current 2737 DESCRIPTION 2738 "The destination MAC address in a frame to which this 2739 entry's filtering information applies. This object must 2740 take the value of a unicast address." 2741 ::= { dot1qStaticUnicastEntry 1 } 2743 dot1qStaticUnicastReceivePort OBJECT-TYPE 2744 SYNTAX Integer32 (0..65535) 2745 MAX-ACCESS not-accessible 2746 STATUS current 2747 DESCRIPTION 2748 "Either the value '0', or the port number of the port 2749 from which a frame must be received in order for this 2750 entry's filtering information to apply. A value of zero 2751 indicates that this entry applies on all ports of the 2752 device for which there is no other applicable entry." 2753 ::= { dot1qStaticUnicastEntry 2 } 2755 dot1qStaticUnicastAllowedToGoTo OBJECT-TYPE 2756 SYNTAX PortList 2757 MAX-ACCESS read-write 2758 STATUS current 2759 DESCRIPTION 2760 "The set of ports for which a frame with a specific 2761 unicast address will be flooded in the event that it 2762 has not been learned. It also specifies the set of 2763 ports a specific unicast address may be dynamically 2764 learnt on. The dot1qTpFdbTable will have an equivalent 2765 entry with a dot1qTpFdbPort value of '0' until this 2766 address has been learnt, when it will be updated with 2767 the port the address has been seen on. This only 2768 applies to ports that are members of the VLAN, defined 2769 by dot1qVlanCurrentEgressPorts. The default value of 2770 this object is a string of ones of appropriate length. 2772 The value of this object MUST be retained across 2773 reinitializations of the management system." 2774 REFERENCE 2775 "IEEE 802.1Q/D11 Table 8-5, ISO/IEC 15802-3 Table 7-5" 2776 ::= { dot1qStaticUnicastEntry 3 } 2778 dot1qStaticUnicastStatus OBJECT-TYPE 2779 SYNTAX INTEGER { 2780 other(1), 2781 invalid(2), 2782 permanent(3), 2783 deleteOnReset(4), 2784 deleteOnTimeout(5) 2785 } 2786 MAX-ACCESS read-write 2787 STATUS current 2788 DESCRIPTION 2789 "This object indicates the status of this entry. 2790 other(1) - this entry is currently in use but 2791 the conditions under which it will remain 2792 so differ from the following values. 2793 invalid(2) - writing this value to the object 2794 removes the corresponding entry. 2795 permanent(3) - this entry is currently in use 2796 and will remain so after the next reset of 2797 the bridge. 2798 deleteOnReset(4) - this entry is currently in 2799 use and will remain so until the next 2800 reset of the bridge. 2801 deleteOnTimeout(5) - this entry is currently in 2802 use and will remain so until it is aged out. 2804 The value of this object MUST be retained across 2805 reinitializations of the management system." 2806 DEFVAL { permanent } 2807 ::= { dot1qStaticUnicastEntry 4 } 2809 dot1qStaticMulticastTable OBJECT-TYPE 2810 SYNTAX SEQUENCE OF Dot1qStaticMulticastEntry 2811 MAX-ACCESS not-accessible 2812 STATUS current 2813 DESCRIPTION 2814 "A table containing filtering information for Multicast 2815 and Broadcast MAC addresses for each VLAN, configured 2816 into the device by (local or network) management 2817 specifying the set of ports to which frames received 2818 from specific ports and containing specific Multicast 2819 and Broadcast destination addresses are allowed to be 2820 forwarded. A value of zero in this table as the port 2821 number from which frames with a specific destination 2822 address are received, is used to specify all ports for 2823 which there is no specific entry in this table for that 2824 particular destination address. Entries are valid for 2825 Multicast and Broadcast addresses only." 2826 REFERENCE 2827 "IEEE 802.1Q/D11 Section 12.7.7, 2828 ISO/IEC 15802-3 Section 7.9.1" 2829 ::= { dot1qStatic 2 } 2831 dot1qStaticMulticastEntry OBJECT-TYPE 2832 SYNTAX Dot1qStaticMulticastEntry 2833 MAX-ACCESS not-accessible 2834 STATUS current 2835 DESCRIPTION 2836 "Filtering information configured into the device by 2837 (local or network) management specifying the set of 2838 ports to which frames received from this specific port 2839 for this VLAN and containing this Multicast or Broadcast 2840 destination address are allowed to be forwarded." 2841 INDEX { 2842 dot1qVlanIndex, 2843 dot1qStaticMulticastAddress, 2844 dot1qStaticMulticastReceivePort 2845 } 2846 ::= { dot1qStaticMulticastTable 1 } 2848 Dot1qStaticMulticastEntry ::= 2849 SEQUENCE { 2850 dot1qStaticMulticastAddress 2851 MacAddress, 2852 dot1qStaticMulticastReceivePort 2853 Integer32, 2854 dot1qStaticMulticastStaticEgressPorts 2855 PortList, 2856 dot1qStaticMulticastForbiddenEgressPorts 2857 PortList, 2858 dot1qStaticMulticastStatus 2859 INTEGER 2860 } 2862 dot1qStaticMulticastAddress OBJECT-TYPE 2863 SYNTAX MacAddress 2864 MAX-ACCESS not-accessible 2865 STATUS current 2866 DESCRIPTION 2867 "The destination MAC address in a frame to which this 2868 entry's filtering information applies. This object must 2869 take the value of a Multicast or Broadcast address." 2870 ::= { dot1qStaticMulticastEntry 1 } 2872 dot1qStaticMulticastReceivePort OBJECT-TYPE 2873 SYNTAX Integer32 (0..65535) 2874 MAX-ACCESS not-accessible 2875 STATUS current 2876 DESCRIPTION 2877 "Either the value '0', or the port number of the port 2878 from which a frame must be received in order for this 2879 entry's filtering information to apply. A value of zero 2880 indicates that this entry applies on all ports of the 2881 device for which there is no other applicable entry." 2882 ::= { dot1qStaticMulticastEntry 2 } 2884 dot1qStaticMulticastStaticEgressPorts OBJECT-TYPE 2885 SYNTAX PortList 2886 MAX-ACCESS read-write 2887 STATUS current 2888 DESCRIPTION 2889 "The set of ports to which frames received from a 2890 specific port and destined for a specific Multicast or 2891 Broadcast MAC address must be forwarded, regardless of 2892 any dynamic information e.g. from GMRP. A port may not 2893 be added in this set if it is already a member of the 2894 set of ports in dot1qStaticMulticastForbiddenEgressPorts. 2895 The default value of this object is a string of ones of 2896 appropriate length. 2898 The value of this object MUST be retained across 2899 reinitializations of the management system." 2900 ::= { dot1qStaticMulticastEntry 3 } 2902 dot1qStaticMulticastForbiddenEgressPorts OBJECT-TYPE 2903 SYNTAX PortList 2904 MAX-ACCESS read-write 2905 STATUS current 2906 DESCRIPTION 2907 "The set of ports to which frames received from a 2908 specific port and destined for a specific Multicast or 2909 Broadcast MAC address must not be forwarded, regardless 2910 of any dynamic information e.g. from GMRP. A port may 2911 not be added in this set if it is already a member of the 2912 set of ports in dot1qStaticMulticastStaticEgressPorts. 2913 The default value of this object is a string of zeros of 2914 appropriate length. 2916 The value of this object MUST be retained across 2917 reinitializations of the management system." 2918 ::= { dot1qStaticMulticastEntry 4 } 2920 dot1qStaticMulticastStatus OBJECT-TYPE 2921 SYNTAX INTEGER { 2922 other(1), 2923 invalid(2), 2924 permanent(3), 2925 deleteOnReset(4), 2926 deleteOnTimeout(5) 2928 } 2929 MAX-ACCESS read-write 2930 STATUS current 2931 DESCRIPTION 2932 "This object indicates the status of this entry. 2933 other(1) - this entry is currently in use but 2934 the conditions under which it will remain 2935 so differ from the following values. 2936 invalid(2) - writing this value to the object 2937 removes the corresponding entry. 2938 permanent(3) - this entry is currently in use 2939 and will remain so after the next reset of 2940 the bridge. 2941 deleteOnReset(4) - this entry is currently in 2942 use and will remain so until the next 2943 reset of the bridge. 2944 deleteOnTimeout(5) - this entry is currently in 2945 use and will remain so until it is aged out. 2947 The value of this object MUST be retained across 2948 reinitializations of the management system." 2949 DEFVAL { permanent } 2950 ::= { dot1qStaticMulticastEntry 5 } 2952 -- ------------------------------------------------------------- 2953 -- The Current VLAN Database 2954 -- ------------------------------------------------------------- 2956 dot1qVlanNumDeletes OBJECT-TYPE 2957 SYNTAX Counter32 2958 MAX-ACCESS read-only 2959 STATUS current 2960 DESCRIPTION 2961 "The number of times a VLAN entry has been deleted from 2962 the dot1qVlanCurrentTable (for any reason). If an entry 2963 is deleted, then inserted, and then deleted, this 2964 counter will be incremented by 2." 2965 ::= { dot1qVlan 1 } 2967 dot1qVlanCurrentTable OBJECT-TYPE 2968 SYNTAX SEQUENCE OF Dot1qVlanCurrentEntry 2969 MAX-ACCESS not-accessible 2970 STATUS current 2971 DESCRIPTION 2972 "A table containing current configuration information 2973 for each VLAN currently configured into the device by 2974 (local or network) management, or dynamically created 2975 as a result of GVRP requests received." 2976 ::= { dot1qVlan 2 } 2978 dot1qVlanCurrentEntry OBJECT-TYPE 2979 SYNTAX Dot1qVlanCurrentEntry 2980 MAX-ACCESS not-accessible 2981 STATUS current 2982 DESCRIPTION 2983 "Information for a VLAN configured into the device by 2984 (local or network) management, or dynamically created 2985 as a result of GVRP requests received." 2986 INDEX { dot1qVlanTimeMark, dot1qVlanIndex } 2987 ::= { dot1qVlanCurrentTable 1 } 2989 Dot1qVlanCurrentEntry ::= 2990 SEQUENCE { 2991 dot1qVlanTimeMark 2992 TimeFilter, 2993 dot1qVlanIndex 2994 VlanIndex, 2995 dot1qVlanFdbId 2996 Unsigned32, 2997 dot1qVlanCurrentEgressPorts 2998 PortList, 2999 dot1qVlanCurrentUntaggedPorts 3000 PortList, 3001 dot1qVlanStatus 3002 INTEGER, 3003 dot1qVlanCreationTime 3004 TimeTicks 3005 } 3007 dot1qVlanTimeMark OBJECT-TYPE 3008 SYNTAX TimeFilter 3009 MAX-ACCESS not-accessible 3010 STATUS current 3011 DESCRIPTION 3012 "A TimeFilter for this entry. See the TimeFilter 3013 textual convention to see how this works." 3014 ::= { dot1qVlanCurrentEntry 1 } 3016 dot1qVlanIndex OBJECT-TYPE 3017 SYNTAX VlanIndex 3018 MAX-ACCESS not-accessible 3019 STATUS current 3020 DESCRIPTION 3021 "The VLAN-ID or other identifier referring to this VLAN." 3022 ::= { dot1qVlanCurrentEntry 2 } 3024 dot1qVlanFdbId OBJECT-TYPE 3025 SYNTAX Unsigned32 3026 MAX-ACCESS read-only 3027 STATUS current 3028 DESCRIPTION 3029 "The Filtering Database used by this VLAN. This is one 3030 of the dot1qFdbId values in the dot1qFdbTable. This 3031 value is allocated automatically by the device whenever 3032 the VLAN is created: either dynamically by GVRP, or by 3033 management, in dot1qVlanStaticTable. Allocation of this 3034 value follows the learning constraints defined for this 3035 VLAN in dot1qLearningConstraintsTable." 3036 ::= { dot1qVlanCurrentEntry 3 } 3038 dot1qVlanCurrentEgressPorts OBJECT-TYPE 3039 SYNTAX PortList 3040 MAX-ACCESS read-only 3041 STATUS current 3042 DESCRIPTION 3043 "The set of ports which are transmitting traffic for 3044 this VLAN as either tagged or untagged frames." 3045 REFERENCE 3046 "IEEE 802.1Q/D11 Section 12.10.2.1" 3047 ::= { dot1qVlanCurrentEntry 4 } 3049 dot1qVlanCurrentUntaggedPorts OBJECT-TYPE 3050 SYNTAX PortList 3051 MAX-ACCESS read-only 3052 STATUS current 3053 DESCRIPTION 3054 "The set of ports which are transmitting traffic for 3055 this VLAN as untagged frames." 3056 REFERENCE 3057 "IEEE 802.1Q/D11 Section 12.10.2.1" 3058 ::= { dot1qVlanCurrentEntry 5 } 3060 dot1qVlanStatus OBJECT-TYPE 3061 SYNTAX INTEGER { 3062 other(1), 3063 permanent(2), 3064 dynamicGvrp(3) 3065 } 3067 MAX-ACCESS read-only 3068 STATUS current 3069 DESCRIPTION 3070 "This object indicates the status of this entry. 3071 other(1) - this entry is currently in use but the 3072 conditions under which it will remain so differ 3073 from the following values. 3074 permanent(2) - this entry, corresponding to an entry 3075 in dot1qVlanStaticTable, is currently in use and 3076 will remain so after the next reset of the 3077 device. The port lists for this entry include 3078 ports from the equivalent dot1qVlanStaticTable 3079 entry and ports learnt dynamically. 3080 dynamicGvrp(3) - this entry is currently in use 3081 and will remain so until removed by GVRP. There 3082 is no static entry for this VLAN and it will be 3083 removed when the last port leaves the VLAN." 3084 ::= { dot1qVlanCurrentEntry 6 } 3086 dot1qVlanCreationTime OBJECT-TYPE 3087 SYNTAX TimeTicks 3088 MAX-ACCESS read-only 3089 STATUS current 3090 DESCRIPTION 3091 "The value of sysUpTime when this VLAN was created." 3092 ::= { dot1qVlanCurrentEntry 7 } 3094 -- ------------------------------------------------------------- 3095 -- The Static VLAN Database 3096 -- ------------------------------------------------------------- 3098 dot1qVlanStaticTable OBJECT-TYPE 3099 SYNTAX SEQUENCE OF Dot1qVlanStaticEntry 3100 MAX-ACCESS not-accessible 3101 STATUS current 3102 DESCRIPTION 3103 "A table containing static configuration information for 3104 each VLAN configured into the device by (local or 3105 network) management. All entries are permanent and will 3106 be restored after the device is reset." 3107 ::= { dot1qVlan 3 } 3109 dot1qVlanStaticEntry OBJECT-TYPE 3110 SYNTAX Dot1qVlanStaticEntry 3111 MAX-ACCESS not-accessible 3112 STATUS current 3113 DESCRIPTION 3114 "Static information for a VLAN configured into the 3115 device by (local or network) management." 3116 INDEX { dot1qVlanIndex } 3117 ::= { dot1qVlanStaticTable 1 } 3119 Dot1qVlanStaticEntry ::= 3120 SEQUENCE { 3121 dot1qVlanStaticName 3122 SnmpAdminString, 3123 dot1qVlanStaticEgressPorts 3124 PortList, 3125 dot1qVlanForbiddenEgressPorts 3126 PortList, 3127 dot1qVlanStaticUntaggedPorts 3128 PortList, 3129 dot1qVlanStaticRowStatus 3130 RowStatus 3131 } 3133 dot1qVlanStaticName OBJECT-TYPE 3134 SYNTAX SnmpAdminString (SIZE (0..32)) 3135 MAX-ACCESS read-create 3136 STATUS current 3137 DESCRIPTION 3138 "An administratively assigned string, which may be used 3139 to identify the VLAN." 3140 REFERENCE 3141 "IEEE 802.1Q/D11 Section 12.10.2.1" 3142 ::= { dot1qVlanStaticEntry 1 } 3144 dot1qVlanStaticEgressPorts OBJECT-TYPE 3145 SYNTAX PortList 3146 MAX-ACCESS read-create 3147 STATUS current 3148 DESCRIPTION 3149 "The set of ports which are permanently assigned to the 3150 egress list for this VLAN by management. Changes to a 3151 bit in this object affect the per-port per-VLAN 3152 Registrar control for Registration Fixed for the 3153 relevant GVRP state machine on each port. A port may 3154 not be added in this set if it is already a member of 3155 the set of ports in dot1qVlanForbiddenEgressPorts. The 3156 default value of this object is a string of zeros of 3157 appropriate length, indicating not fixed." 3158 REFERENCE 3159 "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" 3160 ::= { dot1qVlanStaticEntry 2 } 3162 dot1qVlanForbiddenEgressPorts OBJECT-TYPE 3163 SYNTAX PortList 3164 MAX-ACCESS read-create 3165 STATUS current 3166 DESCRIPTION 3167 "The set of ports which are prohibited by management 3168 from being included in the egress list for this VLAN. 3169 Changes to this object that cause a port to be included 3170 or excluded affect the per-port per-VLAN Registrar 3171 control for Registration Forbidden for the relevant GVRP 3172 state machine on each port. A port may not be added in 3173 this set if it is already a member of the set of ports 3174 in dot1qVlanStaticEgressPorts. The default value of 3175 this object is a string of zeros of appropriate length, 3176 excluding all ports from the forbidden set." 3177 REFERENCE 3178 "IEEE 802.1Q/D11 Section 12.7.7.3, 11.2.3.2.3" 3179 ::= { dot1qVlanStaticEntry 3 } 3181 dot1qVlanStaticUntaggedPorts OBJECT-TYPE 3182 SYNTAX PortList 3183 MAX-ACCESS read-create 3184 STATUS current 3185 DESCRIPTION 3186 "The set of ports which should transmit egress packets 3187 for this VLAN as untagged. The default value of this 3188 object for the default VLAN (dot1qVlanIndex = 1) is a string 3189 of appropriate length including all ports. There is no 3190 specified default for other VLANs. If a device agent cannot 3191 support the set of ports being set then it will reject the 3192 set operation with an error. An example might be if a 3193 manager attempts to set more than one VLAN to be untagged 3194 on egress where the device does not support this IEEE 802.1Q 3195 option." 3196 REFERENCE 3197 "IEEE 802.1Q/D11 Section 12.10.2.1" 3198 ::= { dot1qVlanStaticEntry 4 } 3200 dot1qVlanStaticRowStatus OBJECT-TYPE 3201 SYNTAX RowStatus 3202 MAX-ACCESS read-create 3203 STATUS current 3204 DESCRIPTION 3205 "This object indicates the status of this entry." 3206 ::= { dot1qVlanStaticEntry 5 } 3208 dot1qNextFreeLocalVlanIndex OBJECT-TYPE 3209 SYNTAX Integer32 (0|4096..2147483647) 3210 MAX-ACCESS read-only 3211 STATUS current 3212 DESCRIPTION 3213 "The next available value for dot1qVlanIndex of a local 3214 VLAN entry in dot1qVlanStaticTable. This will report 3215 values >=4096 if a new Local VLAN may be created or else 3216 the value 0 if this is not possible. 3217 A row creation operation in this table for an entry with a local 3218 VlanIndex value may fail if the current value of this object 3219 is not used as the index. Even if the value read is used, 3220 there is no guarantee that it will still be the valid index 3221 when the create operation is attempted - another manager may 3222 have already got in during the intervening time interval. 3223 In this case, dot1qNextFreeLocalVlanIndex should be re-read 3224 and the creation re-tried with the new value. 3226 This value will automatically change when the current value is 3227 used to create a new row." 3228 ::= { dot1qVlan 4 } 3230 -- ------------------------------------------------------------- 3231 -- The VLAN Port Configuration Table 3232 -- ------------------------------------------------------------- 3234 dot1qPortVlanTable OBJECT-TYPE 3235 SYNTAX SEQUENCE OF Dot1qPortVlanEntry 3236 MAX-ACCESS not-accessible 3237 STATUS current 3238 DESCRIPTION 3239 "A table containing per port control and status 3240 information for VLAN configuration in the device." 3241 ::= { dot1qVlan 5 } 3243 dot1qPortVlanEntry OBJECT-TYPE 3244 SYNTAX Dot1qPortVlanEntry 3245 MAX-ACCESS not-accessible 3246 STATUS current 3247 DESCRIPTION 3248 "Information controlling VLAN configuration for a port 3249 on the device. This is indexed by dot1dBasePort." 3250 AUGMENTS { dot1dBasePortEntry } 3251 ::= { dot1qPortVlanTable 1 } 3253 Dot1qPortVlanEntry ::= 3254 SEQUENCE { 3255 dot1qPvid 3256 VlanIndex, 3257 dot1qPortAcceptableFrameTypes 3258 INTEGER, 3259 dot1qPortIngressFiltering 3260 TruthValue, 3261 dot1qPortGvrpStatus 3262 EnabledStatus, 3263 dot1qPortGvrpFailedRegistrations 3264 Counter32, 3265 dot1qPortGvrpLastPduOrigin 3266 MacAddress, 3267 dot1qPortRestrictedVlanRegistration 3268 TruthValue 3269 } 3271 dot1qPvid OBJECT-TYPE 3272 SYNTAX VlanIndex 3273 MAX-ACCESS read-write 3274 STATUS current 3275 DESCRIPTION 3276 "The PVID, the VLAN ID assigned to untagged frames or 3277 Priority-Tagged frames received on this port. 3279 The value of this object MUST be retained across 3280 reinitializations of the management system." 3281 REFERENCE 3282 "IEEE 802.1Q/D11 Section 12.10.1.1" 3283 DEFVAL { 1 } 3284 ::= { dot1qPortVlanEntry 1 } 3286 dot1qPortAcceptableFrameTypes OBJECT-TYPE 3287 SYNTAX INTEGER { 3288 admitAll(1), 3289 admitOnlyVlanTagged(2) 3290 } 3291 MAX-ACCESS read-write 3292 STATUS current 3293 DESCRIPTION 3294 "When this is admitOnlyVlanTagged(2) the device will 3295 discard untagged frames or Priority-Tagged frames 3296 received on this port. When admitAll(1), untagged 3297 frames or Priority-Tagged frames received on this port 3298 will be accepted and assigned to a VID based on the 3299 PVID and VID Set for this port. 3301 This control does not affect VLAN independent BPDU 3302 frames, such as GVRP and STP. It does affect VLAN 3303 dependent BPDU frames, such as GMRP. 3305 The value of this object MUST be retained across 3306 reinitializations of the management system." 3307 REFERENCE 3308 "IEEE 802.1Q/D11 Section 12.10.1.3" 3309 DEFVAL { admitAll } 3310 ::= { dot1qPortVlanEntry 2 } 3312 dot1qPortIngressFiltering OBJECT-TYPE 3313 SYNTAX TruthValue 3314 MAX-ACCESS read-write 3315 STATUS current 3316 DESCRIPTION 3317 "When this is true(1) the device will discard incoming 3318 frames for VLANs which do not include this Port in its 3319 Member set. When false(2), the port will accept all 3320 incoming frames. 3322 This control does not affect VLAN independent BPDU 3323 frames, such as GVRP and STP. It does affect VLAN 3324 dependent BPDU frames, such as GMRP. 3326 The value of this object MUST be retained across 3327 reinitializations of the management system." 3328 REFERENCE 3329 "IEEE 802.1Q/D11 Section 12.10.1.4" 3330 DEFVAL { false } 3331 ::= { dot1qPortVlanEntry 3 } 3333 dot1qPortGvrpStatus OBJECT-TYPE 3334 SYNTAX EnabledStatus 3335 MAX-ACCESS read-write 3336 STATUS current 3337 DESCRIPTION 3338 "The state of GVRP operation on this port. The value 3339 enabled(1) indicates that GVRP is enabled on this port, 3340 as long as dot1qGvrpStatus is also enabled for this 3341 device. When disabled(2) but dot1qGvrpStatus is still 3342 enabled for the device, GVRP is disabled on this port: 3344 any GVRP packets received will be silently discarded and 3345 no GVRP registrations will be propagated from other 3346 ports. This object affects all GVRP Applicant and 3347 Registrar state machines on this port. A transition 3348 from disabled(2) to enabled(1) will cause a reset of all 3349 GVRP state machines on this port. 3351 The value of this object MUST be retained across 3352 reinitializations of the management system." 3353 DEFVAL { enabled } 3354 ::= { dot1qPortVlanEntry 4 } 3356 dot1qPortGvrpFailedRegistrations OBJECT-TYPE 3357 SYNTAX Counter32 3358 MAX-ACCESS read-only 3359 STATUS current 3360 DESCRIPTION 3361 "The total number of failed GVRP registrations, for any 3362 reason, on this port." 3363 ::= { dot1qPortVlanEntry 5 } 3365 dot1qPortGvrpLastPduOrigin OBJECT-TYPE 3366 SYNTAX MacAddress 3367 MAX-ACCESS read-only 3368 STATUS current 3369 DESCRIPTION 3370 "The Source MAC Address of the last GVRP message 3371 received on this port." 3372 ::= { dot1qPortVlanEntry 6 } 3374 dot1qPortRestrictedVlanRegistration OBJECT-TYPE 3375 SYNTAX TruthValue 3376 MAX-ACCESS read-write 3377 STATUS current 3378 DESCRIPTION 3379 "The state of Restricted VLAN Registration on this port. 3380 If the value of this control is true(1), then creation 3381 of a new dynamic VLAN entry is permitted only if there 3382 is a Static VLAN Registration Entry for the VLAN concerned, 3383 in which the Registrar Administrative Control value for 3384 this port is Normal Registration. 3386 The value of this object MUST be retained across 3387 reinitializations of the management system." 3388 REFERENCE 3389 "IEEE 802.1u clause 11.2.3.2.3, 12.10.1.7." 3391 DEFVAL { false } 3392 ::= { dot1qPortVlanEntry 7 } 3394 -- ------------------------------------------------------------- 3395 -- Per port VLAN Statistics Table 3396 -- ------------------------------------------------------------- 3398 dot1qPortVlanStatisticsTable OBJECT-TYPE 3399 SYNTAX SEQUENCE OF Dot1qPortVlanStatisticsEntry 3400 MAX-ACCESS not-accessible 3401 STATUS current 3402 DESCRIPTION 3403 "A table containing per-port, per-VLAN statistics for 3404 traffic received. Separate objects are provided for both the 3405 most-significant and least-significant bits of statistics 3406 counters for ports that are associated with this transparent 3407 bridge. The most-significant bit objects are only required on 3408 high capacity interfaces, as defined in the conformance clauses 3409 for these objects. This mechanism is provided as a way to read 3410 64-bit counters for agents which support only SNMPv1. 3412 Note that the reporting of most-significant and least- 3413 significant counter bits separately runs the risk of missing 3414 an overflow of the lower bits in the interval between sampling. 3415 The manager must be aware of this possibility, even within the 3416 same varbindlist, when interpreting the results of a request or 3417 asynchronous notification." 3418 ::= { dot1qVlan 6 } 3420 dot1qPortVlanStatisticsEntry OBJECT-TYPE 3421 SYNTAX Dot1qPortVlanStatisticsEntry 3422 MAX-ACCESS not-accessible 3423 STATUS current 3424 DESCRIPTION 3425 "Traffic statistics for a VLAN on an interface." 3426 INDEX { dot1dBasePort, dot1qVlanIndex } 3427 ::= { dot1qPortVlanStatisticsTable 1 } 3429 Dot1qPortVlanStatisticsEntry ::= 3430 SEQUENCE { 3431 dot1qTpVlanPortInFrames 3432 Counter32, 3433 dot1qTpVlanPortOutFrames 3434 Counter32, 3435 dot1qTpVlanPortInDiscards 3436 Counter32, 3438 dot1qTpVlanPortInOverflowFrames 3439 Counter32, 3440 dot1qTpVlanPortOutOverflowFrames 3441 Counter32, 3442 dot1qTpVlanPortInOverflowDiscards 3443 Counter32 3444 } 3446 dot1qTpVlanPortInFrames OBJECT-TYPE 3447 SYNTAX Counter32 3448 MAX-ACCESS read-only 3449 STATUS current 3450 DESCRIPTION 3451 "The number of valid frames received by this port from 3452 its segment which were classified as belonging to this 3453 VLAN. Note that a frame received on this port is 3454 counted by this object if and only if it is for a 3455 protocol being processed by the local forwarding process 3456 for this VLAN. This object includes received bridge 3457 management frames classified as belonging to this VLAN 3458 (e.g. GMRP, but not GVRP or STP)." 3459 REFERENCE 3460 "IEEE 802.1Q/D11 Section 12.6.1.1.3(a)" 3461 ::= { dot1qPortVlanStatisticsEntry 1 } 3463 dot1qTpVlanPortOutFrames OBJECT-TYPE 3464 SYNTAX Counter32 3465 MAX-ACCESS read-only 3466 STATUS current 3467 DESCRIPTION 3468 "The number of valid frames transmitted by this port to 3469 its segment from the local forwarding process for this 3470 VLAN. This includes bridge management frames originated 3471 by this device which are classified as belonging to this 3472 VLAN (e.g. GMRP, but not GVRP or STP)." 3473 REFERENCE 3474 "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" 3475 ::= { dot1qPortVlanStatisticsEntry 2 } 3477 dot1qTpVlanPortInDiscards OBJECT-TYPE 3478 SYNTAX Counter32 3479 MAX-ACCESS read-only 3480 STATUS current 3481 DESCRIPTION 3482 "The number of valid frames received by this port from 3483 its segment which were classified as belonging to this 3484 VLAN which were discarded due to VLAN related reasons. 3485 Specifically, the IEEE 802.1Q counters for Discard 3486 Inbound and Discard on Ingress Filtering." 3487 REFERENCE 3488 "IEEE 802.1Q/D11 Section 12.6.1.1.3" 3489 ::= { dot1qPortVlanStatisticsEntry 3 } 3491 dot1qTpVlanPortInOverflowFrames OBJECT-TYPE 3492 SYNTAX Counter32 3493 MAX-ACCESS read-only 3494 STATUS current 3495 DESCRIPTION 3496 "The number of times the associated 3497 dot1qTpVlanPortInFrames counter has overflowed." 3498 REFERENCE 3499 "ISO/IEC 15802-3 Section 14.6.1.1.3" 3500 ::= { dot1qPortVlanStatisticsEntry 4 } 3502 dot1qTpVlanPortOutOverflowFrames OBJECT-TYPE 3503 SYNTAX Counter32 3504 MAX-ACCESS read-only 3505 STATUS current 3506 DESCRIPTION 3507 "The number of times the associated 3508 dot1qTpVlanPortOutFrames counter has overflowed." 3509 REFERENCE 3510 "ISO/IEC 15802-3 Section 14.6.1.1.3" 3511 ::= { dot1qPortVlanStatisticsEntry 5 } 3513 dot1qTpVlanPortInOverflowDiscards OBJECT-TYPE 3514 SYNTAX Counter32 3515 MAX-ACCESS read-only 3516 STATUS current 3517 DESCRIPTION 3518 "The number of times the associated 3519 dot1qTpVlanPortInDiscards counter has overflowed." 3520 REFERENCE 3521 "ISO/IEC 15802-3 Section 14.6.1.1.3" 3522 ::= { dot1qPortVlanStatisticsEntry 6 } 3524 dot1qPortVlanHCStatisticsTable OBJECT-TYPE 3525 SYNTAX SEQUENCE OF Dot1qPortVlanHCStatisticsEntry 3526 MAX-ACCESS not-accessible 3527 STATUS current 3528 DESCRIPTION 3529 "A table containing per port, per VLAN statistics for 3530 traffic on high capacity interfaces." 3531 ::= { dot1qVlan 7 } 3533 dot1qPortVlanHCStatisticsEntry OBJECT-TYPE 3534 SYNTAX Dot1qPortVlanHCStatisticsEntry 3535 MAX-ACCESS not-accessible 3536 STATUS current 3537 DESCRIPTION 3538 "Traffic statistics for a VLAN on a high capacity 3539 interface." 3540 INDEX { dot1dBasePort, dot1qVlanIndex } 3541 ::= { dot1qPortVlanHCStatisticsTable 1 } 3543 Dot1qPortVlanHCStatisticsEntry ::= 3544 SEQUENCE { 3545 dot1qTpVlanPortHCInFrames 3546 Counter64, 3547 dot1qTpVlanPortHCOutFrames 3548 Counter64, 3549 dot1qTpVlanPortHCInDiscards 3550 Counter64 3551 } 3553 dot1qTpVlanPortHCInFrames OBJECT-TYPE 3554 SYNTAX Counter64 3555 MAX-ACCESS read-only 3556 STATUS current 3557 DESCRIPTION 3558 "The number of valid frames received by this port from 3559 its segment which were classified as belonging to this 3560 VLAN. Note that a frame received on this port is 3561 counted by this object if and only if it is for a 3562 protocol being processed by the local forwarding process 3563 for this VLAN. This object includes received bridge 3564 management frames classified as belonging to this VLAN 3565 (e.g. GMRP, but not GVRP or STP)." 3566 REFERENCE 3567 "IEEE 802.1Q/D11 Section 12.6.1.1.3(a)" 3568 ::= { dot1qPortVlanHCStatisticsEntry 1 } 3570 dot1qTpVlanPortHCOutFrames OBJECT-TYPE 3571 SYNTAX Counter64 3572 MAX-ACCESS read-only 3573 STATUS current 3574 DESCRIPTION 3575 "The number of valid frames transmitted by this port to 3576 its segment from the local forwarding process for this 3577 VLAN. This includes bridge management frames originated 3578 by this device which are classified as belonging to this 3579 VLAN (e.g. GMRP, but not GVRP or STP)." 3580 REFERENCE 3581 "IEEE 802.1Q/D11 Section 12.6.1.1.3(d)" 3582 ::= { dot1qPortVlanHCStatisticsEntry 2 } 3584 dot1qTpVlanPortHCInDiscards OBJECT-TYPE 3585 SYNTAX Counter64 3586 MAX-ACCESS read-only 3587 STATUS current 3588 DESCRIPTION 3589 "The number of valid frames received by this port from 3590 its segment which were classified as belonging to this 3591 VLAN which were discarded due to VLAN related reasons. 3592 Specifically, the IEEE 802.1Q counters for Discard 3593 Inbound and Discard on Ingress Filtering." 3594 REFERENCE 3595 "IEEE 802.1Q/D11 Section 12.6.1.1.3" 3596 ::= { dot1qPortVlanHCStatisticsEntry 3 } 3598 -- ------------------------------------------------------------- 3599 -- The VLAN Learning Constraints Table 3600 -- ------------------------------------------------------------- 3602 dot1qLearningConstraintsTable OBJECT-TYPE 3603 SYNTAX SEQUENCE OF Dot1qLearningConstraintsEntry 3604 MAX-ACCESS not-accessible 3605 STATUS current 3606 DESCRIPTION 3607 "A table containing learning constraints for sets of 3608 Shared and Independent VLANs." 3609 REFERENCE 3610 "IEEE 802.1Q/D11 Section 12.10.3.1" 3611 ::= { dot1qVlan 8 } 3613 dot1qLearningConstraintsEntry OBJECT-TYPE 3614 SYNTAX Dot1qLearningConstraintsEntry 3615 MAX-ACCESS not-accessible 3616 STATUS current 3617 DESCRIPTION 3618 "A learning constraint defined for a VLAN." 3619 INDEX { dot1qConstraintVlan, dot1qConstraintSet } 3620 ::= { dot1qLearningConstraintsTable 1 } 3622 Dot1qLearningConstraintsEntry ::= 3623 SEQUENCE { 3624 dot1qConstraintVlan 3625 VlanIndex, 3626 dot1qConstraintSet 3627 Integer32, 3628 dot1qConstraintType 3629 INTEGER, 3630 dot1qConstraintStatus 3631 RowStatus 3632 } 3634 dot1qConstraintVlan OBJECT-TYPE 3635 SYNTAX VlanIndex 3636 MAX-ACCESS not-accessible 3637 STATUS current 3638 DESCRIPTION 3639 "The index of the row in dot1qVlanCurrentTable for the 3640 VLAN constrained by this entry." 3641 ::= { dot1qLearningConstraintsEntry 1 } 3643 dot1qConstraintSet OBJECT-TYPE 3644 SYNTAX Integer32 (0..65535) 3645 MAX-ACCESS not-accessible 3646 STATUS current 3647 DESCRIPTION 3648 "The identity of the constraint set to which 3649 dot1qConstraintVlan belongs. These values may be chosen 3650 by the management station." 3651 ::= { dot1qLearningConstraintsEntry 2 } 3653 dot1qConstraintType OBJECT-TYPE 3654 SYNTAX INTEGER { 3655 independent(1), 3656 shared(2) 3657 } 3658 MAX-ACCESS read-create 3659 STATUS current 3660 DESCRIPTION 3661 "The type of constraint this entry defines. 3662 independent(1) - the VLAN, dot1qConstraintVlan, 3663 uses an independent filtering database from all 3664 other VLANs in the same set, defined by 3665 dot1qConstraintSet. 3666 shared(2) - the VLAN, dot1qConstraintVlan, shares 3667 the same filtering database as all other VLANs 3668 in the same set, defined by dot1qConstraintSet." 3669 ::= { dot1qLearningConstraintsEntry 3 } 3671 dot1qConstraintStatus OBJECT-TYPE 3672 SYNTAX RowStatus 3673 MAX-ACCESS read-create 3674 STATUS current 3675 DESCRIPTION 3676 "The status of this entry." 3677 ::= { dot1qLearningConstraintsEntry 4 } 3679 dot1qConstraintSetDefault OBJECT-TYPE 3680 SYNTAX Integer32 (0..65535) 3681 MAX-ACCESS read-write 3682 STATUS current 3683 DESCRIPTION 3684 "The identity of the constraint set to which a VLAN 3685 belongs, if there is not an explicit entry for that VLAN 3686 in dot1qLearningConstraintsTable. 3688 The value of this object MUST be retained across 3689 reinitializations of the management system." 3690 ::= { dot1qVlan 9 } 3692 dot1qConstraintTypeDefault OBJECT-TYPE 3693 SYNTAX INTEGER { 3694 independent(1), 3695 shared(2) 3696 } 3697 MAX-ACCESS read-write 3698 STATUS current 3699 DESCRIPTION 3700 "The type of constraint set to which a VLAN belongs, if 3701 there is not an explicit entry for that VLAN in 3702 dot1qLearningConstraintsTable. The types are as defined 3703 for dot1qConstraintType. 3705 The value of this object MUST be retained across 3706 reinitializations of the management system." 3707 ::= { dot1qVlan 10 } 3709 -- ------------------------------------------------------------- 3710 -- dot1vProtocol subtree 3711 -- ------------------------------------------------------------- 3713 dot1vProtocolGroupTable OBJECT-TYPE 3714 SYNTAX SEQUENCE OF Dot1vProtocolGroupEntry 3715 MAX-ACCESS not-accessible 3716 STATUS current 3717 DESCRIPTION 3718 "A table that contains mappings from Protocol 3719 Templates to Protocol Group Identifiers used for 3720 Port-and-Protocol-based VLAN Classification." 3721 REFERENCE 3722 "IEEE 802.1v clause 8.6.4" 3723 ::= { dot1vProtocol 1 } 3725 dot1vProtocolGroupEntry OBJECT-TYPE 3726 SYNTAX Dot1vProtocolGroupEntry 3727 MAX-ACCESS not-accessible 3728 STATUS current 3729 DESCRIPTION 3730 "A mapping from a Protocol Template to a Protocol 3731 Group Identifier." 3732 INDEX { dot1vProtocolTemplateFrameType, 3733 dot1vProtocolTemplateProtocolValue } 3734 ::= { dot1vProtocolGroupTable 1 } 3736 Dot1vProtocolGroupEntry ::= 3737 SEQUENCE { 3738 dot1vProtocolTemplateFrameType 3739 INTEGER, 3740 dot1vProtocolTemplateProtocolValue 3741 OCTET STRING, 3742 dot1vProtocolGroupId 3743 Integer32, 3744 dot1vProtocolGroupRowStatus 3745 RowStatus 3746 } 3748 dot1vProtocolTemplateFrameType OBJECT-TYPE 3749 SYNTAX INTEGER { 3750 ethernet (1), 3751 rfc1042 (2), 3752 snap8021H (3), 3753 snapOther (4), 3754 llcOther (5) 3755 } 3756 MAX-ACCESS not-accessible 3757 STATUS current 3758 DESCRIPTION 3759 "The data-link encapsulation format or the 3760 'detagged_frame_type' in a Protocol Template." 3761 REFERENCE 3762 "IEEE 802.1v clause 8.6.2" 3763 ::= { dot1vProtocolGroupEntry 1 } 3765 dot1vProtocolTemplateProtocolValue OBJECT-TYPE 3766 SYNTAX OCTET STRING (SIZE (2 | 5)) 3767 MAX-ACCESS not-accessible 3768 STATUS current 3769 DESCRIPTION 3770 "The identification of the protocol above the data-link 3771 layer in a Protocol Template. Depending on the 3772 frame type, the octet string will have one of the 3773 following values: 3775 For 'ethernet', 'rfc1042' and 'snap8021H', 3776 this is the 16-bit (2-octet) IEEE 802.3 Type Field. 3777 For 'snapOther', 3778 this is the 40-bit (5-octet) PID. 3779 For 'llcOther', 3780 this is the 2-octet IEEE 802.2 LSAP pair: 3781 first octet for DSAP and second octet for SSAP." 3782 REFERENCE 3783 "IEEE 802.1v clause 8.6.2" 3784 ::= { dot1vProtocolGroupEntry 2 } 3786 dot1vProtocolGroupId OBJECT-TYPE 3787 SYNTAX Integer32 (0..2147483647) 3788 MAX-ACCESS read-create 3789 STATUS current 3790 DESCRIPTION 3791 "Represents a group of protocols that are associated 3792 together when assigning a VID to a frame." 3793 REFERENCE 3794 "IEEE 802.1v clause 8.6.3, 12.10.2.1" 3795 ::= { dot1vProtocolGroupEntry 3 } 3797 dot1vProtocolGroupRowStatus OBJECT-TYPE 3798 SYNTAX RowStatus 3799 MAX-ACCESS read-create 3800 STATUS current 3801 DESCRIPTION 3802 "This object indicates the status of this entry." 3803 ::= { dot1vProtocolGroupEntry 4 } 3805 dot1vProtocolPortTable OBJECT-TYPE 3806 SYNTAX SEQUENCE OF Dot1vProtocolPortEntry 3807 MAX-ACCESS not-accessible 3808 STATUS current 3809 DESCRIPTION 3810 "A table that contains VID sets used for 3811 Port-and-Protocol-based VLAN Classification." 3812 REFERENCE 3813 "IEEE 802.1v clause 8.4.4" 3814 ::= { dot1vProtocol 2 } 3816 dot1vProtocolPortEntry OBJECT-TYPE 3817 SYNTAX Dot1vProtocolPortEntry 3818 MAX-ACCESS not-accessible 3819 STATUS current 3820 DESCRIPTION 3821 "A VID set for a port." 3822 INDEX { dot1dBasePort, 3823 dot1vProtocolPortGroupId } 3824 ::= { dot1vProtocolPortTable 1 } 3826 Dot1vProtocolPortEntry ::= 3827 SEQUENCE { 3828 dot1vProtocolPortGroupId 3829 Integer32, 3830 dot1vProtocolPortGroupVid 3831 Integer32, 3832 dot1vProtocolPortRowStatus 3833 RowStatus 3834 } 3836 dot1vProtocolPortGroupId OBJECT-TYPE 3837 SYNTAX Integer32 (1..2147483647) 3838 MAX-ACCESS not-accessible 3839 STATUS current 3840 DESCRIPTION 3841 "Designates a group of protocols in the Protocol 3842 Group Database." 3843 REFERENCE 3844 "IEEE 802.1v clause 8.6.3, 12.10.1.2" 3845 ::= { dot1vProtocolPortEntry 1 } 3847 dot1vProtocolPortGroupVid OBJECT-TYPE 3848 SYNTAX Integer32 (1..4094) 3849 MAX-ACCESS read-create 3850 STATUS current 3851 DESCRIPTION 3852 "The VID associated with a group of protocols for 3853 each port." 3854 REFERENCE 3855 "IEEE 802.1v clause 8.4.4, 12.10.1.2" 3856 ::= { dot1vProtocolPortEntry 2 } 3858 dot1vProtocolPortRowStatus OBJECT-TYPE 3859 SYNTAX RowStatus 3860 MAX-ACCESS read-create 3861 STATUS current 3862 DESCRIPTION 3863 "This object indicates the status of this entry." 3864 ::= { dot1vProtocolPortEntry 3 } 3866 -- ------------------------------------------------------------- 3867 -- IEEE 802.1Q MIB - Conformance Information 3868 -- ------------------------------------------------------------- 3870 qBridgeConformance OBJECT IDENTIFIER ::= { qBridgeMIB 2 } 3872 qBridgeGroups OBJECT IDENTIFIER ::= { qBridgeConformance 1 } 3874 qBridgeCompliances OBJECT IDENTIFIER ::= { qBridgeConformance 2 } 3876 -- ------------------------------------------------------------- 3877 -- units of conformance 3878 -- ------------------------------------------------------------- 3880 qBridgeBaseGroup OBJECT-GROUP 3881 OBJECTS { 3882 dot1qVlanVersionNumber, 3883 dot1qMaxVlanId, 3884 dot1qMaxSupportedVlans, 3885 dot1qNumVlans, 3886 dot1qGvrpStatus 3887 } 3888 STATUS current 3889 DESCRIPTION 3890 "A collection of objects providing device level control 3891 and status information for the Virtual LAN bridge 3892 services." 3893 ::= { qBridgeGroups 1 } 3895 qBridgeFdbUnicastGroup OBJECT-GROUP 3896 OBJECTS { 3897 dot1qFdbDynamicCount, 3898 dot1qTpFdbPort, 3899 dot1qTpFdbStatus 3900 } 3901 STATUS current 3902 DESCRIPTION 3903 "A collection of objects providing information about all 3904 unicast addresses, learnt dynamically or statically 3905 configured by management, in each Filtering Database." 3906 ::= { qBridgeGroups 2 } 3908 qBridgeFdbMulticastGroup OBJECT-GROUP 3909 OBJECTS { 3910 dot1qTpGroupEgressPorts, 3911 dot1qTpGroupLearnt 3912 } 3913 STATUS current 3914 DESCRIPTION 3915 "A collection of objects providing information about all 3916 multicast addresses, learnt dynamically or statically 3917 configured by management, in each Filtering Database." 3918 ::= { qBridgeGroups 3 } 3920 qBridgeServiceRequirementsGroup OBJECT-GROUP 3921 OBJECTS { 3922 dot1qForwardAllPorts, 3923 dot1qForwardAllStaticPorts, 3924 dot1qForwardAllForbiddenPorts, 3925 dot1qForwardUnregisteredPorts, 3926 dot1qForwardUnregisteredStaticPorts, 3927 dot1qForwardUnregisteredForbiddenPorts 3928 } 3929 STATUS current 3930 DESCRIPTION 3931 "A collection of objects providing information about 3932 service requirements, learnt dynamically or statically 3933 configured by management, in each Filtering Database." 3934 ::= { qBridgeGroups 4 } 3936 qBridgeFdbStaticGroup OBJECT-GROUP 3937 OBJECTS { 3938 dot1qStaticUnicastAllowedToGoTo, 3939 dot1qStaticUnicastStatus, 3940 dot1qStaticMulticastStaticEgressPorts, 3941 dot1qStaticMulticastForbiddenEgressPorts, 3942 dot1qStaticMulticastStatus 3943 } 3944 STATUS current 3945 DESCRIPTION 3946 "A collection of objects providing information about 3947 unicast and multicast addresses statically configured by 3948 management, in each Filtering Database or VLAN." 3949 ::= { qBridgeGroups 5 } 3951 qBridgeVlanGroup OBJECT-GROUP 3952 OBJECTS { 3953 dot1qVlanNumDeletes, 3954 dot1qVlanFdbId, 3955 dot1qVlanCurrentEgressPorts, 3956 dot1qVlanCurrentUntaggedPorts, 3957 dot1qVlanStatus, 3958 dot1qVlanCreationTime 3959 } 3960 STATUS current 3961 DESCRIPTION 3962 "A collection of objects providing information about 3963 all VLANs currently configured on this device." 3964 ::= { qBridgeGroups 6 } 3966 qBridgeVlanStaticGroup OBJECT-GROUP 3967 OBJECTS { 3968 dot1qVlanStaticName, 3969 dot1qVlanStaticEgressPorts, 3970 dot1qVlanForbiddenEgressPorts, 3971 dot1qVlanStaticUntaggedPorts, 3972 dot1qVlanStaticRowStatus, 3973 dot1qNextFreeLocalVlanIndex 3974 } 3975 STATUS current 3976 DESCRIPTION 3977 "A collection of objects providing information about 3978 VLANs statically configured by management." 3979 ::= { qBridgeGroups 7 } 3981 qBridgePortGroup OBJECT-GROUP 3982 OBJECTS { 3983 dot1qPvid, 3984 dot1qPortAcceptableFrameTypes, 3985 dot1qPortIngressFiltering, 3986 dot1qPortGvrpStatus, 3987 dot1qPortGvrpFailedRegistrations, 3988 dot1qPortGvrpLastPduOrigin 3989 } 3990 STATUS deprecated 3991 DESCRIPTION 3992 "A collection of objects providing port level VLAN 3993 control and status information for all ports." 3994 ::= { qBridgeGroups 8 } 3996 qBridgeVlanStatisticsGroup OBJECT-GROUP 3997 OBJECTS { 3998 dot1qTpVlanPortInFrames, 3999 dot1qTpVlanPortOutFrames, 4000 dot1qTpVlanPortInDiscards 4001 } 4002 STATUS current 4003 DESCRIPTION 4004 "A collection of objects providing per-port packet 4005 statistics for all VLANs currently configured on this 4006 device." 4007 ::= { qBridgeGroups 9 } 4009 qBridgeVlanStatisticsOverflowGroup OBJECT-GROUP 4010 OBJECTS { 4011 dot1qTpVlanPortInOverflowFrames, 4012 dot1qTpVlanPortOutOverflowFrames, 4013 dot1qTpVlanPortInOverflowDiscards 4014 } 4015 STATUS current 4016 DESCRIPTION 4017 "A collection of objects providing overflow counters for 4018 per-port packet statistics for all VLANs currently configured 4019 on this device for high capacity interfaces, defined as those 4020 that have the value of the corresponding instance of 4021 ifSpeed greater than 650,000,000 bits/second." 4022 ::= { qBridgeGroups 10 } 4024 qBridgeVlanHCStatisticsGroup OBJECT-GROUP 4025 OBJECTS { 4026 dot1qTpVlanPortHCInFrames, 4027 dot1qTpVlanPortHCOutFrames, 4028 dot1qTpVlanPortHCInDiscards 4029 } 4030 STATUS current 4031 DESCRIPTION 4032 "A collection of objects providing per-port packet 4033 statistics for all VLANs currently configured on this 4034 device for high capacity interfaces, defined as those 4035 that have the value of the corresponding instance of 4036 ifSpeed greater than 650,000,000 bits/second." 4037 ::= { qBridgeGroups 11 } 4039 qBridgeLearningConstraintsGroup OBJECT-GROUP 4040 OBJECTS { 4041 dot1qConstraintType, 4042 dot1qConstraintStatus 4043 } 4044 STATUS current 4045 DESCRIPTION 4046 "A collection of objects defining the Filtering Database 4047 constraints all VLANs have with each other." 4048 ::= { qBridgeGroups 12 } 4050 qBridgeLearningConstraintDefaultGroup OBJECT-GROUP 4051 OBJECTS { 4052 dot1qConstraintSetDefault, 4053 dot1qConstraintTypeDefault 4054 } 4055 STATUS current 4056 DESCRIPTION 4057 "A collection of objects defining the default Filtering 4058 Database constraints for VLANs which have no specific 4059 constraints defined." 4060 ::= { qBridgeGroups 13 } 4062 qBridgeClassificationDeviceGroup OBJECT-GROUP 4063 OBJECTS { 4064 dot1vProtocolGroupId, 4065 dot1vProtocolGroupRowStatus 4066 } 4067 STATUS current 4068 DESCRIPTION 4069 "VLAN classification information for the bridge." 4070 ::= { qBridgeGroups 14 } 4072 qBridgeClassificationPortGroup OBJECT-GROUP 4073 OBJECTS { 4074 dot1vProtocolPortGroupVid, 4075 dot1vProtocolPortRowStatus 4076 } 4077 STATUS current 4078 DESCRIPTION 4079 "VLAN classification information for individual ports." 4080 ::= { qBridgeGroups 15 } 4082 qBridgePortGroup2 OBJECT-GROUP 4083 OBJECTS { 4084 dot1qPvid, 4085 dot1qPortAcceptableFrameTypes, 4086 dot1qPortIngressFiltering, 4087 dot1qPortGvrpStatus, 4088 dot1qPortGvrpFailedRegistrations, 4089 dot1qPortGvrpLastPduOrigin, 4090 dot1qPortRestrictedVlanRegistration 4091 } 4092 STATUS current 4093 DESCRIPTION 4094 "A collection of objects providing port level VLAN 4095 control and status information for all ports." 4096 ::= { qBridgeGroups 16 } 4098 -- ------------------------------------------------------------- 4099 -- compliance statements 4100 -- ------------------------------------------------------------- 4102 qBridgeCompliance MODULE-COMPLIANCE 4103 STATUS deprecated 4104 DESCRIPTION 4105 "The compliance statement for device support of Virtual 4106 LAN Bridge services. 4108 RFC2674 was silent about the expected persistence of the 4109 read-write objects in this MIB module. Applications MUST 4110 NOT assume that the values of the read-write objects are 4111 persistent across reinitializations of the management 4112 system, and MUST NOT assume that the values are not 4113 persistent across reinitializations of the management 4114 system." 4116 MODULE 4117 MANDATORY-GROUPS { 4118 qBridgeBaseGroup, 4119 qBridgeVlanGroup, 4120 qBridgeVlanStaticGroup, 4121 qBridgePortGroup 4122 } 4124 GROUP qBridgeFdbUnicastGroup 4125 DESCRIPTION 4126 "This group is mandatory for bridges that implement 4127 802.1Q transparent bridging." 4129 GROUP qBridgeFdbMulticastGroup 4130 DESCRIPTION 4131 "This group is mandatory for bridges that implement 4132 802.1Q transparent bridging." 4134 GROUP qBridgeServiceRequirementsGroup 4135 DESCRIPTION 4136 "This group is mandatory for bridges that implement 4137 extended filtering services. All objects must be 4138 read-write if extended-filtering services are 4139 enabled." 4141 GROUP qBridgeFdbStaticGroup 4142 DESCRIPTION 4143 "This group is optional." 4145 GROUP qBridgeVlanStatisticsGroup 4146 DESCRIPTION 4147 "This group is optional as there may be significant 4148 implementation cost associated with its support." 4150 GROUP qBridgeVlanStatisticsOverflowGroup 4151 DESCRIPTION 4152 "This group is optional as there may be significant 4153 implementation cost associated with its support. It is most 4154 relevant for high capacity interfaces where the SNMP agent 4155 supports only SNMPv1." 4157 GROUP qBridgeVlanHCStatisticsGroup 4158 DESCRIPTION 4159 "This group is optional as there may be significant 4160 implementation cost associated with its support. It is most 4161 relevant for high capacity interfaces." 4163 GROUP qBridgeLearningConstraintsGroup 4164 DESCRIPTION 4165 "This group is mandatory for devices implementing 4166 both Independent VLAN Learning (IVL) and Shared 4167 VLAN Learning (SVL) modes of operation of the 4168 filtering database, as defined by IEEE 802.1Q." 4170 GROUP qBridgeLearningConstraintDefaultGroup 4171 DESCRIPTION 4172 "This group is mandatory for devices implementing 4173 both Independent VLAN Learning (IVL) and Shared 4174 VLAN Learning (SVL) modes of operation of the 4175 filtering database, as defined by IEEE 802.1Q." 4177 OBJECT dot1qPortAcceptableFrameTypes 4178 MIN-ACCESS read-only 4179 DESCRIPTION 4180 "Write access is not required as this is an optional 4181 capability in IEEE 802.1Q." 4183 OBJECT dot1qPortIngressFiltering 4184 MIN-ACCESS read-only 4185 DESCRIPTION 4186 "Write access is not required as this is an optional 4187 capability in IEEE 802.1Q." 4189 OBJECT dot1qConstraintSetDefault 4190 MIN-ACCESS read-only 4191 DESCRIPTION 4192 "Write access is not required as this is an optional 4193 capability in IEEE 802.1Q." 4195 OBJECT dot1qConstraintTypeDefault 4196 MIN-ACCESS read-only 4197 DESCRIPTION 4198 "Write access is not required as this is an optional 4199 capability in IEEE 802.1Q." 4201 ::= { qBridgeCompliances 1 } 4203 qBridgeCompliance2 MODULE-COMPLIANCE 4204 STATUS current 4205 DESCRIPTION 4206 "The compliance statement for device support of Virtual 4207 LAN Bridge services. 4209 This document clarifies the persistence requirements for 4210 the read-write objects in this MIB module. All 4211 implementations claiming compliance to qBridgeCompliance2 4212 MUST retain the values of those read-write objects that 4213 specify this requirement." 4215 MODULE 4216 MANDATORY-GROUPS { 4217 qBridgeBaseGroup, 4218 qBridgeVlanGroup, 4219 qBridgeVlanStaticGroup, 4220 qBridgePortGroup2 4222 } 4224 GROUP qBridgeFdbUnicastGroup 4225 DESCRIPTION 4226 "This group is mandatory for bridges that implement 4227 802.1Q transparent bridging." 4229 GROUP qBridgeFdbMulticastGroup 4230 DESCRIPTION 4231 "This group is mandatory for bridges that implement 4232 802.1Q transparent bridging." 4234 GROUP qBridgeServiceRequirementsGroup 4235 DESCRIPTION 4236 "This group is mandatory for bridges that implement 4237 extended filtering services. All objects must be 4238 read-write if extended-filtering services are 4239 enabled." 4241 GROUP qBridgeFdbStaticGroup 4242 DESCRIPTION 4243 "This group is optional." 4245 GROUP qBridgeVlanStatisticsGroup 4246 DESCRIPTION 4247 "This group is optional as there may be significant 4248 implementation cost associated with its support." 4250 GROUP qBridgeVlanStatisticsOverflowGroup 4251 DESCRIPTION 4252 "This group is optional as there may be significant 4253 implementation cost associated with its support. It is most 4254 relevant for high capacity interfaces where the SNMP agent 4255 supports only SNMPv1." 4257 GROUP qBridgeVlanHCStatisticsGroup 4258 DESCRIPTION 4259 "This group is optional as there may be significant 4260 implementation cost associated with its support. It is most 4261 relevant for high capacity interfaces." 4263 GROUP qBridgeLearningConstraintsGroup 4264 DESCRIPTION 4265 "This group is mandatory for devices implementing 4266 both Independent VLAN Learning (IVL) and Shared 4267 VLAN Learning (SVL) modes of operation of the 4268 filtering database, as defined by IEEE 802.1Q." 4270 GROUP qBridgeLearningConstraintDefaultGroup 4271 DESCRIPTION 4272 "This group is mandatory for devices implementing 4273 both Independent VLAN Learning (IVL) and Shared 4274 VLAN Learning (SVL) modes of operation of the 4275 filtering database, as defined by IEEE 802.1Q." 4277 GROUP qBridgeClassificationDeviceGroup 4278 DESCRIPTION 4279 "This group is mandatory ONLY for devices implementing 4280 VLAN Classification as specified in IEEE 802.1v." 4282 GROUP qBridgeClassificationPortGroup 4283 DESCRIPTION 4284 "This group is mandatory ONLY for devices implementing 4285 VLAN Classification as specified in IEEE 802.1v." 4287 OBJECT dot1qPortAcceptableFrameTypes 4288 MIN-ACCESS read-only 4289 DESCRIPTION 4290 "Write access is not required as this is an optional 4291 capability in IEEE 802.1Q." 4293 OBJECT dot1qPortIngressFiltering 4294 MIN-ACCESS read-only 4295 DESCRIPTION 4296 "Write access is not required as this is an optional 4297 capability in IEEE 802.1Q." 4299 OBJECT dot1qConstraintSetDefault 4300 MIN-ACCESS read-only 4301 DESCRIPTION 4302 "Write access is not required as this is an optional 4303 capability in IEEE 802.1Q." 4305 OBJECT dot1qConstraintTypeDefault 4306 MIN-ACCESS read-only 4307 DESCRIPTION 4308 "Write access is not required as this is an optional 4309 capability in IEEE 802.1Q." 4311 OBJECT dot1vProtocolGroupId 4312 MIN-ACCESS read-only 4313 DESCRIPTION 4314 "Write access is not required as this is an optional 4315 capability in IEEE 802.1v." 4317 OBJECT dot1vProtocolGroupRowStatus 4318 MIN-ACCESS read-only 4319 DESCRIPTION 4320 "Write access is not required as this is an optional 4321 capability in IEEE 802.1v." 4323 ::= { qBridgeCompliances 2 } 4325 END 4326 6. Acknowledgments 4328 Much of the groundwork for this document was performed by the IEEE 4329 802.1 working group during the definition of the IEEE 802.1D updates 4330 [802.1D] and IEEE 802.1Q [802.1Q]. 4332 The authors wish to thank the members of the Bridge Working Group, 4333 and David Harrington, Anders SW Christensen, Andrew Smith, Paul 4334 Langille, Anil Rijhsinghani, and Keith McCloghrie in particular for 4335 their comments and suggestions which improved this effort. 4337 Editing for the final draft was done by David Levi. 4339 The new textual conventions related to VLAN-IDs were produced as a 4340 result of a review of the use of VLAN-ID in several MIB modules. 4341 Further investigation found that VLAN-ID objects were defined in a 4342 few other MIB modules. The editor would like to thank all who 4343 contributed to the discussion which resulted in these new textual 4344 conventions. Specifically Bert Wijnen, Les Bell, Andrew Smith, Mike 4345 Heard, Randy Presuhn, Dan Romascanu, Eduardo Cardona, Tom Petch, 4346 Juergen Schoenwaelder, Richard Woundy, Tony Jeffree and William 4347 Murwin. We also received input and feedback from IEEE confirming 4348 that the values 0 and 4095 are not used for identifying a specific 4349 VLAN-ID and so can be used to represent none or a wildcard (see 4350 Appendix A). 4352 7. IANA Considerations 4354 There are no special considerations for IANA related to this draft. 4355 The MIB modules in this document are updates to MIB modules with 4356 previously assigned IANA identifiers. 4358 8. Security Considerations 4360 There are a number of management objects defined in this MIB module 4361 with a MAX-ACCESS clause of read-write and/or read-create. Such 4362 objects may be considered sensitive or vulnerable in some network 4363 environments. The support for SET operations in a non-secure 4364 environment without proper protection can have a negative effect on 4365 network operations. These tables and objects and their 4366 sensitivity/vulnerability are described below. 4368 The following tables and objects in the P-BRIDGE-MIB can be 4369 manipulated to interfere with the operation of priority classes. 4370 This could, for example, be used to force a reinitialization of state 4371 machines, thus causing network instability. Another possibility 4372 would be for an attacker to override established policy on port 4373 priorities, thus giving a user (or an attacker) unauthorized 4374 preferential treatment. 4376 dot1dTrafficClassesEnabled 4377 dot1dGmrpStatus 4378 dot1dPortPriorityTable 4379 dot1dUserPriorityRegenTable 4380 dot1dTrafficClassTable 4381 dot1dPortGarpTable 4382 dot1dPortGmrpTable 4384 The following tables and objects in the Q-BRIDGE-MIB could be 4385 manipulated to interfere with the operation of virtual LANs. This 4386 could, for example, be used to force a reinitialization of state 4387 machines to cause network instability, or changing the forwarding and 4388 filtering policies. 4390 dot1qGvrpStatus 4391 dot1qForwardAllTable 4392 dot1qStaticUnicastTable 4393 dot1qStaticMulticastTable 4394 dot1qVlanStaticTable 4395 dot1qPortVlanTable 4396 dot1qLearningConstraintsTable 4397 dot1vProtocolGroupTable 4398 dot1vProtocolPortTable 4400 Some of the readable objects in this MIB module (i.e., objects with a 4401 MAX-ACCESS other than not-accessible) may be considered sensitive or 4402 vulnerable in some network environments. It is thus important to 4403 control even GET and/or NOTIFY access to these objects and possibly 4404 to even encrypt the values of these objects when sending them over 4405 the network via SNMP. These are the tables and objects and their 4406 sensitivity/vulnerability. 4408 The objects dot1dDeviceCapabilities and dot1dPortCapabilitiesTable in 4409 the P-BRIDGE-MIB could be used by an attacker to determine which 4410 attacks might be useful to attempt against a given device. 4412 The following read-only tables and objects in the Q-BRIDGE-MIB could 4413 be used by an attacker to determine which attacks might be useful to 4414 attempt against a given device, could be used by an attacker to 4415 detect whether their attacks are being blocked or filtered, or could 4416 be used to understand the logical topology of the network. 4418 dot1qMaxVlanID 4419 dot1qMaxSupportedVlans 4420 dot1qNumVlans 4421 dot1qFdbTable 4422 dot1qTpFdbTable 4423 dot1qTpGroupTable 4424 dot1qVlanCurrentTable 4425 dot1qPortVlanStatisticsTable 4427 SNMP versions prior to SNMPv3 did not include adequate security. 4428 Even if the network itself is secure (for example by using IPSec), 4429 even then, there is no control as to who on the secure network is 4430 allowed to access and GET/SET (read/change/create/delete) the objects 4431 in this MIB module. 4433 It is RECOMMENDED that implementers consider the security features as 4434 provided by the SNMPv3 framework (see [RFC3410], section 8), 4435 including full support for the SNMPv3 cryptographic mechanisms (for 4436 authentication and privacy). 4438 Further, deployment of SNMP versions prior to SNMPv3 is NOT 4439 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 4440 enable cryptographic security. It is then a customer/operator 4441 responsibility to ensure that the SNMP entity giving access to an 4442 instance of this MIB module is properly configured to give access to 4443 the objects only to those principals (users) that have legitimate 4444 rights to indeed GET or SET (change/create/delete) them. 4446 9. Normative References 4448 [BRIDGE-MIB] Norseth, K., and E. Bell, editors "Definitions of 4449 Managed Objects for Bridges", RFC 1493bis, February 2005. 4451 -- NOTE to RFC Ed.: please replace 1493bis with actual RFC 4452 number, update the reference and remove this note 4454 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4455 Rose, M., and S. Waldbusser, "Structure of Management 4456 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 4457 1999. 4459 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4460 Rose, M., and S. Waldbusser, "Textual Conventions for 4461 SMIv2", STD 58, RFC 2579, April 1999. 4463 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4464 Rose, M., and S. Waldbusser, "Conformance Statements for 4465 SMIv2", STD 58, RFC 2580, April 1999. 4467 [RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and 4468 McCloghrie, "Definitions of Managed Objects for Bridges 4469 with Traffic Classes, Multicast Filtering and Virtual LAN 4470 Extensions", RFC 2674, August 1999. 4472 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 4473 MIB", RFC 2863, June 2000. 4475 [RFC3418] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., 4476 "Management Information Base (MIB) for the Simple Network 4477 Management Protocol (SNMP)", STD 62, RFC 3418, March 1991. 4479 [802.1D] "Information technology - Telecommunications and 4480 information exchange between systems - Local and 4481 metropolitan area networks - Common specifications - Part 4482 3: Media Access Control (MAC) Bridges: Revision. This is 4483 a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 4484 802.6k-1992. It incorporates P802.11c, P802.1p and 4485 P802.12e." ISO/IEC 15802-3: 1998. 4487 [802.1Q] ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and 4488 Metropolitan Area Networks: Virtual Bridged Local Area 4489 Networks", 2003. 4491 [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE 4492 Standard for Information technology - Telecommunications 4493 and information exchange between systems - Local and 4494 metropolitan area networks - Common specifications - Part 4495 3: Media Access Control (MAC) Bridges: Technical and 4496 Editorial Corrections". 4498 [802.1u] IEEE 802.1u-2001, "(Amendment to IEEE Standard 802.1Q) IEEE 4499 Standard for Local and metropolitan area networks - Virtual 4500 Bridged Local Area Networks - Amendment 1: Technical and 4501 Editorial Corrections". 4503 [802.1v] IEEE 802.1v-2001, "(Amendment to IEEE Standard 802.1Q) IEEE 4504 Standards for Local and Metropolitan Area Networks: Virtual 4505 Bridged Local Area Networks--Amendment 2: VLAN 4506 Classification by Protocol and Port". 4508 10. Informative References 4510 [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. 4511 McCloghrie, "Definitions of Managed Objects for Bridges", 4512 RFC 1493, July 1993. 4514 [I-D.ietf-ipcdn-qos-mib] Patrick, M. and W. Murwin, "Data Over Cable 4515 System Interface Specification Quality of Service 4516 Management Information Base (DOCSIS-QOS MIB)", draft-ietf- 4517 ipcdn-qos-mib (work in progress), February 2005. 4519 -- NOTE to RFC Editor: please replace with appropriate RFC 4520 reference. 4522 [I-D.ietf-rmonmib-sspm-mib] Kalbfleisch, C., Cole, R. and D. Romascanu, 4523 "Definition of Managed Objects for Synthetic Sources for 4524 Performance Monitoring Algorithms.", draft-ietf-rmonmib- 4525 sspm-mib-12 (work in progress), June 2004. 4527 -- NOTE to RFC Editor: please replace with appropriate RFC 4528 reference. 4530 [RFC2613] Waterman, R., Lahaye, B., Romascanu, D. and S. Waldbusser, 4531 "Remote Network Monitoring MIB Extensions for Switched 4532 Networks Version 1.0", RFC 2613, June 1999. 4534 [RFC3318] Sahita, R., Hahn, S., Chan, K. and K. McCloghrie, 4535 "Framework Policy Information Base", RFC 3318, March 2003. 4537 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 4538 "Introduction and Applicability Statements for Internet- 4539 Standard Management Framework", RFC 3410, December 2002. 4541 11. Contact Information 4543 David Levi 4544 Nortel Networks 4545 4655 Great America Parkway 4546 Santa Clara, CA 95054 4547 USA 4549 Phone: +1 865 686 0432 4550 Email: dlevi@nortel.com 4552 David Harrington 4553 Effective Software 4554 50 Harding Rd. 4555 Portsmouth, NH 03801 4556 USA 4558 Phone: +1 603 436 8634 4559 Email: ietfdbh@comcast.net 4561 Vivian Ngai 4562 Salt lake City, UT 4563 USA 4565 Email: vivian_ngai@acm.org 4567 Les Bell 4568 Hemel Hempstead 4569 Herts. HP2 7YU 4570 UK 4572 EMail: elbell@ntlworld.com 4573 Andrew Smith 4574 Beijing Harbour Networks 4575 Jiuling Building 4576 21 North Xisanhuan Ave. 4577 Beijing, 100089 4578 PRC 4580 Fax: +1 415 345 1827 4581 EMail: ah_smith@acm.org 4583 Paul Langille 4584 Newbridge Networks 4585 5 Corporate Drive 4586 Andover, MA 01810 4587 USA 4589 Phone: +1 978 691 4665 4590 EMail: langille@newbridge.com 4592 Anil Rijhsinghani 4593 Accton Technology Corporation 4594 5 Mount Royal Ave 4595 Marlboro, MA 01752 4596 USA 4597 Email: anil@accton.com 4599 Keith McCloghrie 4600 Cisco Systems, Inc. 4601 170 West Tasman Drive 4602 San Jose, CA 95134-1706 4603 USA 4605 Phone: +1 408 526 5260 4606 EMail: kzm@cisco.com 4608 Appendix A. Email from Tony Jeffrey from IEEE 4610 -----Original Message----- 4611 From: Tony Jeffree [mailto:tony@jeffree.co.uk] 4612 Sent: Friday, 6th of June 2003 17:16 4613 To: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 4614 Subject: RE: VLAn ID 4616 Bert et al - 4618 We have concluded that the use of 4095 as a wildcard is acceptable 4619 to 802.1, and we will make any necessary changes to 802.1Q in due 4620 course to relax the current stated restriction. However, we need 4621 to know whether that is all that needs to be done to 802.1Q - i.e., 4622 is there any need to change our definitions of the managed objects 4623 in the document (Clause 12) to reflect the interpretation of 4095 4624 as a wildcard, or is this simply an issue for the SNMP machinery 4625 to handle? 4627 Regards, 4628 Tony 4630 Copyright Statement 4632 Copyright (C) The Internet Society (2005). This document is subject 4633 to the rights, licenses and restrictions contained in BCP 78, and 4634 except as set forth therein, the authors retain all their rights. 4636 This document and the information contained herein are provided on an 4637 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 4638 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 4639 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 4640 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 4641 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 4642 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4644 Disclaimer of Validity 4646 The IETF takes no position regarding the validity or scope of any 4647 Intellectual Property Rights or other rights that might be claimed to 4648 pertain to the implementation or use of the technology described in 4649 this document or the extent to which any license under such rights 4650 might or might not be available; nor does it represent that it has 4651 made any independent effort to identify any such rights. Information 4652 on the procedures with respect to rights in RFC documents can be 4653 found in BCP 78 and BCP 79. 4655 Copies of IPR disclosures made to the IETF Secretariat and any 4656 assurances of licenses to be made available, or the result of an 4657 attempt made to obtain a general license or permission for the use of 4658 such proprietary rights by implementers or users of this 4659 specification can be obtained from the IETF on-line IPR repository at 4660 http://www.ietf.org/ipr. 4662 The IETF invites any interested party to bring to its attention any 4663 copyrights, patents or patent applications, or other proprietary 4664 rights that may cover technology that may be required to implement 4665 this standard. Please address the information to the IETF at ietf- 4666 ipr@ietf.org.