idnits 2.17.1 draft-ietf-bridge-rstpmib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([RFC2578], [Q-BRIDGE-MIB], [BRIDGEMIB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 3 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (July 2001) is 8319 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'Q-BRIDGE-MIB' is mentioned on line 199, but not defined == Missing Reference: 'BRIDGE-MIB' is mentioned on line 180, but not defined == Missing Reference: 'USM' is mentioned on line 948, but not defined == Missing Reference: 'VACM' is mentioned on line 949, but not defined ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 1493 (ref. 'BRIDGEMIB') (Obsoleted by RFC 4188) ** Obsolete normative reference: RFC 2674 (ref. 'QBRIDGEMIB') (Obsoleted by RFC 4363) Summary: 19 errors (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft E. Bell 3 Expires January 2001 3Com Corp. 4 draft-ietf-bridge-rstpmib-00.txt V. Ngai 5 Enterasys Networks 6 July 2001 8 Definitions of Managed Objects for Bridges with Rapid Spanning Tree 9 Protocol and VLAN Classification Extensions 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of Section 10 of RFC2026. Internet-Drafts are working documents of 15 the Internet Engineering Task Force (IETF), its areas, and its 16 working groups. Note that other groups may also distribute working 17 documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/1id-abstracts.html 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html 30 Copyright Notice 32 Copyright (C) The Internet Society (2001). All Rights Reserved. 34 Abstract 36 This memo defines a portion of the Management Information Base (MIB) 37 for use with network management protocols in TCP/IP based internets. 38 In particular, it defines three MIB modules for managing the new 39 capabilities of MAC bridges defined by the IEEE P802.1t [802.1t], 40 P802.1u [802.1u], P802.1v [802.1v] and P802.1w [802.1w] amendments to 41 IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN) 42 segments. One MIB module defines objects for managing Rapid Spanning 43 Tree Protocol, one for controlling Restricted VLAN Registration, and 44 one for VLAN Classification. 46 Provisions are made for support of transparent bridging. Provisions 47 are also made so that these objects apply to bridges connected by 48 subnetworks other than LAN segments. This memo also includes several 49 MIB modules in a manner that is compliant to SMIv2 [RFC2578]. 51 This memo supplements RFC 1493 [BRIDGEMIB] and RFC 2674 [Q-BRIDGE- 52 MIB]. 54 Table of Contents 56 1 The SNMP Management Framework ................................ 3 57 2 Overview ..................................................... 4 58 2.1 Scope ...................................................... 4 59 3 Structure of MIBs ............................................ 4 60 3.1 Structure of RSTP-MIB ...................................... 5 61 3.2 Structure of U-BRIDGE-MIB .................................. 5 62 3.3 Structure of V-BRIDGE-MIB .................................. 5 63 3.3.1 The dot1vProtocol Group .................................. 6 64 3.4 Relationship to Other MIBs ................................. 6 65 3.4.1 Relationship to Original Bridge MIB ...................... 6 66 3.4.1.1 The dot1dBase Group .................................... 6 67 3.4.1.2 The dot1dStp Group ..................................... 6 68 3.4.1.3 The dot1dTp Group ...................................... 7 69 3.4.1.4 The dot1dStatic Group .................................. 7 70 3.4.2 Relation to the Q-BRDIGE-MIB module defined in RFC2674 ... 7 71 3.4.2.1 The dot1qBase Group .................................... 7 72 3.4.2.2 The dot1qTp Group ...................................... 7 73 3.4.2.3 The dot1qStatic Group .................................. 8 74 3.4.2.4 The dot1qVlan Group .................................... 8 75 4 Definition for RSTP-MIB ...................................... 8 76 5 Definition for U-BRIDGE-MIB .................................. 13 77 6 Definition for V-BRIDGE-MIB .................................. 15 78 7 Acknowledgments .............................................. 20 79 8 Security consideration ....................................... 20 80 9 References ................................................... 21 81 10 Authors' Addresses .......................................... 23 82 11 Full Copyright .............................................. 24 83 1. The SNMP Management Framework 85 The SNMP Management Framework presently consists of five major 86 components: 88 o An overall architecture, described in RFC 2571 [RFC2571]. 90 o Mechanisms for describing and naming objects and events for the 91 purpose of management. The first version of this Structure of 92 Management Information (SMI) is called SMIv1 and described in 93 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 94 1215 [RFC1215]. The second version, called SMIv2, is described 95 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 96 STD 58, RFC 2580 [RFC2580]. 98 o Message protocols for transferring management information. The 99 first version of the SNMP message protocol is called SNMPv1 and 100 described in STD 15, RFC 1157 [RFC1157]. A second version of 101 the SNMP message protocol, which is not an Internet standards 102 track protocol, is called SNMPv2c and described in RFC 1901 103 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 104 message protocol is called SNMPv3 and described in RFC 1906 105 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 107 o Protocol operations for accessing management information. The 108 first set of protocol operations and associated PDU formats is 109 described in STD 15, RFC 1157 [RFC1157]. A second set of 110 protocol operations and associated PDU formats is described in 111 RFC 1905 [RFC1905]. 113 o A set of fundamental applications described in RFC 2573 114 [RFC2573] and the view-based access control mechanism described 115 in RFC 2575 [RFC2575]. 117 A more detailed introduction to the current SNMP Management Framework 118 can be found in RFC 2570 [RFC2570]. 120 Managed objects are accessed via a virtual information store, termed 121 the Management Information Base or MIB. Objects in the MIB are 122 defined using the mechanisms defined in the SMI. 124 This memo specifies a MIB module that is compliant to the SMIv2. A 125 MIB conforming to the SMIv1 can be produced through the appropriate 126 translations. The resulting translated MIB must be semantically 127 equivalent, except where objects or events are omitted because no 128 translation is possible (use of Counter64). Some machine readable 129 information in SMIv2 will be converted into textual descriptions in 130 SMIv1 during the translation process. However, this loss of machine 131 readable information is not considered to change the semantics of the 132 MIB. 134 2. Overview 136 A common device present in many networks in the Bridge. This device 137 is used to connect Local Area Network segments below the network 138 layer. These devices are often known as 'layer 2 switches'. 140 There are two major modes defined for this bridging: Source-Route and 141 transparent. Source-Route bridging is described by IEEE 802.5 142 [802.5] and is not discussed further in this document. 144 The transparent method of bridging is defined by IEEE 802.1D-1998 145 [802.1D] Managed objects for that original specification of 146 transparent bridging were defined in RFC 1493 [BRIDGEMIB]. 148 2.1. Scope 150 This MIB includes a comprehensive set of managed objects which 151 attempts to match the set defined in IEEE P802.1t [802.1t], P802.1u 152 [802.1u], P802.1v [802.1v] and P802.1w [802.1w]. 154 3. Structure of MIBs 156 This document defines additional objects, on top of those existing in 157 the original BRIDGE-MIB module defined in [BRIDGEMIB]: that MIB 158 module is to be maintained unchanged for backwards compatibility. 159 Section 3.4.3 of the present document contains some recommendations 160 regarding usage of objects in the original bridge MIB by devices 161 implementing the enhancements defined here. 163 Three MIB modules are defined here: 165 (1) Managed objects for an extended bridge MIB module RSTP-MIB for 166 Rapid Spanning Tree Protocol defined by IEEE P802.1t and IEEE 167 P802.1w. 169 (2) Managed Objects for an extended virtual bridge MIB module U- 170 BRIDGE-MIB for Restricted VLAN Registration control 171 enhancement defined by IEEE P802.1u. 173 (3) Managed Objects for an extended bridge MIB module V-BRIDGE-MIB 174 for VLAN classification by Protocol and Port enhancement 175 defined by IEEE P802.1v. 177 3.1. Structure of RSTP-MIB 179 Objects in this MIB are defined as an addition to the dot1dStp group 180 in the original bridge MIB [BRIDGE-MIB]. The overall structure is 181 shown below: 183 Bridge MIB Name IEEE P802.1t(t) or 802.1w(w) 184 Reference 186 dot1dStp 187 dot1dStpVersion (w) 17.6.1 ForceVersion 188 dot1dStpPathCostDefault 189 dot1dStpExtPortTable 190 dot1dStpPortProtocolMigration (w) 17.18.10 mcheck 191 dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort 192 dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort 193 dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC 194 dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC 196 3.2. Structure of U-BRIDGE-MIB 198 Objects in this MIB are defined as an addition to the dot1qVlan group 199 in the Virtual Bridge MIB [Q-BRIDGE-MIB]. The overall structure is 200 shown below: 202 Virtual Bridge MIB Name IEEE P802.1u Reference 204 dot1qVlan 205 dot1qExtPortVlanTable 206 dot1qPortRestrictedRegistration 11.2.3.2.3 Restricted 207 VLAN Registration 209 3.3. Structure of V-BRIDGE-MIB 211 Objects in this MIB are arranged in a single group which is organized 212 as a set of related objects. The overall structure and assignment of 213 objects to the group is shown below: 215 Bridge MIB Name IEEE P802.1v Reference 217 dot1vProtocol 218 dot1vProtocolGroupTable 8.6.4 Protocol Group Database, 219 8.6.2 Protocol Template 220 dot1vProtocolTemplateFrameType 221 dot1vProtocolTemplateProtocolValue 222 dot1vProtocolGroupId 8.6.3 Protocol Group Identifier 223 dot1vProtocolPortTable 8.4.4 VID Set for each Port 224 dot1vProtocolPortGroupId 225 dot1vProtocolGroupVid 227 3.3.1. The dot1vProtocol Group 229 This group contains objects that describe the bridge's state with 230 respect VLAN classification by Protocol and Port. If VLAN 231 classification is not supported, this group will not be implemented. 233 3.4. Relationship to Other MIBs 235 As described above, some IEEE 802.1D management objects have not been 236 included in this MIB because they overlap with objects in other MIBs 237 applicable to a bridge implementing this MIB. In particular, it is 238 assumed that a bridge implementing this MIB will implement the 239 original bridge MIB [BRIDGEMIB]. If the U-BRIDGE-MIB and V-BRIDGE- 240 MIB modules are implemented, a bridge will also implement the Q- 241 BRIDGE-MIB module defined in RFC 2674 [QBRIDGEMIB]. 243 3.4.1. Relation to Original Bridge MIB 245 This section defines how objects in the original bridge MIB module 246 [BRIDGEMIB] should be represented for devices which implement all the 247 MIB modules described in this memo. Some of the old objects are less 248 useful in such devices but must still be implemented for reasons of 249 backwards compatibility. 251 3.4.1.1. The dot1dBase Group 253 This mandatory group contains the objects which are applicable to all 254 types of bridges. Interpretation of this group is unchanged. 256 3.4.1.2. The dot1dStp Group 258 This group contains the objects that denote the bridge's state with 259 respect to the Spanning Tree Protocol. If a node does not implement 260 the Spanning Tree Protocol, this group will not be implemented. 262 In a device supporting the Spanning Tree Algorithm and Protocol 263 defined in IEEE 802.1D-1998 Clause 8, interpretation of this group is 264 unchanged. 266 In a device supporting the Rapid Spanning Tree Algorithm and Protocol 267 defined in IEEE 802.1w Clause 17, the interpretation of objects in 268 this group is unchanged except for those listed below: 270 dot1dStpPriority 271 Definition remains unchanged, but the permissible values are 272 changed to 0-61440, in steps of 4096. 274 dot1dStpPortPriority 275 Definition remains unchanged, but the permissible values are 276 changed to 0-240, in steps of 16. 278 dot1dStpTimeSinceTopologyChange 279 The time since the tcWhile timer for any port on this Bridge was 280 non-zero. 282 dot1dStpTopChanges 283 The number of times that there have been at least one non-zero 284 tcWhile timer on this Bridge. 286 In a device supporting the 32-bit default Path Costs defined in IEEE 287 802.1t Table 8-5, the interpretation of objects in this group is 288 unchanged except for the following: 290 dot1dStpPortPathCost 291 Definition remains unchanged, but the permissible values are 292 extended to 1-200,000,000. 293 3.4.1.3. The dot1dTp Group 295 This group contains objects that describe the entity's state with 296 respect to transparent bridging. Interpretation for this group is 297 unchanged. 299 3.4.1.4. The dot1dStatic Group 301 This group contains objects that describe the entity's state with 302 respect to destination-address filtering. Interpretation for this 303 group is unchanged. 305 3.4.2. Relation to the Q-BRIDGE-MIB module defined in RFC 2674 307 This section defines how objects in the Q-BRIDGE-MIB module 308 [QBRIDGEMIB] should be represented for devices which implement the 309 U-BRIDGE-MIB and V-BRIDGE-MIB module described in this memo. 311 3.4.2.1. The dot1qBase Group 313 This mandatory group contains the objects which are applicable to all 314 bridges implementing IEEE 802.1Q virtual LANs. 316 3.4.2.2. The dot1qTp Group 318 This group contains objects that control the operation and report the 319 status of transparent bridging. 321 3.4.2.3. The dot1qStatic Group 323 This group contains objects that control static configuration 324 information for transparent bridging. 326 3.4.2.4. The dot1qVlan Group 328 This group contains objects that control configuration and report 329 status of the Virtual LANs known to a bridge. 331 4. Definitions for RSTP-MIB 333 RSTP-MIB DEFINITIONS ::= BEGIN 335 -- ------------------------------------------------------------- 336 -- MIB for IEEE 802.1w Rapid Spanning Tree Protocol 337 -- ------------------------------------------------------------- 339 IMPORTS 340 MODULE-IDENTITY, OBJECT-TYPE 341 FROM SNMPv2-SMI 342 TruthValue 343 FROM SNMPv2-TC 344 MODULE-COMPLIANCE, OBJECT-GROUP 345 FROM SNMPv2-CONF 346 dot1dBridge, dot1dStp, dot1dStpPortEntry 347 FROM BRIDGE-MIB; 349 rstpMIB MODULE-IDENTITY 350 LAST-UPDATED "200107130000Z" 351 ORGANIZATION "IETF Bridge MIB Working Group" 352 CONTACT-INFO 353 "Email: Bridge-mib@ietf.org" 354 DESCRIPTION 355 "The Bridge MIB Extension module for managing devices 356 that support the Rapid Spanning Tree Protocol defined 357 by IEEE 802.1w." 358 REVISION "200107130000Z" 359 DESCRIPTION 360 "Draft 0" 361 ::= { dot1dBridge 11 } 363 -- ------------------------------------------------------------- 364 -- Addition to the dot1dStp group 365 -- ------------------------------------------------------------- 367 dot1dStpVersion OBJECT-TYPE 368 SYNTAX INTEGER { 369 stpCompatible(0), 370 rstp(2) 371 } 372 MAX-ACCESS read-write 373 STATUS current 374 DESCRIPTION 375 "The version of Spanning Tree Protocol the bridge is 376 currently running. The value 'stpCompatible(0)' 377 indicates the Spanning Tree Protocol specified in 378 IEEE 802.1D and 'rstp(2)' indicates the Rapid Spanning 379 Tree Protocol specified in IEEE 802.1w. New value may 380 be defined as future versions of the protocol become 381 available." 382 REFERENCE 383 "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1" 384 DEFVAL { rstp } 385 ::= { dot1dStp 16 } 387 dot1dStpPathCostDefault OBJECT-TYPE 388 SYNTAX INTEGER { 389 stp8021d1998(1), 390 stp8021t2001(2) 391 } 392 MAX-ACCESS read-write 393 STATUS current 394 DESCRIPTION 395 "The version of the Spanning Tree default Path Costs that 396 are to be used by this Bridge. A value of 8021d1998(1) 397 uses the 16-bit default Path Costs from IEEE Std. 802.1D-1998. 398 A value of stp8021t2001(2) uses the 32-bit default Path 399 Costs from IEEE Std. 802.1t." 400 REFERENCE 401 "IEEE 802.1D & 802.1t Table 8-5" 402 ::= { dot1dStp 17 } 404 dot1dStpExtPortTable OBJECT-TYPE 405 SYNTAX SEQUENCE OF Dot1dStpExtPortEntry 406 MAX-ACCESS not-accessible 407 STATUS current 408 DESCRIPTION 409 "A table that contains port-specific Rapid Spanning Tree 410 information." 411 ::= { dot1dStp 18 } 413 dot1dStpExtPortEntry OBJECT-TYPE 414 SYNTAX Dot1dStpExtPortEntry 415 MAX-ACCESS not-accessible 416 STATUS current 417 DESCRIPTION 418 "A list of Rapid Spanning Tree information maintained by 419 each port." 420 AUGMENTS { dot1dStpPortEntry } 421 ::= { dot1dStpExtPortTable 1 } 423 Dot1dStpExtPortEntry ::= 424 SEQUENCE { 425 dot1dStpPortProtocolMigration 426 TruthValue, 427 dot1dStpPortAdminEdgePort 428 TruthValue, 429 dot1dStpPortOperEdgePort 430 TruthValue, 431 dot1dStpPortAdminPointToPoint 432 INTEGER, 433 dot1dStpPortOperPointToPoint 434 TruthValue 435 } 437 dot1dStpPortProtocolMigration OBJECT-TYPE 438 SYNTAX TruthValue 439 MAX-ACCESS read-write 440 STATUS current 441 DESCRIPTION 442 "When operating in RSTP (version 2) mode, writing TRUE(1) 443 to this object forces this port to transmit RSTP BPDUs. 444 Any other operation on this object has no effect and 445 it always returns FALSE(2) when read." 446 REFERENCE 447 "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26" 448 ::= { dot1dStpExtPortEntry 1 } 450 dot1dStpPortAdminEdgePort OBJECT-TYPE 451 SYNTAX TruthValue 452 MAX-ACCESS read-write 453 STATUS current 454 DESCRIPTION 455 "The administrative value of the Edge Port parameter. A 456 value of TRUE(1) indicates that this port should be 457 assumed as an edge-port and a value of FALSE(2) indicates 458 that this port should be assumed as a non-edge-port." 459 REFERENCE 460 "IEEE 802.1t clause 14.8.2, 18.3.3" 461 ::= { dot1dStpExtPortEntry 2 } 463 dot1dStpPortOperEdgePort OBJECT-TYPE 464 SYNTAX TruthValue 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The operational value of the Edge Port parameter. The 469 object is initialized to the value of 470 dot1dStpPortAdminEdgePort and is set FALSE on reception of 471 a BPDU." 472 REFERENCE 473 "IEEE 802.1t clause 14.8.2, 18.3.4" 474 ::= { dot1dStpExtPortEntry 3 } 476 dot1dStpPortAdminPointToPoint OBJECT-TYPE 477 SYNTAX INTEGER { 478 forceTrue(0), 479 forceFalse(1), 480 auto(2) 481 } 482 MAX-ACCESS read-write 483 STATUS current 484 DESCRIPTION 485 "The administrative point-to-point status of the LAN segment 486 attached to this port. A value of forceTrue(0) indicates that 487 this port should always be treated as if it is connected to 488 a point-to-point link. A value of forceFalse(1) indicates 489 that this port should be treated as having a shared media 490 connection. A value of auto(2) indicates that this port is 491 considered to have a point-to-point link if it is an Aggregator 492 and all of its members are aggregatable, or if the MAC entity 493 is configured for full duplex operation, either through 494 auto-negotiation or by management means." 495 REFERENCE 496 "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" 497 ::= { dot1dStpExtPortEntry 4 } 499 dot1dStpPortOperPointToPoint OBJECT-TYPE 500 SYNTAX TruthValue 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "The operational point-to-point status of the LAN segment 505 attached to this port. It indicates whether a port is 506 considered to have a point-to-point connection or not. 507 The value is determined by management or by auto-detection, 508 as described in the dot1dStpPortAdminPointToPoint object." 509 REFERENCE 510 "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" 511 ::= { dot1dStpExtPortEntry 5 } 513 -- ------------------------------------------------------------- 514 -- rstpMIB - Conformance Information 515 -- ------------------------------------------------------------- 517 rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 1 } 519 rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 } 521 rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 } 523 -- ------------------------------------------------------------- 524 -- Units of conformance 525 -- ------------------------------------------------------------- 527 rstpBridgeGroup OBJECT-GROUP 528 OBJECTS { 529 dot1dStpVersion 530 } 531 STATUS current 532 DESCRIPTION 533 "Rapid Spanning Tree information for the bridge." 534 ::= { rstpGroups 1 } 536 rstpDefaultPathCostGroup OBJECT-GROUP 537 OBJECTS { 538 dot1dStpPathCostDefault 539 } 540 STATUS current 541 DESCRIPTION 542 "Default Spanning Tree path cost information." 543 ::= { rstpGroups 2 } 545 rstpPortGroup OBJECT-GROUP 546 OBJECTS { 547 dot1dStpPortProtocolMigration, 548 dot1dStpPortAdminEdgePort, 549 dot1dStpPortOperEdgePort, 550 dot1dStpPortAdminPointToPoint, 551 dot1dStpPortOperPointToPoint 552 } 553 STATUS current 554 DESCRIPTION 555 "Rapid Spanning Tree information for individual ports." 556 ::= { rstpGroups 3 } 558 -- ------------------------------------------------------------- 559 -- Compliance statements 560 -- ------------------------------------------------------------- 561 rstpCompliance MODULE-COMPLIANCE 562 STATUS current 563 DESCRIPTION 564 "The compliance statement for device support of bridging 565 services." 567 MODULE 568 MANDATORY-GROUPS { 569 rstpBridgeGroup, 570 rstpPortGroup 571 } 572 ::= { rstpCompliances 1 } 574 END 576 5. Definitions for U-BRIDGE-MIB 578 U-BRIDGE-MIB DEFINITIONS ::= BEGIN 580 -- ------------------------------------------------------------- 581 -- MIB for IEEE 802.1u Restricted Group Registration 582 -- ------------------------------------------------------------- 584 IMPORTS 585 MODULE-IDENTITY, OBJECT-TYPE 586 FROM SNMPv2-SMI 587 TruthValue 588 FROM SNMPv2-TC 589 MODULE-COMPLIANCE, OBJECT-GROUP 590 FROM SNMPv2-CONF 591 dot1dBridge, dot1dBasePortEntry 592 FROM BRIDGE-MIB 593 dot1qPortVlanEntry 594 FROM Q-BRIDGE-MIB; 596 uBridgeMIB MODULE-IDENTITY 597 LAST-UPDATED "200107130000Z" 598 ORGANIZATION "IETF Bridge MIB Working Group" 599 CONTACT-INFO 600 "Email: Bridge-mib@ietf.org" 601 DESCRIPTION 602 "The Bridge MIB Extension module for managing devices 603 that allow control over dynamic VLAN registration through 604 Restricted VLAN Registration as defined by IEEE 802.1u." 605 REVISION "200107130000Z" 606 DESCRIPTION 607 "Draft 0" 608 ::= { dot1dBridge 12 } 610 -- ------------------------------------------------------------- 611 -- Augmentation to the dot1qPortVlanTable 612 -- ------------------------------------------------------------- 614 dot1qExtPortVlanTable OBJECT-TYPE 615 SYNTAX SEQUENCE OF Dot1qExtPortVlanEntry 616 MAX-ACCESS not-accessible 617 STATUS current 618 DESCRIPTION 619 "A table containing per port Restricted VLAN Registration 620 control information." 621 ::= { dot1qVlan 11 } 623 dot1qExtPortVlanEntry OBJECT-TYPE 624 SYNTAX Dot1qExtPortVlanEntry 625 MAX-ACCESS not-accessible 626 STATUS current 627 DESCRIPTION 628 "Information controlling VLAN Registration for a port 629 on the device. This is indexed by dot1dBasePort." 630 AUGMENTS { dot1dBasePortEntry } 631 ::= { dot1qExtPortVlanTable 1 } 633 Dot1qExtPortVlanEntry ::= 634 SEQUENCE { 635 dot1qPortRestrictedRegistration 636 TruthValue 637 } 639 dot1qPortRestrictedRegistration OBJECT-TYPE 640 SYNTAX TruthValue 641 MAX-ACCESS read-write 642 STATUS current 643 DESCRIPTION 644 "The state of Restricted Registration on this port. 645 If the value of this control is true(1), then creation 646 of a new dynamic VLAN entry is permitted only if there 647 is a Static VLAN Registration Entry for the VLAN concerned, 648 in which the Registrar Administrative Control value for 649 this port is Normal Registration." 650 REFERENCE 651 "IEEE 802.1u clause 11.2.3.2.3, 12.10.1.7." 652 DEFVAL { false } 653 ::= { dot1qExtPortVlanEntry 1 } 655 -- ------------------------------------------------------------- 656 -- uBridgeMIB - Conformance Information 657 -- ------------------------------------------------------------- 658 uBridgeConformance OBJECT IDENTIFIER ::= { uBridgeMIB 1 } 660 uBridgeGroups OBJECT IDENTIFIER ::= { uBridgeConformance 1 } 662 uBridgeCompliances OBJECT IDENTIFIER ::= { uBridgeConformance 2 } 664 -- ------------------------------------------------------------- 665 -- Units of conformance 666 -- ------------------------------------------------------------- 668 uBridgePortGroup OBJECT-GROUP 669 OBJECTS { 670 dot1qPortRestrictedRegistration 671 } 672 STATUS current 673 DESCRIPTION 674 "Per-port Restricted VLAN Registration Control parameter" 675 ::= { uBridgeGroups 1 } 677 -- ------------------------------------------------------------- 678 -- Compliance statements 679 -- ------------------------------------------------------------- 681 uBridgeCompliance MODULE-COMPLIANCE 682 STATUS current 683 DESCRIPTION 684 "The compliance statement for device support of bridging 685 services." 687 MODULE 688 MANDATORY-GROUPS { 689 uBridgePortGroup 690 } 691 ::= { uBridgeCompliances 1 } 693 END 695 6. Definitions for V-BRIDGE-MIB 697 V-BRIDGE-MIB DEFINITIONS ::= BEGIN 699 -- ------------------------------------------------------------- 700 -- MIB for IEEE 802.1v VLAN Classification by Protocol and Port 701 -- ------------------------------------------------------------- 703 IMPORTS 704 MODULE-IDENTITY, OBJECT-TYPE 705 FROM SNMPv2-SMI 707 MODULE-COMPLIANCE, OBJECT-GROUP 708 FROM SNMPv2-CONF 709 dot1dBridge, dot1dBasePort 710 FROM BRIDGE-MIB; 712 vBridgeMIB MODULE-IDENTITY 713 LAST-UPDATED "200107130000Z" 714 ORGANIZATION "IETF Bridge MIB Working Group" 715 CONTACT-INFO 716 "Email: Bridge-mib@ietf.org" 717 DESCRIPTION 718 "The Bridge MIB Extension module for managing devices 719 that support VLAN Classification by Protocol and Port 720 defined in IEEE 802.1v." 721 REVISION "200107130000Z" 722 DESCRIPTION 723 "Draft 0" 724 ::= { dot1dBridge 13 } 726 vBridgeMIBObjects OBJECT IDENTIFIER ::= { vBridgeMIB 1 } 728 -- ------------------------------------------------------------- 729 -- group in this MIB 730 -- ------------------------------------------------------------- 732 dot1vProtocol OBJECT IDENTIFIER ::= { vBridgeMIBObjects 1 } 734 -- ------------------------------------------------------------- 735 -- dot1vProtocol group 736 -- ------------------------------------------------------------- 738 dot1vProtocolGroupTable OBJECT-TYPE 739 SYNTAX SEQUENCE OF Dot1vProtocolGroupEntry 740 MAX-ACCESS not-accessible 741 STATUS current 742 DESCRIPTION 743 "A table that contains mappings from Protocol 744 Templates to Protocol Group Identifiers used for 745 Port-and-Protocol-based VLAN Classification." 746 REFERENCE 747 "IEEE 802.1v clause 8.6.4" 748 ::= { dot1vProtocol 1 } 750 dot1vProtocolGroupEntry OBJECT-TYPE 751 SYNTAX Dot1vProtocolGroupEntry 752 MAX-ACCESS not-accessible 753 STATUS current 754 DESCRIPTION 755 "A mapping from a Protocol Template to a Protocol 756 Group Identifier." 757 INDEX { dot1vProtocolTemplateFrameType, 758 dot1vProtocolTemplateProtocolValue } 759 ::= { dot1vProtocolGroupTable 1 } 761 Dot1vProtocolGroupEntry ::= 762 SEQUENCE { 763 dot1vProtocolTemplateFrameType 764 INTEGER, 765 dot1vProtocolTemplateProtocolValue 766 OCTET STRING, 767 dot1vProtocolGroupId 768 INTEGER 769 } 771 dot1vProtocolTemplateFrameType OBJECT-TYPE 772 SYNTAX INTEGER { 773 ethernet (1), 774 rfc1042 (2), 775 snap8021H (3), 776 snapOther (4), 777 llcOther (5) 778 } 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "The data-link encapsulation format or the 783 'detagged_frame_type' in a Protocol Template." 784 REFERENCE 785 "IEEE 802.1v clause 8.6.2" 786 ::= { dot1vProtocolGroupEntry 1 } 788 dot1vProtocolTemplateProtocolValue OBJECT-TYPE 789 SYNTAX OCTET STRING (SIZE (2 | 5)) 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "The identification of the protocol above the data-link 794 layer in a Protocol Template. Depending on the 795 frame type, the octet string will have one of the 796 following values: 798 For 'ethernet', 'rfc1042' and 'snap8021H', 799 this is the 16-bit (2-octet) IEEE 802.3 Type Field. 800 For 'snapOther', 801 this is the 40-bit (5-octet) PID. 802 For 'llcOther', 803 this is the 2-octet IEEE 802.2 LSAP pair: 804 first octet for DSAP and second octet for SSAP." 805 REFERENCE 806 "IEEE 802.1v clause 8.6.2" 807 ::= { dot1vProtocolGroupEntry 2 } 809 dot1vProtocolGroupId OBJECT-TYPE 810 SYNTAX INTEGER (0..2147483647) 811 MAX-ACCESS read-create 812 STATUS current 813 DESCRIPTION 814 "Represents a group of protocols that are associated 815 together when assigning a VID to a frame." 816 REFERENCE 817 "IEEE 802.1v clause 8.6.3, 12.10.2.1" 818 ::= { dot1vProtocolGroupEntry 3 } 820 dot1vProtocolPortTable OBJECT-TYPE 821 SYNTAX SEQUENCE OF Dot1vProtocolPortEntry 822 MAX-ACCESS not-accessible 823 STATUS current 824 DESCRIPTION 825 "A table that contains VID sets used for 826 Port-and-Protocol-based VLAN Classification." 827 REFERENCE 828 "IEEE 802.1v clause 8.4.4" 829 ::= { dot1vProtocol 2 } 831 dot1vProtocolPortEntry OBJECT-TYPE 832 SYNTAX Dot1vProtocolPortEntry 833 MAX-ACCESS not-accessible 834 STATUS current 835 DESCRIPTION 836 "A VID set for a port." 837 INDEX { dot1dBasePort, 838 dot1vProtocolPortGroupId } 839 ::= { dot1vProtocolPortTable 1 } 841 Dot1vProtocolPortEntry ::= 842 SEQUENCE { 843 dot1vProtocolPortGroupId 844 INTEGER, 845 dot1vProtocolPortGroupVid 846 INTEGER 847 } 849 dot1vProtocolPortGroupId OBJECT-TYPE 850 SYNTAX INTEGER (1..2147483647) 851 MAX-ACCESS not-accessible 852 STATUS current 853 DESCRIPTION 854 "Designates a group of protocols in the Protocol 855 Group Database." 856 REFERENCE 857 "IEEE 802.1v clause 8.6.3, 12.10.1.2" 858 ::= { dot1vProtocolPortEntry 1 } 860 dot1vProtocolPortGroupVid OBJECT-TYPE 861 SYNTAX INTEGER (1..4094) 862 MAX-ACCESS read-create 863 STATUS current 864 DESCRIPTION 865 "The VID associated with a group of protocols for 866 each port." 867 REFERENCE 868 "IEEE 802.1v clause 8.4.4, 12.10.1.2" 869 ::= { dot1vProtocolPortEntry 2 } 871 -- ------------------------------------------------------------- 872 -- vBridgeMIB - Conformance Information 873 -- ------------------------------------------------------------- 875 vBridgeConformance OBJECT IDENTIFIER ::= { vBridgeMIB 2 } 877 vBridgeGroups OBJECT IDENTIFIER ::= { vBridgeConformance 1 } 879 vBridgeCompliances OBJECT IDENTIFIER ::= { vBridgeConformance 2 } 881 -- ------------------------------------------------------------- 882 -- Units of conformance 883 -- ------------------------------------------------------------- 885 vBridgeDeviceGroup OBJECT-GROUP 886 OBJECTS { 887 dot1vProtocolGroupId 888 } 889 STATUS current 890 DESCRIPTION 891 "VLAN classification information for the bridge." 892 ::= { vBridgeGroups 1 } 894 vBridgePortGroup OBJECT-GROUP 895 OBJECTS { 896 dot1vProtocolPortGroupVid 897 } 898 STATUS current 899 DESCRIPTION 900 "VLAN classification information for individual ports." 901 ::= { vBridgeGroups 2 } 903 -- ------------------------------------------------------------- 904 -- Compliance statements 905 -- ------------------------------------------------------------- 907 vBridgeCompliance MODULE-COMPLIANCE 908 STATUS current 909 DESCRIPTION 910 "The compliance statement for device support of bridging 911 services." 913 MODULE 914 MANDATORY-GROUPS { 915 vBridgeDeviceGroup, 916 vBridgePortGroup 917 } 918 ::= { vBridgeCompliances 1 } 920 END 922 7. Acknowledgments 924 This document was produced on behalf of the Bridge MIB Working Group 925 in the Operations and Management area of the Internet Engineering 926 Task Force. 928 The authors wish to thank the members of the Bridge MIB Working Group 929 and Anders SW Christensen in particular for their comments and 930 suggestions which improved this effort. 932 8. Security Considerations 934 There are a number of management objects defined in this MIB that 935 have a MAX-ACCESS clause of read-write and/or read-create. Such 936 objects may be considered sensitive or vulnerable in some network 937 environments. The support for SET operations in a non-secure 938 environment without proper protection can have a negative effect on 939 network operations. 941 SNMPv1 by itself is not a secure environment. Even if the network 942 itself is secure (for example by using IPSec), even then, there is no 943 control as to who on the secure network is allowed to access and 944 GET/SET (read/change/create/delete) the objects in this MIB. 946 It is recommended that the implementers consider the security 947 features as provided by the SNMPv3 framework. Specifically, the use 948 of the User-based Security Model [USM] and the View-based Access 949 Control Model [VACM] is recommended. 951 9. References 953 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture 954 for Describing SNMP Management Frameworks, RFC 2571, April 955 1999. 957 [RFC1155] Rose, M., and K. McCloghrie, Structure and Identification 958 of Management Information for TCP/IP-based Internets, STD 959 16, RFC 1155, May 1990. 961 [RFC1212] Rose, M., and K. McCloghrie, Concise MIB Definitions, STD 962 16, RFC 1212, March 1991. 964 [RFC1215] M. Rose, A Convention for Defining Traps for use with the 965 SNMP, RFC 1215, March 1991. 967 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 968 Rose, M., and S. Waldbusser, Structure of Management 969 Information Version 2 (SMIv2), STD 58, RFC 2578, April 970 1999. 972 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 973 Rose, M., and S. Waldbusser, Textual Conventions for SMIv2, 974 STD 58, RFC 2579, April 1999. 976 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 977 Rose, M., and S. Waldbusser, Conformance Statements for 978 SMIv2, STD 58, RFC 2580, April 1999. 980 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple 981 Network Management Protocol, STD 15, RFC 1157, May 1990. 983 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 984 Introduction to Community-based SNMPv2, RFC 1901, January 985 1996. 987 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 988 Transport Mappings for Version 2 of the Simple Network 989 Management Protocol (SNMPv2), RFC 1906, January 1996. 991 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, Message 992 Processing and Dispatching for the Simple Network 993 Management Protocol (SNMP), RFC 2572, April 1999. 995 [RFC2574] Blumenthal, U., and B. Wijnen, User-based Security Model 996 (USM) for version 3 of the Simple Network Management 997 Protocol (SNMPv3), RFC 2574, April 1999. 999 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1000 Protocol Operations for Version 2 of the Simple Network 1001 Management Protocol (SNMPv2), RFC 1905, January 1996. 1003 [RFC2573] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, 1004 RFC 2573, April 1999. 1006 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based 1007 Access Control Model (VACM) for the Simple Network 1008 Management Protocol (SNMP), RFC 2575, April 1999. 1010 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1011 Introduction to Version 3 of the Internet-standard Network 1012 Management Framework, RFC 2570, April 1999. 1014 [802.1D] "Information technology - Telecommunications and 1015 information exchange between systems - Local and 1016 metropolitan area networks - Common specifications - Part 1017 3: Media Access Control (MAC) Bridges: Revision. This is 1018 a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k- 1019 1992. It incorporates P802.11c, P802.1p and P802.12e." 1020 ISO/IEC 15802-3: 1998. 1022 [802.1Q] ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and 1023 Metropolitan Area Networks: Virtual Bridged Local Area 1024 Networks", 1998. 1026 [BRIDGEMIB] Decker, E., Langille, P., Rijsinghani, A. and K. 1027 McCloghrie, "Definitions of Managed Objects for Bridges", 1028 RFC 1493, July 1993. 1030 [QBRIDGEMIB] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and 1031 McCloghrie, "Definitions of Managed Objects for Bridges 1032 with Traffic Classes, Multicast Filtering and Virtual LAN 1033 Extensions", RFC 2674, August 1999. 1035 [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE 1036 Standard for Information technology - Telecommunications 1037 and information exchange between systems - Local and 1038 metropolitan area networks - Common specifications - Part 1039 3: Media Access Control (MAC) Bridges: Technical and 1040 Editorial Corrections". 1042 [802.1u] IEEE 802.1u-2001, "(Amendment to IEEE Standard 802.1Q) IEEE 1043 Standard for Local and metropolitan area networks - Virtual 1044 Bridged Local Area Networks - Amendment 1: Technical and 1045 editorial corrections". 1047 [802.1v] IEEE 802.1v-2001, "(Amendment to IEEE Standard 802.1Q) IEEE 1048 Standards for Local and Metropolitan Area Networks: Virtual 1049 Bridged Local Area Networks--Amendment 2: VLAN 1050 Classification by Protocol and Port". 1052 [802.1w] IEEE 802.1w/D10, "(Amendment to IEEE Standard 802.1D) IEEE 1053 Standard for Information technology--Telecommunications and 1054 information exchange between systems--Local and 1055 metropolitan area networks--Common Specifications--Part 3: 1056 Media Access Control (MAC) Bridges: Rapid Reconfiguation". 1058 10. Authors' Addresses 1060 Les Bell 1061 3Com Europe Limited 1062 eCom Centre, Boundary Way 1063 Hemel Hempstead 1064 Herts. HP2 7YU 1065 UK 1067 Phone: +44 1442 438025 1068 Email: Les_Bell@3Com.com 1070 Vivian Ngai 1071 Enterasys Networks 1072 2691 South Decker Lake Lane 1073 Salt Lake City, UT 84119 1075 Phone: +1 801-887-9802 1076 Fax: +1 801-972-5789 1077 Email: vngai@enterasys.com 1079 11. Full Copyright 1081 Copyright (C) The Internet Society (date). All Rights Reserved. 1083 This document and translations of it may be copied and furnished 1084 to others, and derivative works that comment on or otherwise 1085 explain it or assist in its implementation may be prepared, copied, 1086 published and distributed, in whole or in part, without 1087 restriction of any kind, provided that the above copyright notice 1088 and this paragraph are included on all such copies and derivative 1089 works. However, this document itself may not be modified in any 1090 way, such as by removing the copyright notice or references to the 1091 Internet Society or other Internet organizations, except as needed 1092 for the purpose of developing Internet standards in which case the 1093 procedures for copyrights defined in the Internet Standards 1094 process must be followed, or as required to translate it into 1095 languages other than English. 1097 The limited permissions granted above are perpetual and will not 1098 be revoked by the Internet Society or its successors or assigns. 1100 This document and the information contained herein is provided on 1101 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1102 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1103 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1104 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1105 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.