idnits 2.17.1 draft-ietf-bridge-bridgemib-smiv2-04.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 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 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 (Oct 2002) is 7863 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 1798, 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 1854, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE8021D' -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO8021D' -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 1907 (Obsoleted by RFC 3418) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) Summary: 12 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Editors of this version: 2 Expires June 2003 K.C. Norseth 3 draft-ietf-bridge-bridgemib-smiv2-04.txt L-3 Communications 4 Obsoletes: 1493 E. Bell 5 3Com Corp. 6 Authors of previous version: 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 Oct 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-1998 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 "200212050000Z" 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 "200212050000Z" 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-1998 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-1998: clauses 14.4.1.1.3 and 7.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-1998: clause 14.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." 556 ::= { dot1dBase 4 } 558 dot1dBasePortEntry OBJECT-TYPE 559 SYNTAX Dot1dBasePortEntry 560 MAX-ACCESS not-accessible 561 STATUS current 562 DESCRIPTION 563 "A list of information for each port of the bridge." 564 REFERENCE 565 "IEEE 802.1D-1998: clause 14.4.2, 14.6.1" 566 INDEX { dot1dBasePort } 567 ::= { dot1dBasePortTable 1 } 569 Dot1dBasePortEntry ::= 570 SEQUENCE { 571 dot1dBasePort 572 Integer32, 573 dot1dBasePortIfIndex 574 InterfaceIndex, 575 dot1dBasePortCircuit 576 OBJECT IDENTIFIER, 577 dot1dBasePortDelayExceededDiscards 578 Counter32, 579 dot1dBasePortMtuExceededDiscards 580 Counter32 581 } 583 dot1dBasePort OBJECT-TYPE 584 SYNTAX Integer32 (1..65535) 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "The port number of the port for which this entry 589 contains bridge management information." 590 ::= { dot1dBasePortEntry 1 } 592 dot1dBasePortIfIndex OBJECT-TYPE 593 SYNTAX InterfaceIndex 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "The value of the instance of the ifIndex object, 598 defined in IF-MIB, for the interface corresponding 599 to this port." 600 ::= { dot1dBasePortEntry 2 } 602 dot1dBasePortCircuit OBJECT-TYPE 603 SYNTAX OBJECT IDENTIFIER 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "For a port which (potentially) has the same value of 608 dot1dBasePortIfIndex as another port on the same bridge, 609 this object contains the name of an object instance 610 unique to this port. For example, in the case where 611 multiple ports correspond one- to-one with multiple X.25 612 virtual circuits, this value might identify an (e.g., 613 the first) object instance associated with the X.25 614 virtual circuit corresponding to this port. 616 For a port which has a unique value of 617 dot1dBasePortIfIndex, this object can have the value 618 { 0 0 }." 619 ::= { dot1dBasePortEntry 3 } 621 dot1dBasePortDelayExceededDiscards OBJECT-TYPE 622 SYNTAX Counter32 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The number of frames discarded by this port due 627 to excessive transit delay through the bridge. It 628 is incremented by both transparent and source 629 route bridges." 630 REFERENCE 631 "IEEE 802.1D-1998: clause 14.6.1.1.3" 632 ::= { dot1dBasePortEntry 4 } 634 dot1dBasePortMtuExceededDiscards OBJECT-TYPE 635 SYNTAX Counter32 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "The number of frames discarded by this port due 640 to an excessive size. It is incremented by both 641 transparent and source route bridges." 643 REFERENCE 644 "IEEE 802.1D-1998: clause 14.6.1.1.3" 645 ::= { dot1dBasePortEntry 5 } 647 -- ---------------------------------------------------------- -- 648 -- the dot1dStp group 649 -- ---------------------------------------------------------- -- 650 -- Implementation of the dot1dStp group is optional. It is 651 -- implemented by those bridges that support the Spanning Tree 652 -- Protocol. 653 -- ---------------------------------------------------------- -- 655 dot1dStpProtocolSpecification OBJECT-TYPE 656 SYNTAX INTEGER { 657 unknown(1), 658 decLb100(2), 659 ieee8021d(3) 660 } 661 MAX-ACCESS read-only 662 STATUS current 663 DESCRIPTION 664 "An indication of what version of the Spanning Tree 665 Protocol is being run. The value 'decLb100(2)' 666 indicates the DEC LANbridge 100 Spanning Tree protocol. 667 IEEE 802.1D implementations will return 'ieee8021d(3)'. 668 If future versions of the IEEE Spanning Tree Protocol 669 are released that are incompatible with the current 670 version a new value will be defined." 671 ::= { dot1dStp 1 } 673 dot1dStpPriority OBJECT-TYPE 674 SYNTAX Integer32 (0..65535) 675 MAX-ACCESS read-write 676 STATUS current 677 DESCRIPTION 678 "The value of the write-able portion of the Bridge ID, 679 i.e., the first two octets of the (8 octet long) Bridge 680 ID. The other (last) 6 octets of the Bridge ID are 681 given by the value of dot1dBaseBridgeAddress. 682 On bridges supporting IEEE 802.1t or IEEE 802.1w, 683 permissible values are 0-61440, in steps of 4096." 684 REFERENCE 685 "IEEE 802.1D-1998 clause 8.10.2, Table 8-4, 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. 698 For RSTP, this reports the time since the tcWhile 699 timer for any port on this Bridge was non-zero." 700 REFERENCE 701 "IEEE 802.1D-1998 clause 14.8.1.1., 702 IEEE 802.1w clause 14.8.1.1." 703 ::= { dot1dStp 3 } 705 dot1dStpTopChanges OBJECT-TYPE 706 SYNTAX Counter32 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The total number of topology changes detected by 711 this bridge since the management entity was last 712 reset or initialized." 713 REFERENCE 714 "IEEE 802.1D-1998 clause 14.8.1.1." 715 ::= { dot1dStp 4 } 717 dot1dStpDesignatedRoot OBJECT-TYPE 718 SYNTAX BridgeId 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "The bridge identifier of the root of the spanning 723 tree as determined by the Spanning Tree Protocol 724 as executed by this node. This value is used as 725 the Root Identifier parameter in all Configuration 726 Bridge PDUs originated by this node." 727 REFERENCE 728 "IEEE 802.1D-1998: clause 8.5.3.1" 729 ::= { dot1dStp 5 } 731 dot1dStpRootCost OBJECT-TYPE 732 SYNTAX Integer32 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "The cost of the path to the root as seen from 737 this bridge." 738 REFERENCE 739 "IEEE 802.1D-1998: clause 8.5.3.2" 740 ::= { dot1dStp 6 } 742 dot1dStpRootPort OBJECT-TYPE 743 SYNTAX Integer32 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "The port number of the port which offers the lowest 748 cost path from this bridge to the root bridge." 749 REFERENCE 750 "IEEE 802.1D-1998: clause 8.5.3.3" 751 ::= { dot1dStp 7 } 753 dot1dStpMaxAge OBJECT-TYPE 754 SYNTAX Timeout 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "The maximum age of Spanning Tree Protocol information 759 learned from the network on any port before it is 760 discarded, in units of hundredths of a second. This is 761 the actual value that this bridge is currently using." 762 REFERENCE 763 "IEEE 802.1D-1998: clause 8.5.3.4" 764 ::= { dot1dStp 8 } 766 dot1dStpHelloTime OBJECT-TYPE 767 SYNTAX Timeout 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "The amount of time between the transmission of 772 Configuration bridge PDUs by this node on any port when 773 it is the root of the spanning tree or trying to become 774 so, in units of hundredths of a second. This is the 775 actual value that this bridge is currently using." 776 REFERENCE 777 "IEEE 802.1D-1998: clause 8.5.3.5" 778 ::= { dot1dStp 9 } 780 dot1dStpHoldTime OBJECT-TYPE 781 SYNTAX Integer32 782 MAX-ACCESS read-only 783 STATUS current 784 DESCRIPTION 785 "This time value determines the interval length 786 during which no more than two Configuration bridge 787 PDUs shall be transmitted by this node, in units 788 of hundredths of a second." 789 REFERENCE 790 "IEEE 802.1D-1998: clause 8.5.3.14" 791 ::= { dot1dStp 10 } 793 dot1dStpForwardDelay OBJECT-TYPE 794 SYNTAX Timeout 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "This time value, measured in units of hundredths of a 799 second, controls how fast a port changes its spanning 800 state when moving towards the Forwarding state. The 801 value determines how long the port stays in each of the 802 Listening and Learning states, which precede the 803 Forwarding state. This value is also used, when a 804 topology change has been detected and is underway, to 805 age all dynamic entries in the Forwarding Database. 807 [Note that this value is the one that this bridge is 808 currently using, in contrast to 809 dot1dStpBridgeForwardDelay which is the value that this 810 bridge and all others would start using if/when this 811 bridge were to become the root.]" 812 REFERENCE 813 "IEEE 802.1D-1998: clause 8.5.3.6" 814 ::= { dot1dStp 11 } 816 dot1dStpBridgeMaxAge OBJECT-TYPE 817 SYNTAX Timeout (600..4000) 818 MAX-ACCESS read-write 819 STATUS current 820 DESCRIPTION 821 "The value that all bridges use for MaxAge when this 822 bridge is acting as the root. Note that 802.1D-1998 823 specifies that the range for this parameter is related 824 to the value of dot1dStpBridgeHelloTime. The 825 granularity of this timer is specified by 802.1D-1998 to 826 be 1 second. An agent may return a badValue error if a 827 set is attempted to a value which is not a whole number 828 of seconds." 829 REFERENCE 830 "IEEE 802.1D-1998: clause 8.5.3.8" 831 ::= { dot1dStp 12 } 833 dot1dStpBridgeHelloTime OBJECT-TYPE 834 SYNTAX Timeout (100..1000) 835 MAX-ACCESS read-write 836 STATUS current 837 DESCRIPTION 838 "The value that all bridges use for HelloTime when this 839 bridge is acting as the root. The granularity of this 840 timer is specified by 802.1D-1998 to be 1 second. An 841 agent may return a badValue error if a set is attempted 842 to a value which is not a whole number of seconds." 843 REFERENCE 844 "IEEE 802.1D-1998: clause 8.5.3.9" 845 ::= { dot1dStp 13 } 847 dot1dStpBridgeForwardDelay OBJECT-TYPE 848 SYNTAX Timeout (400..3000) 849 MAX-ACCESS read-write 850 STATUS current 851 DESCRIPTION 852 "The value that all bridges use for ForwardDelay when 853 this bridge is acting as the root. Note that 854 802.1D-1998 specifies that the range for this parameter 855 is related to the value of dot1dStpBridgeMaxAge. The 856 granularity of this timer is specified by 802.1D-1998 to 857 be 1 second. An agent may return a badValue error if a 858 set is attempted to a value which is not a whole number 859 of seconds." 860 REFERENCE 861 "IEEE 802.1D-1998: clause 8.5.3.10" 862 ::= { dot1dStp 14 } 864 -- ---------------------------------------------------------- -- 865 -- The Spanning Tree Port Table 866 -- ---------------------------------------------------------- -- 868 dot1dStpPortTable OBJECT-TYPE 869 SYNTAX SEQUENCE OF Dot1dStpPortEntry 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "A table that contains port-specific information 874 for the Spanning Tree Protocol." 875 ::= { dot1dStp 15 } 877 dot1dStpPortEntry OBJECT-TYPE 878 SYNTAX Dot1dStpPortEntry 879 MAX-ACCESS not-accessible 880 STATUS current 881 DESCRIPTION 882 "A list of information maintained by every port about 883 the Spanning Tree Protocol state for that port." 884 INDEX { dot1dStpPort } 885 ::= { dot1dStpPortTable 1 } 887 Dot1dStpPortEntry ::= 888 SEQUENCE { 889 dot1dStpPort 890 Integer32, 891 dot1dStpPortPriority 892 Integer32, 893 dot1dStpPortState 894 INTEGER, 895 dot1dStpPortEnable 896 INTEGER, 897 dot1dStpPortPathCost 898 INTEGER, 899 dot1dStpPortDesignatedRoot 900 BridgeId, 901 dot1dStpPortDesignatedCost 902 Integer32, 903 dot1dStpPortDesignatedBridge 904 BridgeId, 905 dot1dStpPortDesignatedPort 906 OCTET STRING, 907 dot1dStpPortForwardTransitions 908 Counter32, 909 dot1dStpPortPathCost32 910 Integer32 911 } 913 dot1dStpPort OBJECT-TYPE 914 SYNTAX Integer32 (1..65535) 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "The port number of the port for which this entry 919 contains Spanning Tree Protocol management information." 920 REFERENCE 921 "IEEE 802.1D-1998: clause 14.8.2.1.2" 922 ::= { dot1dStpPortEntry 1 } 924 dot1dStpPortPriority OBJECT-TYPE 925 SYNTAX Integer32 (0.. 255) 926 MAX-ACCESS read-write 927 STATUS current 928 DESCRIPTION 929 "The value of the priority field which is contained in 930 the first (in network byte order) octet of the (2 octet 931 long) Port ID. The other octet of the Port ID is given 932 by the value of dot1dStpPort. 933 On bridges supporting IEEE 802.1t or IEEE 802.1w, 934 permissible values are 0-240, in steps of 16." 935 REFERENCE 936 "IEEE 802.1D-1998 clause 8.10.2, Table 8-4, 937 IEEE 802.1t clause 8.10.2, Table 8-4, clause 14.3." 938 ::= { dot1dStpPortEntry 2 } 940 dot1dStpPortState OBJECT-TYPE 941 SYNTAX INTEGER { 942 disabled(1), 943 blocking(2), 944 listening(3), 945 learning(4), 946 forwarding(5), 947 broken(6) 948 } 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "The port's current state as defined by application of 953 the Spanning Tree Protocol. This state controls what 954 action a port takes on reception of a frame. If the 955 bridge has detected a port that is malfunctioning it 956 will place that port into the broken(6) state. For 957 ports which are disabled (see dot1dStpPortEnable), this 958 object will have a value of disabled(1)." 959 REFERENCE 960 "IEEE 802.1D-1998: clause 8.5.5.2" 961 ::= { dot1dStpPortEntry 3 } 963 dot1dStpPortEnable OBJECT-TYPE 964 SYNTAX INTEGER { 965 enabled(1), 966 disabled(2) 967 } 968 MAX-ACCESS read-write 969 STATUS current 970 DESCRIPTION 971 "The enabled/disabled status of the port." 972 REFERENCE 973 "IEEE 802.1D-1998: clause 8.5.5.2" 974 ::= { dot1dStpPortEntry 4 } 976 dot1dStpPortPathCost OBJECT-TYPE 977 SYNTAX INTEGER (1..65535) 978 MAX-ACCESS read-write 979 STATUS deprecated 980 DESCRIPTION 981 "The contribution of this port to the path cost of 982 paths towards the spanning tree root which include 983 this port. 802.1D-1998 recommends that the 984 default value of this parameter be in inverse 985 proportion to the speed of the attached LAN. 987 New implementations should use dot1dStpPortPathCost32" 988 REFERENCE 989 "IEEE 802.1D-1998: clause 8.5.5.3" 990 ::= { dot1dStpPortEntry 5 } 992 dot1dStpPortDesignatedRoot OBJECT-TYPE 993 SYNTAX BridgeId 994 MAX-ACCESS read-only 995 STATUS current 996 DESCRIPTION 997 "The unique Bridge Identifier of the Bridge 998 recorded as the Root in the Configuration BPDUs 999 transmitted by the Designated Bridge for the 1000 segment to which the port is attached." 1001 REFERENCE 1002 "IEEE 802.1D-1998: clause 8.5.5.4" 1003 ::= { dot1dStpPortEntry 6 } 1005 dot1dStpPortDesignatedCost OBJECT-TYPE 1006 SYNTAX Integer32 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "The path cost of the Designated Port of the segment 1011 connected to this port. This value is compared to the 1012 Root Path Cost field in received bridge PDUs." 1013 REFERENCE 1014 "IEEE 802.1D-1998: clause 8.5.5.5" 1015 ::= { dot1dStpPortEntry 7 } 1017 dot1dStpPortDesignatedBridge OBJECT-TYPE 1018 SYNTAX BridgeId 1019 MAX-ACCESS read-only 1020 STATUS current 1021 DESCRIPTION 1022 "The Bridge Identifier of the bridge which this 1023 port considers to be the Designated Bridge for 1024 this port's segment." 1025 REFERENCE 1026 "IEEE 802.1D-1998: clause 8.5.5.6" 1027 ::= { dot1dStpPortEntry 8 } 1029 dot1dStpPortDesignatedPort OBJECT-TYPE 1030 SYNTAX OCTET STRING (SIZE (2)) 1031 MAX-ACCESS read-only 1032 STATUS current 1033 DESCRIPTION 1034 "The Port Identifier of the port on the Designated 1035 Bridge for this port's segment." 1036 REFERENCE 1037 "IEEE 802.1D-1998: clause 8.5.5.7" 1038 ::= { dot1dStpPortEntry 9 } 1040 dot1dStpPortForwardTransitions OBJECT-TYPE 1041 SYNTAX Counter32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "The number of times this port has transitioned 1046 from the Learning state to the Forwarding state." 1047 ::= { dot1dStpPortEntry 10 } 1049 dot1dStpPortPathCost32 OBJECT-TYPE 1050 SYNTAX Integer32 (1..200000000) 1051 MAX-ACCESS read-write 1052 STATUS current 1053 DESCRIPTION 1054 "The contribution of this port to the path cost of 1055 paths towards the spanning tree root which include 1056 this port. 802.1D-1998 recommends that the 1057 default value of this parameter be in inverse 1058 proportion to the speed of the attached LAN. 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-1998: clause 14.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-1998 recommends a default of 300 seconds." 1101 REFERENCE 1102 "IEEE 802.1D-1998: clause 14.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 1118 determining how to propagate a received frame." 1119 ::= { dot1dTp 3 } 1121 dot1dTpFdbEntry OBJECT-TYPE 1122 SYNTAX Dot1dTpFdbEntry 1123 MAX-ACCESS not-accessible 1124 STATUS current 1125 DESCRIPTION 1126 "Information about a specific unicast MAC address 1127 for which the bridge has some forwarding and/or 1128 filtering information." 1129 INDEX { dot1dTpFdbAddress } 1130 ::= { dot1dTpFdbTable 1 } 1132 Dot1dTpFdbEntry ::= 1133 SEQUENCE { 1134 dot1dTpFdbAddress 1135 MacAddress, 1136 dot1dTpFdbPort 1137 Integer32, 1138 dot1dTpFdbStatus 1139 INTEGER 1140 } 1142 dot1dTpFdbAddress OBJECT-TYPE 1143 SYNTAX MacAddress 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "A unicast MAC address for which the bridge has 1148 forwarding and/or filtering information." 1149 REFERENCE 1150 "IEEE 802.1D-1998: clause 7.9.1, 7.9.2" 1151 ::= { dot1dTpFdbEntry 1 } 1153 dot1dTpFdbPort OBJECT-TYPE 1154 SYNTAX Integer32 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "Either the value '0', or the port number of the port on 1159 which a frame having a source address equal to the value 1160 of the corresponding instance of dot1dTpFdbAddress has 1161 been seen. A value of '0' indicates that the port 1162 number has not been learned but that the bridge does 1163 have some forwarding/filtering information about this 1164 address (e.g. in the dot1dStaticTable). Implementors 1165 are encouraged to assign the port value to this object 1166 whenever it is learned even for addresses for which the 1167 corresponding value of dot1dTpFdbStatus is not 1168 learned(3)." 1169 ::= { dot1dTpFdbEntry 2 } 1171 dot1dTpFdbStatus OBJECT-TYPE 1172 SYNTAX INTEGER { 1173 other(1), 1174 invalid(2), 1175 learned(3), 1176 self(4), 1177 mgmt(5) 1178 } 1179 MAX-ACCESS read-only 1180 STATUS current 1181 DESCRIPTION 1182 "The status of this entry. The meanings of the 1183 values are: 1184 other(1) - none of the following. This would 1185 include the case where some other MIB object 1186 (not the corresponding instance of 1187 dot1dTpFdbPort, nor an entry in the 1188 dot1dStaticTable) is being used to determine if 1189 and how frames addressed to the value of the 1190 corresponding instance of dot1dTpFdbAddress are 1191 being forwarded. 1192 invalid(2) - this entry is not longer valid (e.g., 1193 it was learned but has since aged-out), but has 1194 not yet been flushed from the table. 1195 learned(3) - the value of the corresponding instance 1196 of dot1dTpFdbPort was learned, and is being 1197 used. 1198 self(4) - the value of the corresponding instance of 1199 dot1dTpFdbAddress represents one of the bridge's 1200 addresses. The corresponding instance of 1201 dot1dTpFdbPort indicates which of the bridge's 1202 ports has this address. 1203 mgmt(5) - the value of the corresponding instance of 1204 dot1dTpFdbAddress is also the value of an 1205 existing instance of dot1dStaticAddress." 1206 ::= { dot1dTpFdbEntry 3 } 1208 -- ---------------------------------------------------------- -- 1209 -- Port Table for Transparent Bridges 1210 -- ---------------------------------------------------------- -- 1212 dot1dTpPortTable OBJECT-TYPE 1213 SYNTAX SEQUENCE OF Dot1dTpPortEntry 1214 MAX-ACCESS not-accessible 1215 STATUS current 1216 DESCRIPTION 1217 "A table that contains information about every port that 1218 is associated with this transparent bridge." 1219 ::= { dot1dTp 4 } 1221 dot1dTpPortEntry OBJECT-TYPE 1222 SYNTAX Dot1dTpPortEntry 1223 MAX-ACCESS not-accessible 1224 STATUS current 1225 DESCRIPTION 1226 "A list of information for each port of a transparent 1227 bridge." 1228 INDEX { dot1dTpPort } 1229 ::= { dot1dTpPortTable 1 } 1231 Dot1dTpPortEntry ::= 1232 SEQUENCE { 1233 dot1dTpPort 1234 Integer32, 1235 dot1dTpPortMaxInfo 1236 Integer32, 1237 dot1dTpPortInFrames 1238 Counter32, 1240 dot1dTpPortOutFrames 1241 Counter32, 1242 dot1dTpPortInDiscards 1243 Counter32 1244 } 1246 dot1dTpPort OBJECT-TYPE 1247 SYNTAX Integer32 (1..65535) 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "The port number of the port for which this entry 1252 contains Transparent bridging management information." 1253 ::= { dot1dTpPortEntry 1 } 1255 -- It would be nice if we could use ifMtu as the size of the 1256 -- largest INFO field, but we can't because ifMtu is defined 1257 -- to be the size that the (inter-)network layer can use which 1258 -- can differ from the MAC layer (especially if several layers 1259 -- of encapsulation are used). 1261 dot1dTpPortMaxInfo OBJECT-TYPE 1262 SYNTAX Integer32 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "The maximum size of the INFO (non-MAC) field that 1267 this port will receive or transmit." 1268 ::= { dot1dTpPortEntry 2 } 1270 dot1dTpPortInFrames OBJECT-TYPE 1271 SYNTAX Counter32 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "The number of frames that have been received by this 1276 port from its segment. Note that a frame received on the 1277 interface corresponding to this port is only counted by 1278 this object if and only if it is for a protocol being 1279 processed by the local bridging function, including 1280 bridge management frames." 1281 REFERENCE 1282 "IEEE 802.1D-1998: clause 14.6.1.1.3" 1283 ::= { dot1dTpPortEntry 3 } 1285 dot1dTpPortOutFrames OBJECT-TYPE 1286 SYNTAX Counter32 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "The number of frames that have been transmitted by this 1291 port to its segment. Note that a frame transmitted on 1292 the interface corresponding to this port is only counted 1293 by this object if and only if it is for a protocol being 1294 processed by the local bridging function, including 1295 bridge management frames." 1296 REFERENCE 1297 "IEEE 802.1D-1998: clause 14.6.1.1.3" 1298 ::= { dot1dTpPortEntry 4 } 1300 dot1dTpPortInDiscards OBJECT-TYPE 1301 SYNTAX Counter32 1302 MAX-ACCESS read-only 1303 STATUS current 1304 DESCRIPTION 1305 "Count of valid frames received which were discarded 1306 (i.e., filtered) by the Forwarding Process." 1307 REFERENCE 1308 "IEEE 802.1D-1998: clause 14.6.1.1.3" 1309 ::= { dot1dTpPortEntry 5 } 1311 -- ---------------------------------------------------------- -- 1312 -- The Static (Destination-Address Filtering) Database 1313 -- ---------------------------------------------------------- -- 1314 -- Implementation of this group is optional. 1315 -- ---------------------------------------------------------- -- 1317 dot1dStaticTable OBJECT-TYPE 1318 SYNTAX SEQUENCE OF Dot1dStaticEntry 1319 MAX-ACCESS not-accessible 1320 STATUS current 1321 DESCRIPTION 1322 "A table containing filtering information configured 1323 into the bridge by (local or network) management 1324 specifying the set of ports to which frames received 1325 from specific ports and containing specific destination 1326 addresses are allowed to be forwarded. The value of 1327 zero in this table as the port number from which frames 1328 with a specific destination address are received, is 1329 used to specify all ports for which there is no specific 1330 entry in this table for that particular destination 1331 address. Entries are valid for unicast and for 1332 group/broadcast addresses." 1333 REFERENCE 1334 "IEEE 802.1D-1998: clause 14.7.2" 1335 ::= { dot1dStatic 1 } 1337 dot1dStaticEntry OBJECT-TYPE 1338 SYNTAX Dot1dStaticEntry 1339 MAX-ACCESS not-accessible 1340 STATUS current 1341 DESCRIPTION 1342 "Filtering information configured into the bridge by 1343 (local or network) management specifying the set of 1344 ports to which frames received from a specific port and 1345 containing a specific destination address are allowed to 1346 be forwarded." 1347 REFERENCE 1348 "IEEE 802.1D-1998: clause 14.7.2" 1349 INDEX { dot1dStaticAddress, dot1dStaticReceivePort } 1350 ::= { dot1dStaticTable 1 } 1352 Dot1dStaticEntry ::= 1353 SEQUENCE { 1354 dot1dStaticAddress MacAddress, 1355 dot1dStaticReceivePort Integer32, 1356 dot1dStaticAllowedToGoTo OCTET STRING, 1357 dot1dStaticStatus INTEGER 1358 } 1360 dot1dStaticAddress OBJECT-TYPE 1361 SYNTAX MacAddress 1362 MAX-ACCESS read-create 1363 STATUS current 1364 DESCRIPTION 1365 "The destination MAC address in a frame to which this 1366 entry's filtering information applies. This object can 1367 take the value of a unicast address, a group address or 1368 the broadcast address." 1369 REFERENCE 1370 "IEEE 802.1D-1998: clause 7.9.1, 7.9.2" 1371 ::= { dot1dStaticEntry 1 } 1373 dot1dStaticReceivePort OBJECT-TYPE 1374 SYNTAX Integer32 (0..65535) 1375 MAX-ACCESS read-create 1376 STATUS current 1377 DESCRIPTION 1378 "Either the value '0', or the port number of the port 1379 from which a frame must be received in order for this 1380 entry's filtering information to apply. A value of zero 1381 indicates that this entry applies on all ports of the 1382 bridge for which there is no other applicable entry." 1383 ::= { dot1dStaticEntry 2 } 1385 dot1dStaticAllowedToGoTo OBJECT-TYPE 1386 SYNTAX OCTET STRING (SIZE (0..512)) 1387 MAX-ACCESS read-create 1388 STATUS current 1389 DESCRIPTION 1390 "The set of ports to which frames received from a 1391 specific port and destined for a specific MAC address, 1392 are allowed to be forwarded. Each octet within the 1393 value of this object specifies a set of eight ports, 1394 with the first octet specifying ports 1 through 8, the 1395 second octet specifying ports 9 through 16, etc. Within 1396 each octet, the most significant bit represents the 1397 lowest numbered port, and the least significant bit 1398 represents the highest numbered port. Thus, each port 1399 of the bridge is represented by a single bit within the 1400 value of this object. If that bit has a value of '1' 1401 then that port is included in the set of ports; the port 1402 is not included if its bit has a value of '0'. (Note 1403 that the setting of the bit corresponding to the port 1404 from which a frame is received is irrelevant.) The 1405 default value of this object is a string of ones of 1406 appropriate length. 1408 This exceeds the minimum required SNMP packet size 1409 supported. This is sufficient to allow the maximum 1410 4096 ports now supported." 1411 ::= { dot1dStaticEntry 3 } 1413 dot1dStaticStatus OBJECT-TYPE 1414 SYNTAX INTEGER { 1415 other(1), 1416 invalid(2), 1417 permanent(3), 1418 deleteOnReset(4), 1419 deleteOnTimeout(5) 1420 } 1421 MAX-ACCESS read-create 1422 STATUS current 1423 DESCRIPTION 1424 "This object indicates the status of this entry. 1425 The default value is permanent(3). 1426 other(1) - this entry is currently in use but the 1427 conditions under which it will remain so are 1428 different from each of the following values. 1429 invalid(2) - writing this value to the object 1430 removes the corresponding entry. 1431 permanent(3) - this entry is currently in use and 1432 will remain so after the next reset of the 1433 bridge. 1434 deleteOnReset(4) - this entry is currently in use 1435 and will remain so until the next reset of the 1436 bridge. 1437 deleteOnTimeout(5) - this entry is currently in use 1438 and will remain so until it is aged out." 1439 ::= { dot1dStaticEntry 4 } 1441 -- ---------------------------------------------------------- -- 1442 -- Notifications for use by Bridges 1443 -- ---------------------------------------------------------- -- 1444 -- Notifications for the Spanning Tree Protocol 1445 -- ---------------------------------------------------------- -- 1447 newRoot NOTIFICATION-TYPE 1448 -- OBJECTS { } 1449 STATUS current 1450 DESCRIPTION 1451 "The newRoot trap indicates that the sending agent has 1452 become the new root of the Spanning Tree; the trap is 1453 sent by a bridge soon after its election as the new 1454 root, e.g., upon expiration of the Topology Change Timer 1455 immediately subsequent to its election. Implementation 1456 of this trap is optional." 1457 ::= { dot1dNotification 1 } 1459 topologyChange NOTIFICATION-TYPE 1460 -- OBJECTS { } 1461 STATUS current 1462 DESCRIPTION 1463 "A topologyChange trap is sent by a bridge when any of 1464 its configured ports transitions from the Learning state 1465 to the Forwarding state, or from the Forwarding state to 1466 the Blocking state. The trap is not sent if a newRoot 1467 trap is sent for the same transition. Implementation of 1468 this trap is optional." 1469 ::= { dot1dNotification 2 } 1471 -- ---------------------------------------------------------- -- 1472 -- IEEE 802.1D MIB - Conformance Information 1473 -- ---------------------------------------------------------- -- 1475 dot1dGroups OBJECT IDENTIFIER ::= { dot1dConformance 1 } 1476 dot1dCompliances OBJECT IDENTIFIER ::= { dot1dConformance 2 } 1478 -- ---------------------------------------------------------- -- 1479 -- units of conformance 1480 -- ---------------------------------------------------------- -- 1482 -- ---------------------------------------------------------- -- 1483 -- the dot1dBase group 1484 -- ---------------------------------------------------------- -- 1486 dot1dBaseBridgeGroup OBJECT-GROUP 1487 OBJECTS { 1488 dot1dBaseBridgeAddress, 1489 dot1dBaseNumPorts, 1490 dot1dBaseType 1491 } 1492 STATUS current 1493 DESCRIPTION 1494 "Bridge level information for this device." 1495 ::= { dot1dGroups 1 } 1497 dot1dBasePortGroup OBJECT-GROUP 1498 OBJECTS { 1499 dot1dBasePort, 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 dot1dStpPort, 1539 dot1dStpPortPriority, 1540 dot1dStpPortState, 1541 dot1dStpPortEnable, 1542 dot1dStpPortPathCost, 1543 dot1dStpPortDesignatedRoot, 1544 dot1dStpPortDesignatedCost, 1545 dot1dStpPortDesignatedBridge, 1546 dot1dStpPortDesignatedPort, 1547 dot1dStpPortForwardTransitions 1548 } 1549 STATUS deprecated 1550 DESCRIPTION 1551 "Spanning Tree data for each port on this device." 1552 ::= { dot1dGroups 4 } 1554 dot1dStpPortGroup2 OBJECT-GROUP 1555 OBJECTS { 1556 dot1dStpPort, 1557 dot1dStpPortPriority, 1558 dot1dStpPortState, 1559 dot1dStpPortEnable, 1560 dot1dStpPortDesignatedRoot, 1561 dot1dStpPortDesignatedCost, 1562 dot1dStpPortDesignatedBridge, 1563 dot1dStpPortDesignatedPort, 1564 dot1dStpPortForwardTransitions, 1565 dot1dStpPortPathCost32 1566 } 1567 STATUS current 1568 DESCRIPTION 1569 "Spanning Tree data for each port on this device." 1570 ::= { dot1dGroups 5 } 1572 -- ---------------------------------------------------------- -- 1573 -- the dot1dTp group 1574 -- ---------------------------------------------------------- -- 1576 dot1dTpBridgeGroup OBJECT-GROUP 1577 OBJECTS { 1578 dot1dTpLearnedEntryDiscards, 1579 dot1dTpAgingTime 1580 } 1581 STATUS current 1582 DESCRIPTION 1583 "Bridge level Transparent Bridging data." 1584 ::= { dot1dGroups 6 } 1586 dot1dTpFdbGroup OBJECT-GROUP 1587 OBJECTS { 1588 dot1dTpFdbAddress, 1589 dot1dTpFdbPort, 1590 dot1dTpFdbStatus 1591 } 1592 STATUS current 1593 DESCRIPTION 1594 "Filtering Database information for the Bridge." 1595 ::= { dot1dGroups 7 } 1597 dot1dTpGroup OBJECT-GROUP 1598 OBJECTS { 1599 dot1dTpPort, 1600 dot1dTpPortMaxInfo, 1601 dot1dTpPortInFrames, 1602 dot1dTpPortOutFrames, 1603 dot1dTpPortInDiscards 1604 } 1605 STATUS current 1606 DESCRIPTION 1607 "Dynamic Filtering Database information for each port of 1608 the Bridge." 1609 ::= { dot1dGroups 8 } 1611 -- ---------------------------------------------------------- -- 1612 -- The Static (Destination-Address Filtering) Database 1613 -- ---------------------------------------------------------- -- 1615 dot1dStaticGroup OBJECT-GROUP 1616 OBJECTS { 1617 dot1dStaticAddress, 1618 dot1dStaticReceivePort, 1619 dot1dStaticAllowedToGoTo, 1620 dot1dStaticStatus 1621 } 1622 STATUS current 1623 DESCRIPTION 1624 "Static Filtering Database information for each port of 1625 the Bridge." 1626 ::= { dot1dGroups 9 } 1628 -- ---------------------------------------------------------- -- 1629 -- The Trap Notfication Group 1630 -- ---------------------------------------------------------- -- 1632 dot1dNotificationGroup NOTIFICATION-GROUP 1633 NOTIFICATIONS { 1634 newRoot, 1635 topologyChange 1636 } 1637 STATUS current 1638 DESCRIPTION 1639 "Group of objects describing notifications (traps)." 1640 ::= { dot1dGroups 10 } 1642 -- ---------------------------------------------------------- -- 1643 -- compliance statements 1644 -- ---------------------------------------------------------- -- 1646 bridgeCompliance MODULE-COMPLIANCE 1647 STATUS deprecated 1648 DESCRIPTION 1649 "The compliance statement for device support of bridging 1650 services. As per RFC1493" 1652 MODULE 1653 MANDATORY-GROUPS { 1654 dot1dBaseBridgeGroup, 1655 dot1dBasePortGroup 1656 } 1658 GROUP dot1dStpBridgeGroup 1659 DESCRIPTION 1660 "Implementation of this group is mandatory for bridges 1661 that support the Spanning Tree Protocol." 1663 GROUP dot1dStpPortGroup 1664 DESCRIPTION 1665 "Implementation of this group is mandatory for bridges 1666 that support the Spanning Tree Protocol." 1668 GROUP dot1dTpBridgeGroup 1669 DESCRIPTION 1670 "Implementation of this group is mandatory for bridges 1671 that support the transparent bridging mode. A 1672 transparent or SRT bridge will implement this group." 1674 GROUP dot1dTpFdbGroup 1675 DESCRIPTION 1676 "Implementation of this group is mandatory for bridges 1677 that support the transparent bridging mode. A 1678 transparent or SRT bridge will implement this group." 1680 GROUP dot1dTpGroup 1681 DESCRIPTION 1682 "Implementation of this group is mandatory for bridges 1683 that support the transparent bridging mode. A 1684 transparent or SRT bridge will implement this group." 1686 GROUP dot1dStaticGroup 1687 DESCRIPTION 1688 "Implementation of this group is optional." 1690 GROUP dot1dNotificationGroup 1691 DESCRIPTION 1692 "Implementation of this group is optional." 1693 ::= { dot1dCompliances 1 } 1695 bridgeCompliance2 MODULE-COMPLIANCE 1696 STATUS current 1697 DESCRIPTION 1698 "The compliance statement for device support of bridging 1699 services. This supports 32-bit Path Cost values and the 1700 more restricted bridge and port priorities, as per IEEE 1701 802.1t." 1703 MODULE 1704 MANDATORY-GROUPS { 1705 dot1dBaseBridgeGroup, 1706 dot1dBasePortGroup 1707 } 1709 GROUP dot1dStpBridgeGroup 1710 DESCRIPTION 1711 "Implementation of this group is mandatory for 1712 bridges that support the Spanning Tree Protocol." 1714 OBJECT dot1dStpPriority 1715 SYNTAX Integer32 (0|4096|8192|12288|16384|20480|24576 1716 |28672|32768|36864|40960|45056|49152 1717 |53248|57344|61440) 1718 DESCRIPTION 1719 "All possible values as per IEEE 802.1t." 1721 GROUP dot1dStpPortGroup2 1722 DESCRIPTION 1723 "Implementation of this group is mandatory for 1724 bridges that support the Spanning Tree Protocol." 1726 OBJECT dot1dStpPortPriority 1727 SYNTAX Integer32 (0|16|32|48|64|80|96|112|128 1728 |144|160|176|192|208|224|240) 1729 DESCRIPTION 1730 "All possible values as per IEEE 802.1t." 1732 GROUP dot1dTpBridgeGroup 1733 DESCRIPTION 1734 "Implementation of this group is mandatory for 1735 bridges that support the transparent bridging 1736 mode. A transparent or SRT bridge will implement 1737 this group." 1739 GROUP dot1dTpFdbGroup 1740 DESCRIPTION 1741 "Implementation of this group is mandatory for 1742 bridges that support the transparent bridging 1743 mode. A transparent or SRT bridge will implement 1744 this group." 1746 GROUP dot1dTpGroup 1747 DESCRIPTION 1748 "Implementation of this group is mandatory for 1749 bridges that support the transparent bridging 1750 mode. A transparent or SRT bridge will implement 1751 this group." 1753 GROUP dot1dStaticGroup 1754 DESCRIPTION 1755 "Implementation of this group is optional." 1757 GROUP dot1dNotificationGroup 1758 DESCRIPTION 1759 "Implementation of this group is optional." 1761 ::= { dot1dCompliances 2 } 1763 END 1765 4. Security Considerations 1767 There are a number of management objects defined in this MIB that 1768 have a MAX-ACCESS clause of read-write and/or read-create. Such 1769 objects may be considered sensitive or vulnerable in some network 1770 environments. The support for SET operations in a non-secure 1771 environment without proper protection can have a negative effect on 1772 network operations. 1774 SNMPv1 by itself is not a secure environment. Even if the network 1775 itself is secure (for example by using IPSec), even then, there is no 1776 control as to who on the secure network is allowed to access and 1777 GET/SET (read/change/create/delete) the objects in this MIB. 1779 It is recommended that the implementers consider the security 1780 features as provided by the SNMPv3 framework. Specifically, the use 1781 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1782 based Access Control Model RFC 2575 [RFC2575] is recommended. 1784 It is then a customer/user responsibility to ensure that the SNMP 1785 entity giving access to an instance of this MIB, is properly 1786 configured to give access to the objects only to those principals 1787 (users) that have legitimate rights to indeed GET or SET 1788 (change/create/delete) them. 1790 5. Acknowledgments 1792 The MIB presented in this memo is a direct translation of the BRIDGE 1793 MIB defined in [RFC1493], to the SMIv2 syntax required for current 1794 IETF MIB standards. 1796 The original authors were E. Decker, P. Langille, A Rijsinghani and 1797 K. McCloghrie. Further acknowledgement is given to the members of 1798 the original Bridge Working Group in [RFC1493]. 1800 This document was produced on behalf of the Bridge MIB Working Group 1801 in the Operations and Management area of the Internet Engineering 1802 Task Force. 1804 The authors wish to thank the members of the Bridge MIB Working Group 1805 , especially Mike MacFadden and Bert Visscher for their many comments 1806 and suggestions which improved this effort. 1808 6. References 1810 Normative References 1812 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1813 "Protocol Operations for Version 2 of the Simple Network 1814 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1816 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1817 for Describing SNMP Management Frameworks", RFC 2571, April 1818 1999. 1820 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1821 Processing and Dispatching for the Simple Network Management 1822 Protocol (SNMP)", RFC 2572, April 1999. 1824 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1825 RFC 2573, April 1999. 1827 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1828 (USM) for version 3 of the Simple Network Management 1829 Protocol (SNMPv3)", RFC 2574, April 1999. 1831 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1832 Access Control Model (VACM) for the Simple Network 1833 Management Protocol (SNMP)", RFC 2575, April 1999. 1835 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1836 Rose, M., and S. Waldbusser, "Structure of Management 1837 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1838 1999. 1840 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1841 Rose, M., and S. Waldbusser, "Textual Conventions for 1842 SMIv2", STD 58, RFC 2579, April 1999. 1844 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1845 Rose, M., and S. Waldbusser, "Conformance Statements for 1846 SMIv2", STD 58, RFC 2580, April 1999. 1848 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1849 MIB", RFC 2863, June 2000. 1851 [IEEE8021D] ANSI/IEEE Standard 802.1D-1998 MAC Bridges, IEEE Project 802 1852 Local and Metropolitan Area Networks, (March 8, 1998). 1854 [ISO8021D] ISO DIS 10038 MAC Bridges. 1856 Informative References 1858 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1859 of Management Information for TCP/IP-based Internets", STD 1860 16, RFC 1155, May 1990. 1862 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1863 Network Management Protocol", STD 15, RFC 1157, May 1990. 1865 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1866 16, RFC 1212, March 1991. 1868 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1869 SNMP", RFC 1215, March 1991. 1871 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1872 "Introduction to Community-based SNMPv2", RFC 1901, January 1873 1996. 1875 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1876 "Transport Mappings for Version 2 of the Simple Network 1877 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1879 [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1880 "Management Information Base for Version 2 of the Simple 1881 Network Management Protocol (SNMPv2)", RFC 1907, January 1882 1996. 1884 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1885 "Introduction to Version 3 of the Internet-standard Network 1886 Management Framework", RFC 2570, April 1999. 1888 7. Changes from RFC 1493 1890 The following changes have been made from RFC 1493. 1892 (1) Translated the MIB definition to use SMIv2. 1894 (2) Updated the SNMP Framework and references to comply with the 1895 current IETF guidelines. 1897 (3) Updated the Security section to comply with current IETF 1898 guidelines. 1900 The following chnages have been made from 1901 draft-ietf-bridge-bridgemib-smiv2-00.txt 1903 (1) Misc. description refernces to IEEE 802.1d documents 1905 (2) dot1dNotificationGroup changed from dot1dTrapGroup 1907 (3) Misc. additions to some descriptions 1909 The following chnages have been made from 1910 draft-ietf-bridge-bridgemib-smiv2-01.txt 1912 (1) corrections to objects that were made not-accessible in the 1913 draft-00 version that were read /read-write in rfc 1493 1915 (2) Misc. additions to some descriptions 1917 The following chnages have been made from 1918 draft-ietf-bridge-bridgemib-smiv2-02.txt 1920 (1) Updated references of IEEE 802.1d draft from 1921 1990 document to 1998 document. 1923 The following chnages have been made from 1924 draft-ietf-bridge-bridgemib-smiv2-03.txt 1926 (1) Adapted the current conformance statement. 1928 8. Authors' Addresses 1930 K.C. Norseth 1931 L-3 Communications 1932 640 N. 2200 West. 1933 Salt Lake City, Utah 84116-0850 1934 Email: kenyon.c.norseth@L-3com.com 1935 kcn@norseth.com 1937 Les Bell 1938 3Com Europe Limited 1939 3Com Centre, Boundary Way 1940 Hemel Hempstead 1941 Herts. HP2 7YU 1942 UK 1944 Phone: +44 1442 438025 1945 Email: Les_Bell@3Com.com 1947 9. Full Copyright 1949 Copyright (C) The Internet Society (2001). All Rights Reserved. 1951 This document and translations of it may be copied and furnished to 1952 others, and derivative works that comment on or otherwise explain it 1953 or assist in its implmentation may be prepared, copied, published and 1954 distributed, in whole or in part, without restriction of any kind, 1955 provided that the above copyright notice and this paragraph are 1956 included on all such copies and derivative works. However, this 1957 document itself may not be modified in any way, such as by removing 1958 the copyright notice or references to the Internet Society or other 1959 Internet organizations, except as needed for the purpose of 1960 developing Internet standards in which case the procedures for 1961 copyrights defined in the Internet Standards process must be 1962 followed, or as required to translate it into languages other than 1963 English. 1965 The limited permissions granted above are perpetual and will not be 1966 revoked by the Internet Society or its successors or assigns. 1968 This document and the information contained herein is provided on an 1969 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1970 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1971 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1972 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1973 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1975 Table of Contents 1976 1. The SNMP Management Framework 2 1977 2. Overview 3 1978 2.1. Structure of MIB 3 1979 2.1.1. The dot1dBase Group 5 1980 2.1.2. The dot1dStp Group 5 1981 2.1.3. The dot1dSr Group 5 1982 2.1.4. The dot1dTp Group 6 1983 2.1.5. The dot1dStatic Group 6 1984 2.2. Relationship to Other MIBs 6 1985 2.2.1. Relationship to the 'system' group 6 1986 2.2.2. Relationship to the 'interfaces' group 6 1987 2.3. Textual Conventions 7 1988 3. Definitions 7 1989 4. Security Considerations 33 1990 5. Acknowledgments 34 1991 6. References 34 1992 7. Changes from RFC 1493 36 1993 8. Authors' Addresses 36 1994 9. Full Copyright 37