idnits 2.17.1 draft-ietf-bridge-bridgemib-smiv2-02.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. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 33 longer pages, the longest (page 2) being 59 lines 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. ** The abstract seems to contain references ([RFC1493]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 (February 2002) is 8106 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: 'RFC1493' is mentioned on line 1709, but not defined ** Obsolete undefined reference: RFC 1493 (Obsoleted by RFC 4188) == Missing Reference: 'RFC1213' is mentioned on line 292, but not defined == Unused Reference: 'ISO8021D' is defined on line 1784, but no explicit reference was found in the text ** 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE8021D' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO8021D' ** Obsolete normative reference: RFC 1907 (Obsoleted by RFC 3418) Summary: 19 errors (**), 0 flaws (~~), 6 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Editor of this version: 2 Expires August 2002 K.C. Norseth 3 draft-ietf-bridge-bridgemib-smiv2-02.txt Enterasys Networks 4 Obsoletes: 1493 Authors of previous version: 5 E. Bell 6 3Com Corp. 7 E. Decker 8 Cisco Systems, Inc. 9 P. Langille 10 Newbridge Networks 11 A. Rijhsinghani 12 Enterasys Networks 13 K. McCloghrie 14 Cisco Systems, Inc. 15 February 2002 17 Definitions of Managed Objects for Bridges 19 Status of this Memo 21 This document is an Internet Draft and is in full conformance with 22 all provisions of Section 10 of RFC2026. Internet Drafts are working 23 documents of the Internet Engineering Task Force (IETF), its Areas, 24 and its Working Groups. Note that other groups may also distribute 25 working documents as Internet Drafts. 27 Internet Drafts are draft documents valid for a maximum of six 28 months. Internet Drafts may be updated, replaced, or obsoleted by 29 other documents at any time. It is not appropriate to use Internet 30 Drafts as reference material or to cite them other than as a "working 31 draft" or "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/1id-abstracts.html 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 To learn the current status of any Internet-Draft, please check the 40 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 41 Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe), 42 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 44 Copyright Notice 46 Copyright (C) The Internet Society (2002). All Rights Reserved. 48 Abstract 50 This memo defines a portion of the Management Information Base (MIB) 51 for use with network management protocols in TCP/IP based internets. 52 In particular it defines objects for managing MAC bridges based on 53 the IEEE 802.1D-1990 standard between Local Area Network (LAN) 54 segments. Provisions are made for support of transparent bridging. 55 Provisions are also made so that these objects apply to bridges 56 connected by subnetworks other than LAN segments. 58 The MIB presented in this memo is a direct translation of the BRIDGE 59 MIB defined in [RFC1493], to the SMIv2 syntax required for current 60 IETF MIB standards. This memo obsoletes RFC 1493. 62 1. The SNMP Management Framework 64 The SNMP Management Framework presently consists of five major 65 components: 67 o An overall architecture, described in RFC 2571 [RFC2571]. 69 o Mechanisms for describing and naming objects and events for the 70 purpose of management. The first version of this Structure of 71 Management Information (SMI) is called SMIv1 and described in 72 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 73 1215 [RFC1215]. The second version, called SMIv2, is described 74 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 75 STD 58, RFC 2580 [RFC2580]. 77 o Message protocols for transferring management information. The 78 first version of the SNMP message protocol is called SNMPv1 and 79 described in STD 15, RFC 1157 [RFC1157]. A second version of 80 the SNMP message protocol, which is not an Internet standards 81 track protocol, is called SNMPv2c and described in RFC 1901 82 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 83 message protocol is called SNMPv3 and described in RFC 1906 84 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 86 o Protocol operations for accessing management information. The 87 first set of protocol operations and associated PDU formats is 88 described in STD 15, RFC 1157 [RFC1157]. A second set of 89 protocol operations and associated PDU formats is described in 90 RFC 1905 [RFC1905]. 92 o A set of fundamental applications described in RFC 2573 93 [RFC2573] and the view-based access control mechanism described 94 in RFC 2575 [RFC2575]. 96 A more detailed introduction to the current SNMP Management Framework 97 can be found in RFC 2570 [RFC2570]. 99 Managed objects are accessed via a virtual information store, termed 100 the Management Information Base or MIB. Objects in the MIB are 101 defined using the mechanisms defined in the SMI. 103 This memo specifies a MIB module that is compliant to the SMIv2. A 104 MIB conforming to the SMIv1 can be produced through the appropriate 105 translations. The resulting translated MIB must be semantically 106 equivalent, except where objects or events are omitted because no 107 translation is possible (use of Counter64). Some machine readable 108 information in SMIv2 will be converted into textual descriptions in 109 SMIv1 during the translation process. However, this loss of machine 110 readable information is not considered to change the semantics of the 111 MIB. 113 2. Overview 115 A common device present in many networks is the Bridge. This device 116 is used to connect Local Area Network segments below the network 117 layer. 119 There are two major modes defined for this bridging; transparent and 120 source route. The transparent method of bridging is defined in the 121 IEEE 802.1D specification [IEEE8021D]. This memo defines those 122 objects needed for the management of a bridging entity operating in 123 the transparent mode, as well as some objects applicable to all types 124 of bridges. 126 To be consistent with IAB directives and good engineering practice, 127 an explicit attempt was made to keep this MIB as simple as possible. 128 This was accomplished by applying the following criteria to objects 129 proposed for inclusion: 131 (1) Start with a small set of essential objects and add only as 132 further objects are needed. 134 (2) Require objects be essential for either fault or configuration 135 management. 137 (3) Consider evidence of current use and/or utility. 139 (4) Limit the total of objects. 141 (5) Exclude objects which are simply derivable from others in this 142 or other MIBs. 144 (6) Avoid causing critical sections to be heavily instrumented. The 145 guideline that was followed is one counter per critical section 146 per layer. 148 2.1. Structure of MIB 150 Objects in this MIB are arranged into groups. Each group is 151 organized as a set of related objects. The overall structure and 152 assignment of objects to their groups is shown below. Where 153 appropriate the corresponding IEEE 802.1D [IEEE8021D] management 154 object name is also included. 156 Bridge MIB Name IEEE 802.1D Name 158 dot1dBridge 159 dot1dBase 160 BridgeAddress Bridge.BridgeAddress 161 NumPorts Bridge.NumberOfPorts 162 Type 163 PortTable 164 Port BridgePort.PortNumber 165 IfIndex 166 Circuit 167 DelayExceededDiscards .DiscardTransitDelay 168 MtuExceededDiscards .DiscardOnError 169 dot1dStp 170 ProtocolSpecification 171 Priority SpanningTreeProtocol 172 .BridgePriority 173 TimeSinceTopologyChange .TimeSinceTopologyChange 174 TopChanges .TopologyChangeCount 175 DesignatedRoot .DesignatedRoot 176 RootCost .RootCost 177 RootPort .RootPort 178 MaxAge .MaxAge 179 HelloTime .HelloTime 180 HoldTime .HoldTime 181 ForwardDelay .ForwardDelay 182 BridgeMaxAge .BridgeMaxAge 183 BridgeHelloTime .BridgeHelloTime 184 BridgeForwardDelay .BridgeForwardDelay 185 PortTable 186 Port SpanningTreeProtocolPort 187 .PortNumber 188 Priority .PortPriority 189 State .SpanningTreeState 190 Enable 191 PathCost .PortPathCost 192 DesignatedRoot .DesignatedRoot 193 DesignatedCost .DesignatedCost 194 DesignatedBridge .DesignatedBridge 195 DesignatedPort .DesignatedPort 196 ForwardTransitions 197 dot1dTp 198 LearnedEntryDiscards BridgeFilter.DatabaseSize 199 .NumDynamic,NumStatic 200 AgingTime BridgeFilter.AgingTime 201 FdbTable 202 Address 203 Port 204 Status 205 PortTable 206 Port 207 MaxInfo 208 InFrames BridgePort.FramesReceived 209 OutFrames .ForwardOutbound 210 InDiscards .DiscardInbound 211 dot1dStatic 212 StaticTable 213 Address 214 ReceivePort 215 AllowedToGoTo 216 Status 218 The following IEEE 802.1D management objects have not been included 219 in the Bridge MIB for the indicated reasons. 221 IEEE 802.1D Object Disposition 223 Bridge.BridgeName Same as sysDescr (MIB II) 224 Bridge.BridgeUpTime Same as sysUpTime (MIB II) 225 Bridge.PortAddresses Same as ifPhysAddress (MIB II) 226 BridgePort.PortName Same as ifDescr (MIB II) 227 BridgePort.PortType Same as ifType (MIB II) 228 BridgePort.RoutingType Derivable from the implemented 229 groups 231 SpanningTreeProtocol 232 .BridgeIdentifier Combination of dot1dStpPriority 233 and dot1dBaseBridgeAddress 234 .TopologyChange Since this is transitory, it 235 is not considered useful. 236 SpanningTreeProtocolPort 237 .Uptime Same as ifLastChange (MIB II) 238 .PortIdentifier Combination of dot1dStpPort 239 and dot1dStpPortPriority 240 .TopologyChangeAcknowledged Since this is transitory, it 241 is not considered useful. 242 .DiscardLackOfBuffers Redundant 244 Transmission Priority These objects are not required 245 as per the Pics Proforma and 246 not considered useful. 247 .TransmissionPriorityName 248 .OutboundUserPriority 249 .OutboundAccessPriority 251 2.1.1. The dot1dBase Group 253 This mandatory group contains the objects which are applicable to all 254 types of bridges. 256 2.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 260 implemented the Spanning Tree Protocol, this group will not be 261 implemented. 263 2.1.3. The dot1dSr Group 264 This group contains the objects that describe the entity's state with 265 respect to source route bridging. If source routing is not supported 266 this group will not be implemented. This group is applicable to 267 source route only, and SRT bridges. This group will be described in 268 a separate document applicable only to source route bridging. 270 2.1.4. The dot1dTp Group 272 This group contains objects that describe the entity's state with 273 respect to transparent bridging. If transparent bridging is not 274 supported this group will not be implemented. This group is 275 applicable to transparent only and SRT bridges. 277 2.1.5. The dot1dStatic Group 279 This group contains objects that describe the entity's state with 280 respect to destination-address filtering. If destination-address 281 filtering is not supported this group will not be implemented. This 282 group is applicable to any type of bridge which performs destination- 283 address filtering. 285 2.2. Relationship to Other MIBs 287 As described above, some IEEE 802.1D management objects have not been 288 included in this MIB because they overlap with objects in other MIBs 289 applicable to a bridge implementing this MIB. In particular, it is 290 assumed that a bridge implementing this MIB will also implement (at 291 least) the 'system' group and the 'interfaces' group defined in MIB- 292 II [RFC1213]. 294 2.2.1. Relationship to the 'system' group 296 In MIB-II [RFC1907], the 'system' group is defined as being mandatory 297 for all systems such that each managed entity contains one instance 298 of each object in the 'system' group. Thus, those objects apply to 299 the entity as a whole irrespective of whether the entity's sole 300 functionality is bridging, or whether bridging is only a subset of 301 the entity's functionality. 303 2.2.2. Relationship to the 'interfaces' group 305 In the Interfaces Group MIB [RFC2863], the 'interfaces' group is 306 defined as being mandatory for all systems and contains information 307 on an entity's interfaces, where each interface is thought of as 308 being attached to a `subnetwork'. (Note that this term is not to be 309 confused with `subnet' which refers to an addressing partitioning 310 scheme used in the Internet suite of protocols.) The term 'segment' 311 is used in this memo to refer to such a subnetwork, whether it be an 312 Ethernet segment, a 'ring', a WAN link, or even an X.25 virtual 313 circuit. 315 Implicit in this Bridge MIB is the notion of ports on a bridge. Each 316 of these ports is associated with one interface of the 'interfaces' 317 group, and in most situations, each port is associated with a 318 different interface. However, there are situations in which multiple 319 ports are associated with the same interface. An example of such a 320 situation would be several ports each corresponding one-to-one with 321 several X.25 virtual circuits but all on the same interface. 323 Each port is uniquely identified by a port number. A port number has 324 no mandatory relationship to an interface number, but in the simple 325 case a port number will have the same value as the corresponding 326 interface's interface number. Port numbers are in the range 327 (1..dot1dBaseNumPorts). 329 Some entities perform other functionality as well as bridging through 330 the sending and receiving of data on their interfaces. In such 331 situations, only a subset of the data sent/received on an interface 332 is within the domain of the entity's bridging functionality. This 333 subset is considered to be delineated according to a set of 334 protocols, with some protocols being bridged, and other protocols not 335 being bridged. For example, in an entity which exclusively performed 336 bridging, all protocols would be considered as being bridged, whereas 337 in an entity which performed IP routing on IP datagrams and only 338 bridged other protocols, only the non-IP data would be considered as 339 being bridged. 341 Thus, this Bridge MIB (and in particular, its counters) are 342 applicable only to that subset of the data on an entity's interfaces 343 which is sent/received for a protocol being bridged. All such data 344 is sent/received via the ports of the bridge. 346 2.3. Textual Conventions 348 The datatypes, MacAddress, BridgeId and Timeout, are used as textual 349 conventions in this document. Objects defined using these 350 conventions are always encoded by means of the rules that define 351 their primitive type. Hence, no changes to the SMI or the SNMP are 352 necessary to accommodate these textual conventions which are adopted 353 merely for the convenience of readers. 355 3. Definitions 357 BRIDGE-MIB DEFINITIONS ::= BEGIN 359 -- ---------------------------------------------------------- -- 360 -- MIB for IEEE 802.1D devices 361 -- ---------------------------------------------------------- -- 362 IMPORTS 363 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 364 Counter32, Integer32, TimeTicks, mib-2 365 FROM SNMPv2-SMI 366 TEXTUAL-CONVENTION, MacAddress 367 FROM SNMPv2-TC 368 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 369 FROM SNMPv2-CONF 370 InterfaceIndex FROM IF-MIB 371 ; 373 bridgeMIB MODULE-IDENTITY 374 LAST-UPDATED "200201310000Z" 375 ORGANIZATION "IETF Bridge MIB Working Group" 376 CONTACT-INFO 377 "Email: Bridge-mib@ietf.org" 378 DESCRIPTION 379 "The Bridge MIB module for managing devices that support 380 IEEE 802.1D." 381 REVISION "200106260000Z" 382 DESCRIPTION 383 "Translation of RFC 1493 to SMIv2." 384 REVISION "199307310000Z" 385 DESCRIPTION 386 "RFC 1493: SMIv1 version." 387 ::= { dot1dBridge 8 } 389 dot1dNotification OBJECT IDENTIFIER ::= { dot1dBridge 0 } 391 -- ---------------------------------------------------------- -- 392 -- Textual Conventions 393 -- ---------------------------------------------------------- -- 395 -- All representations of MAC addresses in this MIB Module use, 396 -- as a textual convention (i.e. this convention does not affect 397 -- their encoding), the data type MacAddress, defined in 398 -- SNMPv2-TC. 400 -- Similarly, all representations of Bridge-Id in this MIB 401 -- Module use, as a textual convention (i.e. this convention 402 -- does not affect their encoding), the data type: 404 BridgeId ::= TEXTUAL-CONVENTION 405 STATUS current 406 DESCRIPTION 407 "The Bridge-Identifier as used in the Spanning Tree 408 Protocol to uniquely identify a bridge. Its first two 409 octets (in network byte order) contain a priority value 410 and its last 6 octets contain the MAC address used to 411 refer to a bridge in a unique fashion (typically, the 412 numerically smallest MAC address of all ports on the 413 bridge)." 414 SYNTAX OCTET STRING (SIZE (8)) 416 -- Several objects in this MIB module represent values of timers 417 -- used by the Spanning Tree Protocol. In this MIB, these 418 -- timers have values in units of hundreths of a second (i.e. 419 -- 1/100 secs). 420 -- These timers, when stored in a Spanning Tree Protocol's BPDU, 421 -- are in units of 1/256 seconds. Note, however, that 422 -- 802.1D-1990 specifies a settable granularity of no more 423 -- than 1 second for these timers. To avoid ambiguity, a data 424 -- type is defined here as a textual convention and all 425 -- representation of these timers in this MIB module are defined 426 -- using this data type. An algorithm is also defined for 427 -- converting between the different units, to ensure a timer's 428 -- value is not distorted by multiple conversions. 429 -- The data type is: 431 Timeout ::= TEXTUAL-CONVENTION 432 STATUS current 433 DESCRIPTION 434 "A STP timer in units of 1/100 seconds. 435 To convert a Timeout value into a value in units of 436 1/256 seconds, the following algorithm should be used: 438 b = floor( (n * 256) / 100) 440 where: 441 floor = quotient [ignore remainder] 442 n is the value in 1/100 second units 443 b is the value in 1/256 second units 445 To convert the value from 1/256 second units back to 446 1/100 seconds, the following algorithm should be used: 448 n = ceiling( (b * 100) / 256) 450 where: 451 ceiling = quotient [if remainder is 0], or 452 quotient + 1 [if remainder is non-zero] 453 n is the value in 1/100 second units 454 b is the value in 1/256 second units 456 Note: it is important that the arithmetic operations are 457 done in the order specified (i.e., multiply first, 458 divide second)." 459 SYNTAX Integer32 461 -- ---------------------------------------------------------- -- 463 dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 } 465 -- ---------------------------------------------------------- -- 466 -- groups in the Bridge MIB 467 -- ---------------------------------------------------------- -- 469 dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 } 470 dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 } 472 dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 } 473 -- separately documented 475 dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 } 476 dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 } 478 -- Groups defined in the Bridge Mib Extensions: 480 -- pBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 6 } 481 -- qBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 7 } 483 -- The MODULE-IDENTITY for this MIB has been defined above as: 484 -- bridgeMIB MODULE-IDENTITY ::= { dot1dBridge 8 } 486 -- The MODULE-IDENTITY for the Source Routing MIB has been 487 -- defined in that MIB as: 488 -- srMIB MODULE-IDENTITY ::= { dot1dBridge 9 } 490 -- Groups defined in the Source Routing MIB: 491 -- dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 } 493 dot1dConformance OBJECT IDENTIFIER ::= { bridgeMIB 1 } 495 -- ---------------------------------------------------------- -- 496 -- the dot1dBase group 497 -- ---------------------------------------------------------- -- 498 -- Implementation of the dot1dBase group is mandatory for all 499 -- bridges. 500 -- ---------------------------------------------------------- -- 502 dot1dBaseBridgeAddress OBJECT-TYPE 503 SYNTAX MacAddress 504 MAX-ACCESS read-only 505 STATUS current 506 DESCRIPTION 507 "The MAC address used by this bridge when it must be 508 referred to in a unique fashion. It is recommended 509 that this be the numerically smallest MAC address of all 510 ports that belong to this bridge. However it is only 511 required to be unique. When concatenated with 512 dot1dStpPriority a unique BridgeIdentifier is formed 513 which is used in the Spanning Tree Protocol." 514 REFERENCE 515 "IEEE 802.1D-1990: Sections 6.4.1.1.3 and 3.12.5" 516 ::= { dot1dBase 1 } 518 dot1dBaseNumPorts OBJECT-TYPE 519 SYNTAX Integer32 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "The number of ports controlled by this bridging 524 entity." 525 REFERENCE 526 "IEEE 802.1D-1990: Section 6.4.1.1.3" 527 ::= { dot1dBase 2 } 529 dot1dBaseType OBJECT-TYPE 530 SYNTAX INTEGER { 531 unknown(1), 532 transparentOnly(2), 533 sourcerouteOnly(3), 534 srt(4) 535 } 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "Indicates what type of bridging this bridge can 540 perform. If a bridge is actually performing a 541 certain type of bridging this will be indicated by 542 entries in the port table for the given type." 543 ::= { dot1dBase 3 } 545 -- ---------------------------------------------------------- -- 546 -- The Generic Bridge Port Table 547 -- ---------------------------------------------------------- -- 548 dot1dBasePortTable OBJECT-TYPE 549 SYNTAX SEQUENCE OF Dot1dBasePortEntry 550 MAX-ACCESS not-accessible 551 STATUS current 552 DESCRIPTION 553 "A table that contains generic information about every 554 port that is associated with this bridge. Transparent, 555 source-route, and srt ports are included." 557 ::= { dot1dBase 4 } 559 dot1dBasePortEntry OBJECT-TYPE 560 SYNTAX Dot1dBasePortEntry 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "A list of information for each port of the bridge." 565 REFERENCE 566 "IEEE 802.1D-1990: Section 6.4.2, 6.6.1" 567 INDEX { dot1dBasePort } 568 ::= { dot1dBasePortTable 1 } 570 Dot1dBasePortEntry ::= 571 SEQUENCE { 572 dot1dBasePort 573 Integer32, 574 dot1dBasePortIfIndex 575 InterfaceIndex, 576 dot1dBasePortCircuit 577 OBJECT IDENTIFIER, 578 dot1dBasePortDelayExceededDiscards 579 Counter32, 580 dot1dBasePortMtuExceededDiscards 581 Counter32 582 } 584 dot1dBasePort OBJECT-TYPE 585 SYNTAX Integer32 (1..65535) 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "The port number of the port for which this entry 590 contains bridge management information." 591 ::= { dot1dBasePortEntry 1 } 593 dot1dBasePortIfIndex OBJECT-TYPE 594 SYNTAX InterfaceIndex 595 MAX-ACCESS read-only 596 STATUS current 597 DESCRIPTION 598 "The value of the instance of the ifIndex object, 599 defined in IF-MIB, for the interface corresponding 600 to this port." 601 ::= { dot1dBasePortEntry 2 } 603 dot1dBasePortCircuit OBJECT-TYPE 604 SYNTAX OBJECT IDENTIFIER 605 MAX-ACCESS read-only 606 STATUS current 608 DESCRIPTION 609 "For a port which (potentially) has the same value of 610 dot1dBasePortIfIndex as another port on the same bridge, 611 this object contains the name of an object instance 612 unique to this port. For example, in the case where 613 multiple ports correspond one- to-one with multiple X.25 614 virtual circuits, this value might identify an (e.g., 615 the first) object instance associated with the X.25 616 virtual circuit corresponding to this port. 618 For a port which has a unique value of 619 dot1dBasePortIfIndex, this object can have the value 620 { 0 0 }." 621 ::= { dot1dBasePortEntry 3 } 623 dot1dBasePortDelayExceededDiscards OBJECT-TYPE 624 SYNTAX Counter32 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "The number of frames discarded by this port due 629 to excessive transit delay through the bridge. It 630 is incremented by both transparent and source 631 route bridges." 632 REFERENCE 633 "IEEE 802.1D-1990: Section 6.6.1.1.3" 634 ::= { dot1dBasePortEntry 4 } 636 dot1dBasePortMtuExceededDiscards OBJECT-TYPE 637 SYNTAX Counter32 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "The number of frames discarded by this port due 643 to an excessive size. It is incremented by both 644 transparent and source route bridges." 645 REFERENCE 646 "IEEE 802.1D-1990: Section 6.6.1.1.3" 647 ::= { dot1dBasePortEntry 5 } 649 -- ---------------------------------------------------------- -- 650 -- the dot1dStp group 651 -- ---------------------------------------------------------- -- 652 -- Implementation of the dot1dStp group is optional. It is 653 -- implemented by those bridges that support the Spanning Tree 654 -- Protocol. 655 -- ---------------------------------------------------------- -- 657 dot1dStpProtocolSpecification OBJECT-TYPE 658 SYNTAX INTEGER { 659 unknown(1), 660 decLb100(2), 661 ieee8021d(3) 662 } 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "An indication of what version of the Spanning Tree 667 Protocol is being run. The value 'decLb100(2)' 668 indicates the DEC LANbridge 100 Spanning Tree protocol. 669 IEEE 802.1D implementations will return 'ieee8021d(3)'. 670 If future versions of the IEEE Spanning Tree Protocol 671 are released that are incompatible with the current 672 version a new value will be defined." 673 ::= { dot1dStp 1 } 675 dot1dStpPriority OBJECT-TYPE 676 SYNTAX Integer32 (0..65535) 677 MAX-ACCESS read-write 678 STATUS current 679 DESCRIPTION 680 "The value of the write-able portion of the Bridge ID, 681 i.e., the first two octets of the (8 octet long) Bridge 682 ID. The other (last) 6 octets of the Bridge ID are 683 given by the value of dot1dBaseBridgeAddress. 684 Permissible values are 0-61440, in steps of 4096." 685 REFERENCE 686 " IEEE 802.1t clause 8.10.2, Table 8-4, clause 14.3." 687 ::= { dot1dStp 2 } 689 dot1dStpTimeSinceTopologyChange OBJECT-TYPE 690 SYNTAX TimeTicks 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "The time (in hundredths of a second) since the 695 last time a topology change was detected by the 696 bridge entity. 697 For RSTP, this reports the time since the tcWhile timer for 698 any port on this Bridge was non-zero." 699 REFERENCE 700 " IEEE 802.1w clause 14.8.1.1." 701 ::= { dot1dStp 3 } 703 dot1dStpTopChanges OBJECT-TYPE 704 SYNTAX Counter32 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "The total number of topology changes detected by 709 this bridge since the management entity was last 710 reset or initialized." 711 REFERENCE 712 " IEEE 802.1w clause 14.8.1.1." 713 ::= { dot1dStp 4 } 715 dot1dStpDesignatedRoot OBJECT-TYPE 716 SYNTAX BridgeId 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "The bridge identifier of the root of the spanning 721 tree as determined by the Spanning Tree Protocol 722 as executed by this node. This value is used as 723 the Root Identifier parameter in all Configuration 724 Bridge PDUs originated by this node." 725 REFERENCE 726 "IEEE 802.1D-1990: Section 4.5.3.1" 727 ::= { dot1dStp 5 } 729 dot1dStpRootCost OBJECT-TYPE 730 SYNTAX Integer32 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "The cost of the path to the root as seen from 735 this bridge." 736 REFERENCE 737 "IEEE 802.1D-1990: Section 4.5.3.2" 738 ::= { dot1dStp 6 } 740 dot1dStpRootPort OBJECT-TYPE 741 SYNTAX Integer32 742 MAX-ACCESS read-only 743 STATUS current 744 DESCRIPTION 745 "The port number of the port which offers the lowest 746 cost path from this bridge to the root bridge." 748 REFERENCE 749 "IEEE 802.1D-1990: Section 4.5.3.3" 750 ::= { dot1dStp 7 } 752 dot1dStpMaxAge OBJECT-TYPE 753 SYNTAX Timeout 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The maximum age of Spanning Tree Protocol information 758 learned from the network on any port before it is 759 discarded, in units of hundredths of a second. This is 760 the actual value that this bridge is currently using." 761 REFERENCE 762 "IEEE 802.1D-1990: Section 4.5.3.4" 763 ::= { dot1dStp 8 } 765 dot1dStpHelloTime OBJECT-TYPE 766 SYNTAX Timeout 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "The amount of time between the transmission of 771 Configuration bridge PDUs by this node on any port when 772 it is the root of the spanning tree or trying to become 773 so, in units of hundredths of a second. This is the 774 actual value that this bridge is currently using." 775 REFERENCE 776 "IEEE 802.1D-1990: Section 4.5.3.5" 777 ::= { dot1dStp 9 } 779 dot1dStpHoldTime OBJECT-TYPE 780 SYNTAX Integer32 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "This time value determines the interval length 785 during which no more than two Configuration bridge 786 PDUs shall be transmitted by this node, in units 787 of hundredths of a second." 788 REFERENCE 789 "IEEE 802.1D-1990: Section 4.5.3.14" 790 ::= { dot1dStp 10 } 792 dot1dStpForwardDelay OBJECT-TYPE 793 SYNTAX Timeout 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION 797 "This time value, measured in units of hundredths of a 798 second, controls how fast a port changes its spanning 799 state when moving towards the Forwarding state. The 800 value determines how long the port stays in each of the 801 Listening and Learning states, which precede the 802 Forwarding state. This value is also used, when a 803 topology change has been detected and is underway, to 804 age all dynamic entries in the Forwarding Database. 805 [Note that this value is the one that this bridge is 806 currently using, in contrast to 807 dot1dStpBridgeForwardDelay which is the value that this 808 bridge and all others would start using if/when this 809 bridge were to become the root.]" 810 REFERENCE 811 "IEEE 802.1D-1990: Section 4.5.3.6" 812 ::= { dot1dStp 11 } 814 dot1dStpBridgeMaxAge OBJECT-TYPE 815 SYNTAX Timeout (600..4000) 816 MAX-ACCESS read-write 817 STATUS current 818 DESCRIPTION 819 "The value that all bridges use for MaxAge when this 820 bridge is acting as the root. Note that 802.1D-1990 821 specifies that the range for this parameter is related 822 to the value of dot1dStpBridgeHelloTime. The 823 granularity of this timer is specified by 802.1D-1990 to 824 be 1 second. An agent may return a badValue error if a 825 set is attempted to a value which is not a whole number 826 of seconds." 827 REFERENCE 828 "IEEE 802.1D-1990: Section 4.5.3.8" 829 ::= { dot1dStp 12 } 831 dot1dStpBridgeHelloTime OBJECT-TYPE 832 SYNTAX Timeout (100..1000) 833 MAX-ACCESS read-write 834 STATUS current 835 DESCRIPTION 836 "The value that all bridges use for HelloTime when this 837 bridge is acting as the root. The granularity of this 838 timer is specified by 802.1D- 1990 to be 1 second. An 839 agent may return a badValue error if a set is attempted 840 to a value which is not a whole number of seconds." 841 REFERENCE 842 "IEEE 802.1D-1990: Section 4.5.3.9" 843 ::= { dot1dStp 13 } 845 dot1dStpBridgeForwardDelay OBJECT-TYPE 846 SYNTAX Timeout (400..3000) 847 MAX-ACCESS read-write 848 STATUS current 849 DESCRIPTION 850 "The value that all bridges use for ForwardDelay when 851 this bridge is acting as the root. Note that 852 802.1D-1990 specifies that the range for this parameter 853 is related to the value of dot1dStpBridgeMaxAge. The 854 granularity of this timer is specified by 802.1D-1990 to 855 be 1 second. An agent may return a badValue error if a 856 set is attempted to a value which is not a whole number 857 of seconds." 858 REFERENCE 859 "IEEE 802.1D-1990: Section 4.5.3.10" 860 ::= { dot1dStp 14 } 862 -- ---------------------------------------------------------- -- 863 -- The Spanning Tree Port Table 864 -- ---------------------------------------------------------- -- 866 dot1dStpPortTable OBJECT-TYPE 867 SYNTAX SEQUENCE OF Dot1dStpPortEntry 868 MAX-ACCESS not-accessible 869 STATUS current 870 DESCRIPTION 871 "A table that contains port-specific information 872 for the Spanning Tree Protocol." 873 ::= { dot1dStp 15 } 875 dot1dStpPortEntry OBJECT-TYPE 876 SYNTAX Dot1dStpPortEntry 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "A list of information maintained by every port about 881 the Spanning Tree Protocol state for that port." 882 INDEX { dot1dStpPort } 883 ::= { dot1dStpPortTable 1 } 885 Dot1dStpPortEntry ::= 886 SEQUENCE { 887 dot1dStpPort 888 Integer32, 889 dot1dStpPortPriority 890 Integer32, 891 dot1dStpPortState 892 INTEGER, 893 dot1dStpPortEnable 894 INTEGER, 895 dot1dStpPortPathCost 896 INTEGER, 897 dot1dStpPortDesignatedRoot 898 BridgeId, 899 dot1dStpPortDesignatedCost 900 Integer32, 901 dot1dStpPortDesignatedBridge 902 BridgeId, 903 dot1dStpPortDesignatedPort 904 OCTET STRING, 905 dot1dStpPortForwardTransitions 906 Counter32, 907 dot1dStpPortPathCost32 908 Integer32 909 } 911 dot1dStpPort OBJECT-TYPE 912 SYNTAX Integer32 (1..65535) 913 MAX-ACCESS not-accessible 914 STATUS current 915 DESCRIPTION 916 "The port number of the port for which this entry 917 contains Spanning Tree Protocol management information." 918 REFERENCE 919 "IEEE 802.1D-1990: Section 6.8.2.1.2" 920 ::= { dot1dStpPortEntry 1 } 922 dot1dStpPortPriority OBJECT-TYPE 923 SYNTAX Integer32 (0.. 255) 925 MAX-ACCESS read-write 926 STATUS current 927 DESCRIPTION 928 "The value of the priority field which is contained in 929 the first (in network byte order) octet of the (2 octet 930 long) Port ID. The other octet of the Port ID is given 931 by the value of dot1dStpPort. 933 On newer bridges, permissible values are 934 0-240, in steps of 16." 935 REFERENCE 936 " IEEE 802.1t clause 8.10.2, Table 8-4, clause 14.3." 937 ::= { dot1dStpPortEntry 2 } 939 dot1dStpPortState OBJECT-TYPE 940 SYNTAX INTEGER { 941 disabled(1), 942 blocking(2), 943 listening(3), 944 learning(4), 945 forwarding(5), 946 broken(6) 947 } 948 MAX-ACCESS read-only 949 STATUS current 950 DESCRIPTION 951 "The port's current state as defined by application of 952 the Spanning Tree Protocol. This state controls what 953 action a port takes on reception of a frame. If the 954 bridge has detected a port that is malfunctioning it 955 will place that port into the broken(6) state. For 956 ports which are disabled (see dot1dStpPortEnable), this 957 object will have a value of disabled(1)." 958 REFERENCE 959 "IEEE 802.1D-1990: Section 4.5.5.2" 960 ::= { dot1dStpPortEntry 3 } 962 dot1dStpPortEnable OBJECT-TYPE 963 SYNTAX INTEGER { 964 enabled(1), 965 disabled(2) 966 } 967 MAX-ACCESS read-write 968 STATUS current 969 DESCRIPTION 970 "The enabled/disabled status of the port." 971 REFERENCE 972 "IEEE 802.1D-1990: Section 4.5.5.2" 973 ::= { dot1dStpPortEntry 4 } 975 dot1dStpPortPathCost OBJECT-TYPE 976 SYNTAX INTEGER (1..65535) 977 MAX-ACCESS read-write 978 STATUS deprecated 979 DESCRIPTION 980 "The contribution of this port to the path cost of 981 paths towards the spanning tree root which include 982 this port. 802.1D-1990 recommends that the 983 default value of this parameter be in inverse 984 proportion to the speed of the attached LAN. 986 New implementations should use dot1dStpPortPathCost32" 987 REFERENCE 988 "IEEE 802.1D-1990: Section 4.5.5.3" 989 ::= { dot1dStpPortEntry 5 } 991 dot1dStpPortDesignatedRoot OBJECT-TYPE 992 SYNTAX BridgeId 993 MAX-ACCESS read-only 994 STATUS current 995 DESCRIPTION 996 "The unique Bridge Identifier of the Bridge 997 recorded as the Root in the Configuration BPDUs 998 transmitted by the Designated Bridge for the 999 segment to which the port is attached." 1000 REFERENCE 1001 "IEEE 802.1D-1990: Section 4.5.5.4" 1002 ::= { dot1dStpPortEntry 6 } 1004 dot1dStpPortDesignatedCost OBJECT-TYPE 1005 SYNTAX Integer32 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The path cost of the Designated Port of the segment 1010 connected to this port. This value is compared to the 1011 Root Path Cost field in received bridge PDUs." 1012 REFERENCE 1013 "IEEE 802.1D-1990: Section 4.5.5.5" 1014 ::= { dot1dStpPortEntry 7 } 1016 dot1dStpPortDesignatedBridge OBJECT-TYPE 1017 SYNTAX BridgeId 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "The Bridge Identifier of the bridge which this 1022 port considers to be the Designated Bridge for 1023 this port's segment." 1024 REFERENCE 1025 "IEEE 802.1D-1990: Section 4.5.5.6" 1026 ::= { dot1dStpPortEntry 8 } 1028 dot1dStpPortDesignatedPort OBJECT-TYPE 1029 SYNTAX OCTET STRING (SIZE (2)) 1030 MAX-ACCESS read-only 1031 STATUS current 1032 DESCRIPTION 1033 "The Port Identifier of the port on the Designated 1034 Bridge for this port's segment." 1035 REFERENCE 1036 "IEEE 802.1D-1990: Section 4.5.5.7" 1037 ::= { dot1dStpPortEntry 9 } 1039 dot1dStpPortForwardTransitions OBJECT-TYPE 1040 SYNTAX Counter32 1041 MAX-ACCESS read-only 1042 STATUS current 1043 DESCRIPTION 1044 "The number of times this port has transitioned 1045 from the Learning state to the Forwarding state." 1046 ::= { dot1dStpPortEntry 10 } 1048 dot1dStpPortPathCost32 OBJECT-TYPE 1049 SYNTAX Integer32 (1..200000000) 1050 MAX-ACCESS read-write 1051 STATUS current 1052 DESCRIPTION 1053 "The contribution of this port to the path cost of 1054 paths towards the spanning tree root which include 1055 this port. 802.1D-1990 recommends that the 1056 default value of this parameter be in inverse 1057 proportion to the speed of the attached LAN. 1058 The permissible values must be extended to 1-200,000,000. 1060 Replacement for deprecated object dot1dStpPortPathCost" 1061 REFERENCE 1062 " IEEE 802.1t clause 8.10.2, Table 8-5." 1063 ::= { dot1dStpPortEntry 11 } 1065 -- ---------------------------------------------------------- -- 1066 -- the dot1dTp group 1067 -- ---------------------------------------------------------- -- 1068 -- Implementation of the dot1dTp group is optional. It is 1069 -- implemented by those bridges that support the transparent 1070 -- bridging mode. A transparent or SRT bridge will implement 1071 -- this group. 1072 -- ---------------------------------------------------------- -- 1074 dot1dTpLearnedEntryDiscards OBJECT-TYPE 1075 SYNTAX Counter32 1076 MAX-ACCESS read-only 1077 STATUS current 1078 DESCRIPTION 1079 "The total number of Forwarding Database entries, which 1080 have been or would have been learnt, but have been 1081 discarded due to a lack of space to store them in the 1082 Forwarding Database. If this counter is increasing, it 1083 indicates that the Forwarding Database is regularly 1084 becoming full (a condition which has unpleasant 1085 performance effects on the subnetwork). If this counter 1086 has a significant value but is not presently increasing, 1087 it indicates that the problem has been occurring but is 1088 not persistent." 1089 REFERENCE 1090 "IEEE 802.1D-1990: Section 6.7.1.1.3" 1091 ::= { dot1dTp 1 } 1093 dot1dTpAgingTime OBJECT-TYPE 1094 SYNTAX Integer32 (10..1000000) 1095 MAX-ACCESS read-write 1096 STATUS current 1097 DESCRIPTION 1098 "The timeout period in seconds for aging out 1099 dynamically learned forwarding information. 1100 802.1D-1990 recommends a default of 300 seconds." 1101 REFERENCE 1102 "IEEE 802.1D-1990: Section 6.7.1.1.3" 1103 ::= { dot1dTp 2 } 1105 -- ---------------------------------------------------------- -- 1106 -- The Forwarding Database for Transparent Bridges 1107 -- ---------------------------------------------------------- -- 1109 dot1dTpFdbTable OBJECT-TYPE 1110 SYNTAX SEQUENCE OF Dot1dTpFdbEntry 1111 MAX-ACCESS not-accessible 1112 STATUS current 1113 DESCRIPTION 1114 "A table that contains information about unicast 1115 entries for which the bridge has forwarding and/or 1116 filtering information. This information is used 1117 by the transparent bridging function in 1119 determining how to propagate a received frame." 1120 ::= { dot1dTp 3 } 1122 dot1dTpFdbEntry OBJECT-TYPE 1123 SYNTAX Dot1dTpFdbEntry 1124 MAX-ACCESS not-accessible 1125 STATUS current 1126 DESCRIPTION 1127 "Information about a specific unicast MAC address 1128 for which the bridge has some forwarding and/or 1129 filtering information." 1130 INDEX { dot1dTpFdbAddress } 1131 ::= { dot1dTpFdbTable 1 } 1133 Dot1dTpFdbEntry ::= 1134 SEQUENCE { 1135 dot1dTpFdbAddress 1136 MacAddress, 1137 dot1dTpFdbPort 1138 Integer32, 1139 dot1dTpFdbStatus 1140 INTEGER 1141 } 1143 dot1dTpFdbAddress OBJECT-TYPE 1144 SYNTAX MacAddress 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "A unicast MAC address for which the bridge has 1149 forwarding and/or filtering information." 1150 REFERENCE 1151 "IEEE 802.1D-1990: Section 3.9.1, 3.9.2" 1152 ::= { dot1dTpFdbEntry 1 } 1154 dot1dTpFdbPort OBJECT-TYPE 1155 SYNTAX Integer32 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "Either the value '0', or the port number of the port on 1160 which a frame having a source address equal to the value 1161 of the corresponding instance of dot1dTpFdbAddress has 1162 been seen. A value of '0' indicates that the port 1163 number has not been learned but that the bridge does 1164 have some forwarding/filtering information about this 1165 address (e.g. in the dot1dStaticTable). Implementors 1166 are encouraged to assign the port value to this object 1167 whenever it is learned even for addresses for which the 1168 corresponding value of dot1dTpFdbStatus is not 1169 learned(3)." 1170 ::= { dot1dTpFdbEntry 2 } 1172 dot1dTpFdbStatus OBJECT-TYPE 1173 SYNTAX INTEGER { 1174 other(1), 1175 invalid(2), 1176 learned(3), 1177 self(4), 1178 mgmt(5) 1180 } 1181 MAX-ACCESS read-only 1182 STATUS current 1183 DESCRIPTION 1184 "The status of this entry. The meanings of the 1185 values are: 1186 other(1) - none of the following. This would 1187 include the case where some other MIB object 1188 (not the corresponding instance of 1189 dot1dTpFdbPort, nor an entry in the 1190 dot1dStaticTable) is being used to determine if 1191 and how frames addressed to the value of the 1192 corresponding instance of dot1dTpFdbAddress are 1193 being forwarded. 1194 invalid(2) - this entry is not longer valid (e.g., 1195 it was learned but has since aged-out), but has 1196 not yet been flushed from the table. 1197 learned(3) - the value of the corresponding instance 1198 of dot1dTpFdbPort was learned, and is being 1199 used. 1200 self(4) - the value of the corresponding instance of 1201 dot1dTpFdbAddress represents one of the bridge's 1202 addresses. The corresponding instance of 1203 dot1dTpFdbPort indicates which of the bridge's 1204 ports has this address. 1205 mgmt(5) - the value of the corresponding instance of 1206 dot1dTpFdbAddress is also the value of an 1207 existing instance of dot1dStaticAddress." 1208 ::= { dot1dTpFdbEntry 3 } 1210 -- ---------------------------------------------------------- -- 1211 -- Port Table for Transparent Bridges 1212 -- ---------------------------------------------------------- -- 1214 dot1dTpPortTable OBJECT-TYPE 1215 SYNTAX SEQUENCE OF Dot1dTpPortEntry 1216 MAX-ACCESS not-accessible 1217 STATUS current 1218 DESCRIPTION 1219 "A table that contains information about every port that 1220 is associated with this transparent bridge." 1221 ::= { dot1dTp 4 } 1223 dot1dTpPortEntry OBJECT-TYPE 1224 SYNTAX Dot1dTpPortEntry 1225 MAX-ACCESS not-accessible 1226 STATUS current 1227 DESCRIPTION 1228 "A list of information for each port of a transparent 1229 bridge." 1230 INDEX { dot1dTpPort } 1231 ::= { dot1dTpPortTable 1 } 1233 Dot1dTpPortEntry ::= 1234 SEQUENCE { 1235 dot1dTpPort 1236 Integer32, 1237 dot1dTpPortMaxInfo 1238 Integer32, 1239 dot1dTpPortInFrames 1240 Counter32, 1241 dot1dTpPortOutFrames 1242 Counter32, 1243 dot1dTpPortInDiscards 1244 Counter32 1245 } 1247 dot1dTpPort OBJECT-TYPE 1248 SYNTAX Integer32 (1..65535) 1249 MAX-ACCESS not-accessible 1250 STATUS current 1251 DESCRIPTION 1252 "The port number of the port for which this entry 1253 contains Transparent bridging management information." 1254 ::= { dot1dTpPortEntry 1 } 1256 -- It would be nice if we could use ifMtu as the size of the 1257 -- largest INFO field, but we can't because ifMtu is defined 1258 -- to be the size that the (inter-)network layer can use which 1259 -- can differ from the MAC layer (especially if several layers 1260 -- of encapsulation are used). 1262 dot1dTpPortMaxInfo OBJECT-TYPE 1263 SYNTAX Integer32 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "The maximum size of the INFO (non-MAC) field that 1268 this port will receive or transmit." 1269 ::= { dot1dTpPortEntry 2 } 1271 dot1dTpPortInFrames OBJECT-TYPE 1272 SYNTAX Counter32 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "The number of frames that have been received by this 1277 port from its segment. Note that a frame received on the 1278 interface corresponding to this port is only counted by 1279 this object if and only if it is for a protocol being 1280 processed by the local bridging function, including 1281 bridge management frames." 1282 REFERENCE 1283 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1284 ::= { dot1dTpPortEntry 3 } 1286 dot1dTpPortOutFrames OBJECT-TYPE 1287 SYNTAX Counter32 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "The number of frames that have been transmitted by this 1292 port to its segment. Note that a frame transmitted on 1293 the interface corresponding to this port is only counted 1294 by this object if and only if it is for a protocol being 1295 processed by the local bridging function, including 1296 bridge management frames." 1297 REFERENCE 1298 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1299 ::= { dot1dTpPortEntry 4 } 1301 dot1dTpPortInDiscards OBJECT-TYPE 1302 SYNTAX Counter32 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "Count of valid frames received which were discarded 1307 (i.e., filtered) by the Forwarding Process." 1308 REFERENCE 1309 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1310 ::= { dot1dTpPortEntry 5 } 1312 -- ---------------------------------------------------------- -- 1313 -- The Static (Destination-Address Filtering) Database 1314 -- ---------------------------------------------------------- -- 1315 -- Implementation of this group is optional. 1316 -- ---------------------------------------------------------- -- 1318 dot1dStaticTable OBJECT-TYPE 1319 SYNTAX SEQUENCE OF Dot1dStaticEntry 1320 MAX-ACCESS not-accessible 1321 STATUS current 1322 DESCRIPTION 1323 "A table containing filtering information configured 1324 into the bridge by (local or network) management 1325 specifying the set of ports to which frames received 1326 from specific ports and containing specific destination 1327 addresses are allowed to be forwarded. The value of 1328 zero in this table as the port number from which frames 1329 with a specific destination address are received, is 1330 used to specify all ports for which there is no specific 1331 entry in this table for that particular destination 1332 address. Entries are valid for unicast and for 1333 group/broadcast addresses." 1334 REFERENCE 1335 "IEEE 802.1D-1990: Section 6.7.2" 1336 ::= { dot1dStatic 1 } 1338 dot1dStaticEntry OBJECT-TYPE 1339 SYNTAX Dot1dStaticEntry 1340 MAX-ACCESS not-accessible 1341 STATUS current 1342 DESCRIPTION 1344 "Filtering information configured into the bridge by 1345 (local or network) management specifying the set of 1346 ports to which frames received from a specific port and 1347 containing a specific destination address are allowed to 1348 be forwarded." 1349 REFERENCE 1350 "IEEE 802.1D-1990: Section 6.7.2" 1351 INDEX { dot1dStaticAddress, dot1dStaticReceivePort } 1352 ::= { dot1dStaticTable 1 } 1354 Dot1dStaticEntry ::= 1355 SEQUENCE { 1356 dot1dStaticAddress MacAddress, 1357 dot1dStaticReceivePort Integer32, 1358 dot1dStaticAllowedToGoTo OCTET STRING, 1359 dot1dStaticStatus INTEGER 1360 } 1362 dot1dStaticAddress OBJECT-TYPE 1363 SYNTAX MacAddress 1364 MAX-ACCESS read-create 1365 STATUS current 1366 DESCRIPTION 1367 "The destination MAC address in a frame to which this 1368 entry's filtering information applies. This object can 1369 take the value of a unicast address, a group address or 1370 the broadcast address." 1371 REFERENCE 1372 "IEEE 802.1D-1990: Section 3.9.1, 3.9.2" 1373 ::= { dot1dStaticEntry 1 } 1375 dot1dStaticReceivePort OBJECT-TYPE 1376 SYNTAX Integer32 (0..65535) 1377 MAX-ACCESS read-create 1378 STATUS current 1379 DESCRIPTION 1380 "Either the value '0', or the port number of the port 1381 from which a frame must be received in order for this 1382 entry's filtering information to apply. A value of zero 1383 indicates that this entry applies on all ports of the 1384 bridge for which there is no other applicable entry." 1385 ::= { dot1dStaticEntry 2 } 1387 dot1dStaticAllowedToGoTo OBJECT-TYPE 1388 SYNTAX OCTET STRING (SIZE (0..512)) 1389 MAX-ACCESS read-create 1390 STATUS current 1391 DESCRIPTION 1392 "The set of ports to which frames received from a 1393 specific port and destined for a specific MAC address, 1394 are allowed to be forwarded. Each octet within the 1395 value of this object specifies a set of eight ports, 1396 with the first octet specifying ports 1 through 8, the 1397 second octet specifying ports 9 through 16, etc. Within 1398 each octet, the most significant bit represents the 1399 lowest numbered port, and the least significant bit 1400 represents the highest numbered port. Thus, each port 1401 of the bridge is represented by a single bit within the 1402 value of this object. If that bit has a value of '1' 1403 then that port is included in the set of ports; the port 1404 is not included if its bit has a value of '0'. (Note 1405 that the setting of the bit corresponding to the port 1406 from which a frame is received is irrelevant.) The 1407 default value of this object is a string of ones of 1408 appropriate length. 1410 This exceeds the minimum required SNMP packet size 1411 supported. This is sufficient to allow the maximum 1412 4096 ports now supported." 1413 ::= { dot1dStaticEntry 3 } 1415 dot1dStaticStatus OBJECT-TYPE 1416 SYNTAX INTEGER { 1417 other(1), 1418 invalid(2), 1419 permanent(3), 1420 deleteOnReset(4), 1421 deleteOnTimeout(5) 1422 } 1423 MAX-ACCESS read-create 1424 STATUS current 1425 DESCRIPTION 1426 "This object indicates the status of this entry. 1427 The default value is permanent(3). 1428 other(1) - this entry is currently in use but the 1429 conditions under which it will remain so are 1430 different from each of the following values. 1431 invalid(2) - writing this value to the object 1432 removes the corresponding entry. 1433 permanent(3) - this entry is currently in use and 1434 will remain so after the next reset of the 1435 bridge. 1436 deleteOnReset(4) - this entry is currently in use 1437 and will remain so until the next reset of the 1438 bridge. 1439 deleteOnTimeout(5) - this entry is currently in use 1440 and will remain so until it is aged out." 1441 ::= { dot1dStaticEntry 4 } 1443 -- ---------------------------------------------------------- -- 1444 -- Notifications for use by Bridges 1445 -- ---------------------------------------------------------- -- 1446 -- Notifications for the Spanning Tree Protocol 1447 -- ---------------------------------------------------------- -- 1448 newRoot NOTIFICATION-TYPE 1449 -- OBJECTS { } 1450 STATUS current 1451 DESCRIPTION 1452 "The newRoot trap indicates that the sending agent has 1453 become the new root of the Spanning Tree; the trap is 1454 sent by a bridge soon after its election as the new 1455 root, e.g., upon expiration of the Topology Change Timer 1456 immediately subsequent to its election. Implementation 1457 of this trap is optional." 1458 ::= { dot1dNotification 1 } 1460 topologyChange NOTIFICATION-TYPE 1461 -- OBJECTS { } 1462 STATUS current 1463 DESCRIPTION 1464 "A topologyChange trap is sent by a bridge when any of 1465 its configured ports transitions from the Learning state 1466 to the Forwarding state, or from the Forwarding state to 1467 the Blocking state. The trap is not sent if a newRoot 1468 trap is sent for the same transition. Implementation of 1469 this trap is optional." 1470 ::= { dot1dNotification 2 } 1472 -- ---------------------------------------------------------- -- 1473 -- IEEE 802.1D MIB - Conformance Information 1474 -- ---------------------------------------------------------- -- 1476 dot1dGroups OBJECT IDENTIFIER ::= { dot1dConformance 1 } 1477 dot1dCompliances OBJECT IDENTIFIER ::= { dot1dConformance 2 } 1479 -- ---------------------------------------------------------- -- 1480 -- units of conformance 1481 -- ---------------------------------------------------------- -- 1483 -- ---------------------------------------------------------- -- 1484 -- the dot1dBase group 1485 -- ---------------------------------------------------------- -- 1487 dot1dBaseBridgeGroup OBJECT-GROUP 1488 OBJECTS { 1489 dot1dBaseBridgeAddress, 1490 dot1dBaseNumPorts, 1491 dot1dBaseType 1492 } 1493 STATUS current 1494 DESCRIPTION 1495 "Bridge level information for this device." 1496 ::= { dot1dGroups 1 } 1498 dot1dBasePortGroup OBJECT-GROUP 1499 OBJECTS { 1500 dot1dBasePortIfIndex, 1501 dot1dBasePortCircuit, 1502 dot1dBasePortDelayExceededDiscards, 1503 dot1dBasePortMtuExceededDiscards 1504 } 1505 STATUS current 1506 DESCRIPTION 1507 "Information for each port on this device." 1508 ::= { dot1dGroups 2 } 1510 -- ---------------------------------------------------------- -- 1511 -- the dot1dStp group 1512 -- ---------------------------------------------------------- -- 1514 dot1dStpBridgeGroup OBJECT-GROUP 1515 OBJECTS { 1516 dot1dStpProtocolSpecification, 1517 dot1dStpPriority, 1518 dot1dStpTimeSinceTopologyChange, 1519 dot1dStpTopChanges, 1520 dot1dStpDesignatedRoot, 1521 dot1dStpRootCost, 1522 dot1dStpRootPort, 1523 dot1dStpMaxAge, 1524 dot1dStpHelloTime, 1525 dot1dStpHoldTime, 1526 dot1dStpForwardDelay, 1527 dot1dStpBridgeMaxAge, 1528 dot1dStpBridgeHelloTime, 1529 dot1dStpBridgeForwardDelay 1530 } 1531 STATUS current 1532 DESCRIPTION 1533 "Bridge level Spanning Tree data for this device." 1534 ::= { dot1dGroups 3 } 1536 dot1dStpPortGroup OBJECT-GROUP 1537 OBJECTS { 1538 dot1dStpPortPriority, 1539 dot1dStpPortState, 1540 dot1dStpPortEnable, 1541 dot1dStpPortPathCost, 1542 dot1dStpPortDesignatedRoot, 1543 dot1dStpPortDesignatedCost, 1544 dot1dStpPortDesignatedBridge, 1545 dot1dStpPortDesignatedPort, 1546 dot1dStpPortForwardTransitions 1547 } 1548 STATUS current 1549 DESCRIPTION 1550 "Spanning Tree data for each port on this device." 1551 ::= { dot1dGroups 4 } 1553 -- ---------------------------------------------------------- -- 1554 -- the dot1dTp group 1555 -- ---------------------------------------------------------- -- 1557 dot1dTpBridgeGroup OBJECT-GROUP 1558 OBJECTS { 1559 dot1dTpLearnedEntryDiscards, 1560 dot1dTpAgingTime 1561 } 1562 STATUS current 1563 DESCRIPTION 1564 "Bridge level Transparent Bridging data." 1565 ::= { dot1dGroups 5 } 1567 dot1dTpFdbGroup OBJECT-GROUP 1568 OBJECTS { 1569 dot1dTpFdbPort, 1570 dot1dTpFdbStatus 1571 } 1572 STATUS current 1573 DESCRIPTION 1574 "Filtering Database information for the Bridge." 1575 ::= { dot1dGroups 6 } 1577 dot1dTpGroup OBJECT-GROUP 1578 OBJECTS { 1579 dot1dTpPortMaxInfo, 1580 dot1dTpPortInFrames, 1581 dot1dTpPortOutFrames, 1582 dot1dTpPortInDiscards 1583 } 1584 STATUS current 1585 DESCRIPTION 1586 "Dynamic Filtering Database information for each port of 1587 the Bridge." 1588 ::= { dot1dGroups 7 } 1590 -- ---------------------------------------------------------- -- 1591 -- The Static (Destination-Address Filtering) Database 1592 -- ---------------------------------------------------------- -- 1594 dot1dStaticGroup OBJECT-GROUP 1595 OBJECTS { 1596 dot1dStaticAllowedToGoTo, 1597 dot1dStaticStatus 1598 } 1599 STATUS current 1600 DESCRIPTION 1601 "Static Filtering Database information for each port of 1602 the Bridge." 1603 ::= { dot1dGroups 8 } 1605 -- ---------------------------------------------------------- -- 1606 -- The Trap Notfication Group 1607 -- ---------------------------------------------------------- -- 1608 dot1dNotificationGroup NOTIFICATION-GROUP 1609 NOTIFICATIONS { 1610 newRoot, 1611 topologyChange 1612 } 1613 STATUS current 1614 DESCRIPTION 1615 "Group of objects describing notifications (traps)." 1616 ::= { dot1dGroups 9 } 1618 -- ---------------------------------------------------------- -- 1619 -- compliance statements 1620 -- ---------------------------------------------------------- -- 1622 bridgeCompliance MODULE-COMPLIANCE 1623 STATUS current 1624 DESCRIPTION 1625 "The compliance statement for device support of bridging 1626 services." 1628 MODULE 1629 MANDATORY-GROUPS { 1630 dot1dBaseBridgeGroup, 1631 dot1dBasePortGroup 1632 } 1634 GROUP dot1dStpBridgeGroup 1635 DESCRIPTION 1636 "Implementation of this group is mandatory for 1637 bridges that support the Spanning Tree Protocol." 1639 GROUP dot1dStpPortGroup 1640 DESCRIPTION 1641 "Implementation of this group is mandatory for 1642 bridges that support the Spanning Tree Protocol." 1644 GROUP dot1dTpBridgeGroup 1645 DESCRIPTION 1646 "Implementation of this group is mandatory for 1647 bridges that support the transparent bridging 1648 mode. A transparent or SRT bridge will implement 1649 this group." 1651 GROUP dot1dTpFdbGroup 1652 DESCRIPTION 1653 "Implementation of this group is mandatory for 1654 bridges that support the transparent bridging 1655 mode. A transparent or SRT bridge will implement 1656 this group." 1658 GROUP dot1dTpGroup 1659 DESCRIPTION 1660 "Implementation of this group is mandatory for 1661 bridges that support the transparent bridging 1662 mode. A transparent or SRT bridge will implement 1663 this group." 1665 GROUP dot1dStaticGroup 1666 DESCRIPTION 1667 "Implementation of this group is optional." 1669 GROUP dot1dNotificationGroup 1670 DESCRIPTION 1671 "Implementation of this group is optional." 1672 ::= { dot1dCompliances 1 } 1674 END 1676 4. Security Considerations 1678 There are a number of management objects defined in this MIB that 1679 have a MAX-ACCESS clause of read-write and/or read-create. Such 1680 objects may be considered sensitive or vulnerable in some network 1681 environments. The support for SET operations in a non-secure 1682 environment without proper protection can have a negative effect on 1683 network operations. 1685 SNMPv1 by itself is not a secure environment. Even if the network 1686 itself is secure (for example by using IPSec), even then, there is no 1687 control as to who on the secure network is allowed to access and 1688 GET/SET (read/change/create/delete) the objects in this MIB. 1690 It is recommended that the implementers consider the security 1691 features as provided by the SNMPv3 framework. Specifically, the use 1692 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1693 based Access Control Model RFC 2575 [RFC2575] is recommended. 1695 It is then a customer/user responsibility to ensure that the SNMP 1696 entity giving access to an instance of this MIB, is properly 1697 configured to give access to the objects only to those principals 1698 (users) that have legitimate rights to indeed GET or SET 1699 (change/create/delete) them. 1701 5. Acknowledgments 1703 The MIB presented in this memo is a direct translation of the BRIDGE 1704 MIB defined in [RFC1493], to the SMIv2 syntax required for current 1705 IETF MIB standards. 1707 The original authors were E. Decker, P. Langille, A Rijsinghani and 1708 K. McCloghrie. Further acknowledgement is given to the members of 1709 the original Bridge Working Group in [RFC1493]. 1711 This document was produced on behalf of the Bridge MIB Working Group 1712 in the Operations and Management area of the Internet Engineering 1713 Task Force. 1715 The authors wish to thank the members of the Bridge MIB Working Group 1716 for their many comments and suggestions which improved this effort. 1718 6. References 1720 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1721 for Describing SNMP Management Frameworks", RFC 2571, April 1722 1999. 1724 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1725 of Management Information for TCP/IP-based Internets", STD 1726 16, RFC 1155, May 1990. 1728 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1729 16, RFC 1212, March 1991. 1731 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1732 SNMP", RFC 1215, March 1991. 1734 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1735 Rose, M., and S. Waldbusser, "Structure of Management 1736 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1737 1999. 1739 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1740 Rose, M., and S. Waldbusser, "Textual Conventions for 1741 SMIv2", STD 58, RFC 2579, April 1999. 1743 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1744 Rose, M., and S. Waldbusser, "Conformance Statements for 1745 SMIv2", STD 58, RFC 2580, April 1999. 1747 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1748 Network Management Protocol", STD 15, RFC 1157, May 1990. 1750 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1751 "Introduction to Community-based SNMPv2", RFC 1901, January 1752 1996. 1754 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1755 "Transport Mappings for Version 2 of the Simple Network 1756 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1758 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1759 Processing and Dispatching for the Simple Network Management 1760 Protocol (SNMP)", RFC 2572, April 1999. 1762 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1763 (USM) for version 3 of the Simple Network Management 1764 Protocol (SNMPv3)", RFC 2574, April 1999. 1766 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1767 "Protocol Operations for Version 2 of the Simple Network 1768 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1770 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1771 RFC 2573, April 1999. 1773 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1774 Access Control Model (VACM) for the Simple Network 1775 Management Protocol (SNMP)", RFC 2575, April 1999. 1777 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1778 "Introduction to Version 3 of the Internet-standard Network 1779 Management Framework", RFC 2570, April 1999. 1781 [IEEE8021D] ANSI/IEEE Standard 802.1D-1990 MAC Bridges, IEEE Project 802 1782 Local and Metropolitan Area Networks, (March 8, 1991). 1784 [ISO8021D] ISO DIS 10038 MAC Bridges. 1786 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1787 MIB", RFC 2863, June 2000. 1789 [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1790 "Management Information Base for Version 2 of the Simple 1791 Network Management Protocol (SNMPv2)", RFC 1907, January 1793 1996. 1795 7. Changes from RFC 1493 1797 The following changes have been made from RFC 1493. 1799 (1) Translated the MIB definition to use SMIv2. 1801 (2) Updated the SNMP Framework and references to comply with the 1802 current IETF guidelines. 1804 (3) Updated the Security section to comply with current IETF 1805 guidelines. 1807 The following chnages have been made from 1808 draft-ietf-bridge-bridgemib-smiv2-00.txt 1810 (1) Misc. description refernces to IEEE 802.1d documents 1812 (2) dot1dNotificationGroup changed from dot1dTrapGroup 1814 (3) Misc. additions to some descriptions 1816 The following chnages have been made from 1817 draft-ietf-bridge-bridgemib-smiv2-01.txt 1819 (1) corrections to objects that were made not-accessible in the 1820 draft-00 version that were read /read-write in rfc 1493 1822 (2) Misc. additions to some descriptions 1824 8. Authors' Addresses 1826 K.C. Norseth 1827 Enterasys Networks 1828 2691 S. Decker Lake Lane 1829 Salt Lake City, Utah 84119 1830 Phone: +1 801 887 9823 1831 Email: knorseth@enterasys.com 1833 9. Full Copyright 1835 Copyright (C) The Internet Society (2001). All Rights Reserved. 1837 This document and translations of it may be copied and furnished to 1838 others, and derivative works that comment on or otherwise explain it 1839 or assist in its implmentation may be prepared, copied, published and 1840 distributed, in whole or in part, without restriction of any kind, 1841 provided that the above copyright notice and this paragraph are 1842 included on all such copies and derivative works. However, this 1843 document itself may not be modified in any way, such as by removing 1844 the copyright notice or references to the Internet Society or other 1845 Internet organizations, except as needed for the purpose of 1846 developing Internet standards in which case the procedures for 1847 copyrights defined in the Internet Standards process must be 1848 followed, or as required to translate it into languages other than 1849 English. 1851 The limited permissions granted above are perpetual and will not be 1852 revoked by the Internet Society or its successors or assigns. 1854 This document and the information contained herein is provided on an 1855 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1856 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1857 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1858 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1859 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1861 Table of Contents 1863 1 The SNMP Management Framework ................................ 2 1864 2 Overview ..................................................... 3 1865 2.1 Structure of MIB ........................................... 3 1866 2.1.1 The dot1dBase Group ...................................... 5 1867 2.1.2 The dot1dStp Group ....................................... 5 1868 2.1.3 The dot1dSr Group ........................................ 6 1869 2.1.4 The dot1dTp Group ........................................ 6 1870 2.1.5 The dot1dStatic Group .................................... 6 1871 2.2 Relationship to Other MIBs ................................. 6 1872 2.2.1 Relationship to the 'system' group ....................... 6 1873 2.2.2 Relationship to the 'interfaces' group ................... 6 1874 2.3 Textual Conventions ........................................ 7 1875 3 Definitions .................................................. 7 1876 4 Security Considerations ...................................... 32 1877 5 Acknowledgments .............................................. 32 1878 6 References ................................................... 33 1879 7 Changes from RFC 1493 and Previous Drafts .................... 34 1880 8 Authors' Addresses ........................................... 34 1881 9 Full Copyright ............................................... 35