idnits 2.17.1 draft-ietf-bridge-bridgemib-smiv2-01.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 (November 2001) is 8199 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 1692, 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 1767, 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 May 2002 K.C. Norseth 3 draft-ietf-bridge-bridgemib-smiv2-01.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 November 2001 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 (2001). 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. 53 In particular it defines objects for managing MAC bridges based on 54 the IEEE 802.1D-1990 standard between Local Area Network (LAN) 55 segments. Provisions are made for support of transparent bridging. 56 Provisions are also made so that these objects apply to bridges 57 connected by subnetworks other than LAN segments. 59 The MIB presented in this memo is a direct translation of the BRIDGE 60 MIB defined in [RFC1493], to the SMIv2 syntax required for current 61 IETF MIB standards. This memo obsoletes RFC 1493. 63 1. The SNMP Management Framework 65 The SNMP Management Framework presently consists of five major 66 components: 68 o An overall architecture, described in RFC 2571 [RFC2571]. 70 o Mechanisms for describing and naming objects and events for the 71 purpose of management. The first version of this Structure of 72 Management Information (SMI) is called SMIv1 and described in 73 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 74 1215 [RFC1215]. The second version, called SMIv2, is described 75 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 76 STD 58, RFC 2580 [RFC2580]. 78 o Message protocols for transferring management information. The 79 first version of the SNMP message protocol is called SNMPv1 and 80 described in STD 15, RFC 1157 [RFC1157]. A second version of 81 the SNMP message protocol, which is not an Internet standards 82 track protocol, is called SNMPv2c and described in RFC 1901 83 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 84 message protocol is called SNMPv3 and described in RFC 1906 85 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 87 o Protocol operations for accessing management information. The 88 first set of protocol operations and associated PDU formats is 89 described in STD 15, RFC 1157 [RFC1157]. A second set of 90 protocol operations and associated PDU formats is described in 91 RFC 1905 [RFC1905]. 93 o A set of fundamental applications described in RFC 2573 94 [RFC2573] and the view-based access control mechanism described 95 in RFC 2575 [RFC2575]. 97 A more detailed introduction to the current SNMP Management Framework 98 can be found in RFC 2570 [RFC2570]. 100 Managed objects are accessed via a virtual information store, termed 101 the Management Information Base or MIB. Objects in the MIB are 102 defined using the mechanisms defined in the SMI. 104 This memo specifies a MIB module that is compliant to the SMIv2. A 105 MIB conforming to the SMIv1 can be produced through the appropriate 106 translations. The resulting translated MIB must be semantically 107 equivalent, except where objects or events are omitted because no 108 translation is possible (use of Counter64). Some machine readable 109 information in SMIv2 will be converted into textual descriptions in 110 SMIv1 during the translation process. However, this loss of machine 111 readable information is not considered to change the semantics of the 112 MIB. 114 2. Overview 116 A common device present in many networks is the Bridge. This device 117 is used to connect Local Area Network segments below the network 118 layer. 120 There are two major modes defined for this bridging; transparent and 121 source route. The transparent method of bridging is defined in the 122 IEEE 802.1D specification [IEEE8021D]. This memo defines those 123 objects needed for the management of a bridging entity operating in 124 the transparent mode, as well as some objects applicable to all types 125 of bridges. 127 To be consistent with IAB directives and good engineering practice, 128 an explicit attempt was made to keep this MIB as simple as possible. 129 This was accomplished by applying the following criteria to objects 130 proposed for inclusion: 132 (1) Start with a small set of essential objects and add only as 133 further objects are needed. 135 (2) Require objects be essential for either fault or configuration 136 management. 138 (3) Consider evidence of current use and/or utility. 140 (4) Limit the total of objects. 142 (5) Exclude objects which are simply derivable from others in this 143 or other MIBs. 145 (6) Avoid causing critical sections to be heavily instrumented. The 146 guideline that was followed is one counter per critical section 147 per layer. 149 2.1. Structure of MIB 151 Objects in this MIB are arranged into groups. Each group is 152 organized as a set of related objects. The overall structure and 153 assignment of objects to their groups is shown below. Where 154 appropriate the corresponding IEEE 802.1D [IEEE8021D] management 155 object name is also included. 157 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 -- ---------------------------------------------------------- -- 363 IMPORTS 364 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 365 Counter32, Integer32, TimeTicks, mib-2 366 FROM SNMPv2-SMI 367 TEXTUAL-CONVENTION, MacAddress 368 FROM SNMPv2-TC 369 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 370 FROM SNMPv2-CONF 372 ; 374 bridgeMIB MODULE-IDENTITY 375 LAST-UPDATED "200111180000Z" 376 ORGANIZATION "IETF Bridge MIB Working Group" 377 CONTACT-INFO 378 "Email: Bridge-mib@ietf.org" 379 DESCRIPTION 380 "The Bridge MIB module for managing devices that support 381 IEEE 802.1D." 382 REVISION "200111190000Z" 383 DESCRIPTION 384 "Draft 1: 01 version of draft." 385 REVISION "200106260000Z" 386 DESCRIPTION 387 "Draft 1: initial translation of RFC 1493 to SMIv2." 388 REVISION "199307310000Z" 389 DESCRIPTION 390 "RFC 1493: SMIv1 version." 391 ::= { dot1dBridge 8 } 393 dot1dNotification OBJECT IDENTIFIER ::= { dot1dBridge 0 } 395 -- ---------------------------------------------------------- -- 396 -- Textual Conventions 397 -- ---------------------------------------------------------- -- 399 -- All representations of MAC addresses in this MIB Module use, 400 -- as a textual convention (i.e. this convention does not affect 401 -- their encoding), the data type MacAddress, defined in 402 -- SNMPv2-TC. 404 -- Similarly, all representations of Bridge-Id in this MIB 405 -- Module use, as a textual convention (i.e. this convention 406 -- does not affect their encoding), the data type: 408 BridgeId ::= TEXTUAL-CONVENTION 409 STATUS current 410 DESCRIPTION 411 "The Bridge-Identifier as used in the Spanning Tree 412 Protocol to uniquely identify a bridge. Its first two 413 octets (in network byte order) contain a priority value 414 and its last 6 octets contain the MAC address used to 415 refer to a bridge in a unique fashion (typically, the 416 numerically smallest MAC address of all ports on the 417 bridge)." 418 SYNTAX OCTET STRING (SIZE (8)) 420 -- Several objects in this MIB module represent values of timers 421 -- used by the Spanning Tree Protocol. In this MIB, these 422 -- timers have values in units of hundreths of a second (i.e. 423 -- 1/100 secs). 424 -- These timers, when stored in a Spanning Tree Protocol's BPDU, 425 -- are in units of 1/256 seconds. Note, however, that 426 -- 802.1D-1990 specifies a settable granularity of no more 427 -- than 1 second for these timers. To avoid ambiguity, a data 428 -- type is defined here as a textual convention and all 429 -- representation of these timers in this MIB module are defined 430 -- using this data type. An algorithm is also defined for 431 -- converting between the different units, to ensure a timer's 432 -- value is not distorted by multiple conversions. 433 -- The data type is: 435 Timeout ::= TEXTUAL-CONVENTION 436 STATUS current 437 DESCRIPTION 438 "A STP timer in units of 1/100 seconds. 439 To convert a Timeout value into a value in units of 440 1/256 seconds, the following algorithm should be used: 442 b = floor( (n * 256) / 100) 444 where: 445 floor = quotient [ignore remainder] 446 n is the value in 1/100 second units 447 b is the value in 1/256 second units 449 To convert the value from 1/256 second units back to 450 1/100 seconds, the following algorithm should be used: 452 n = ceiling( (b * 100) / 256) 454 where: 455 ceiling = quotient [if remainder is 0], or 456 quotient + 1 [if remainder is non-zero] 457 n is the value in 1/100 second units 458 b is the value in 1/256 second units 460 Note: it is important that the arithmetic operations are 461 done in the order specified (i.e., multiply first, 462 divide second)." 463 SYNTAX Integer32 465 -- ---------------------------------------------------------- -- 467 dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 } 469 -- ---------------------------------------------------------- -- 470 -- groups in the Bridge MIB 471 -- ---------------------------------------------------------- -- 473 dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 } 474 dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 } 476 dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 } 477 -- separately documented 478 dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 } 479 dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 } 481 -- Groups defined in the Bridge Mib Extensions: 482 -- pBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 6 } 483 -- qBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 7 } 485 -- The MODULE-IDENTITY for this MIB has been defined above as: 486 -- bridgeMIB MODULE-IDENTITY ::= { dot1dBridge 8 } 488 -- The MODULE-IDENTITY for the Source Routing MIB has been 489 -- defined in that MIB as: 490 -- srMIB MODULE-IDENTITY ::= { dot1dBridge 9 } 492 -- Groups defined in the Source Routing MIB: 493 -- dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 } 495 dot1dConformance OBJECT IDENTIFIER ::= { bridgeMIB 1 } 497 -- ---------------------------------------------------------- -- 498 -- the dot1dBase group 499 -- ---------------------------------------------------------- -- 500 -- Implementation of the dot1dBase group is mandatory for all 501 -- bridges. 502 -- ---------------------------------------------------------- -- 504 dot1dBaseBridgeAddress OBJECT-TYPE 505 SYNTAX MacAddress 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "The MAC address used by this bridge when it must be 510 referred to in a unique fashion. It is recommended 511 that this be the numerically smallest MAC address of all 512 ports that belong to this bridge. However it is only 513 required to be unique. When concatenated with 514 dot1dStpPriority a unique BridgeIdentifier is formed 515 which is used in the Spanning Tree Protocol." 516 REFERENCE 517 "IEEE 802.1D-1990: Sections 6.4.1.1.3 and 3.12.5" 518 ::= { dot1dBase 1 } 520 dot1dBaseNumPorts OBJECT-TYPE 521 SYNTAX Integer32 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "The number of ports controlled by this bridging 526 entity." 527 REFERENCE 528 "IEEE 802.1D-1990: Section 6.4.1.1.3" 529 ::= { dot1dBase 2 } 531 dot1dBaseType OBJECT-TYPE 532 SYNTAX INTEGER { 533 unknown(1), 534 transparentOnly(2), 535 sourcerouteOnly(3), 536 srt(4) 537 } 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "Indicates what type of bridging this bridge can 542 perform. If a bridge is actually performing a 543 certain type of bridging this will be indicated by 544 entries in the port table for the given type." 545 ::= { dot1dBase 3 } 547 -- ---------------------------------------------------------- -- 548 -- The Generic Bridge Port Table 549 -- ---------------------------------------------------------- -- 551 dot1dBasePortTable OBJECT-TYPE 552 SYNTAX SEQUENCE OF Dot1dBasePortEntry 553 MAX-ACCESS not-accessible 554 STATUS current 555 DESCRIPTION 556 "A table that contains generic information about every 557 port that is associated with this bridge. Transparent, 558 source-route, and srt ports are included." 560 ::= { dot1dBase 4 } 562 dot1dBasePortEntry OBJECT-TYPE 563 SYNTAX Dot1dBasePortEntry 564 MAX-ACCESS not-accessible 565 STATUS current 566 DESCRIPTION 567 "A list of information for each port of the bridge." 568 REFERENCE 569 "IEEE 802.1D-1990: Section 6.4.2, 6.6.1" 570 INDEX { dot1dBasePort } 571 ::= { dot1dBasePortTable 1 } 573 Dot1dBasePortEntry ::= 574 SEQUENCE { 575 dot1dBasePort 576 Integer32, 577 dot1dBasePortIfIndex 578 Integer32, 579 dot1dBasePortCircuit 580 OBJECT IDENTIFIER, 581 dot1dBasePortDelayExceededDiscards 582 Counter32, 583 dot1dBasePortMtuExceededDiscards 584 Counter32 586 } 588 dot1dBasePort OBJECT-TYPE 589 SYNTAX Integer32 (1..65535) 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "The port number of the port for which this entry 594 contains bridge management information." 595 ::= { dot1dBasePortEntry 1 } 597 dot1dBasePortIfIndex OBJECT-TYPE 598 SYNTAX InterfaceIndex 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "The value of the instance of the ifIndex object, 603 defined in MIB-II, for the interface corresponding 604 to this port." 605 ::= { dot1dBasePortEntry 2 } 607 dot1dBasePortCircuit OBJECT-TYPE 608 SYNTAX OBJECT IDENTIFIER 609 MAX-ACCESS read-only 610 STATUS current 612 DESCRIPTION 613 "For a port which (potentially) has the same value of 614 dot1dBasePortIfIndex as another port on the same bridge, 615 this object contains the name of an object instance 616 unique to this port. For example, in the case where 617 multiple ports correspond one- to-one with multiple X.25 618 virtual circuits, this value might identify an (e.g., 619 the first) object instance associated with the X.25 620 virtual circuit corresponding to this port. 622 For a port which has a unique value of 623 dot1dBasePortIfIndex, this object can have the value 624 { 0 0 }." 625 ::= { dot1dBasePortEntry 3 } 627 dot1dBasePortDelayExceededDiscards OBJECT-TYPE 628 SYNTAX Counter32 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "The number of frames discarded by this port due 633 to excessive transit delay through the bridge. It 634 is incremented by both transparent and source 635 route bridges." 636 REFERENCE 637 "IEEE 802.1D-1990: Section 6.6.1.1.3" 638 ::= { dot1dBasePortEntry 4 } 640 dot1dBasePortMtuExceededDiscards OBJECT-TYPE 641 SYNTAX Counter32 642 MAX-ACCESS read-only 643 STATUS current 644 DESCRIPTION 645 "The number of frames discarded by this port due 646 to an excessive size. It is incremented by both 647 transparent and source route bridges." 648 REFERENCE 649 "IEEE 802.1D-1990: Section 6.6.1.1.3" 650 ::= { dot1dBasePortEntry 5 } 652 -- ---------------------------------------------------------- -- 653 -- the dot1dStp group 654 -- ---------------------------------------------------------- -- 655 -- Implementation of the dot1dStp group is optional. It is 656 -- implemented by those bridges that support the Spanning Tree 657 -- Protocol. 658 -- ---------------------------------------------------------- -- 660 dot1dStpProtocolSpecification OBJECT-TYPE 661 SYNTAX INTEGER { 662 unknown(1), 663 decLb100(2), 664 ieee8021d(3) 665 } 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "An indication of what version of the Spanning Tree 670 Protocol is being run. The value 'decLb100(2)' 671 indicates the DEC LANbridge 100 Spanning Tree protocol. 672 IEEE 802.1D implementations will return 'ieee8021d(3)'. 673 If future versions of the IEEE Spanning Tree Protocol 674 are released that are incompatible with the current 675 version a new value will be defined." 676 ::= { dot1dStp 1 } 678 dot1dStpPriority OBJECT-TYPE 679 SYNTAX Integer32 (0..65535) 680 MAX-ACCESS read-write 681 STATUS current 682 DESCRIPTION 683 "The value of the write-able portion of the Bridge ID, 684 i.e., the first two octets of the (8 octet long) Bridge 685 ID. The other (last) 6 octets of the Bridge ID are 686 given by the value of dot1dBaseBridgeAddress. 687 Permissible values are 0-61440, in steps of 4096." 688 REFERENCE 689 " IEEE 802.1t clause 8.10.2, Table 8-4, clause 14.3."" 690 ::= { dot1dStp 2 } 692 dot1dStpTimeSinceTopologyChange OBJECT-TYPE 693 SYNTAX TimeTicks 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "The time (in hundredths of a second) since the 698 last time a topology change was detected by the 699 bridge entity. 700 For RSTP, this reports the time since the tcWhile timer for 701 any port on this Bridge was non-zero." 702 REFERENCE 703 " IEEE 802.1w clause 14.8.1.1." 704 ::= { dot1dStp 3 } 706 dot1dStpTopChanges OBJECT-TYPE 707 SYNTAX Counter32 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "The total number of topology changes detected by 712 this bridge since the management entity was last 713 reset or initialized. 714 For RSTP, this reports the count of times that there have 715 been at least one non-zero tcWhile timer on this Bridge." 716 REFERENCE 717 " IEEE 802.1w clause 14.8.1.1." 718 ::= { dot1dStp 4 } 720 dot1dStpDesignatedRoot OBJECT-TYPE 721 SYNTAX BridgeId 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "The bridge identifier of the root of the spanning 726 tree as determined by the Spanning Tree Protocol 727 as executed by this node. This value is used as 728 the Root Identifier parameter in all Configuration 729 Bridge PDUs originated by this node." 730 REFERENCE 731 "IEEE 802.1D-1990: Section 4.5.3.1" 732 ::= { dot1dStp 5 } 734 dot1dStpRootCost OBJECT-TYPE 735 SYNTAX Integer32 736 MAX-ACCESS read-only 737 STATUS current 738 DESCRIPTION 739 "The cost of the path to the root as seen from 740 this bridge." 741 REFERENCE 742 "IEEE 802.1D-1990: Section 4.5.3.2" 743 ::= { dot1dStp 6 } 745 dot1dStpRootPort OBJECT-TYPE 746 SYNTAX Integer32 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "The port number of the port which offers the lowest 751 cost path from this bridge to the root bridge." 752 REFERENCE 753 "IEEE 802.1D-1990: Section 4.5.3.3" 754 ::= { dot1dStp 7 } 756 dot1dStpMaxAge OBJECT-TYPE 757 SYNTAX Timeout 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "The maximum age of Spanning Tree Protocol information 762 learned from the network on any port before it is 763 discarded, in units of hundredths of a second. This is 764 the actual value that this bridge is currently using." 765 REFERENCE 766 "IEEE 802.1D-1990: Section 4.5.3.4" 767 ::= { dot1dStp 8 } 769 dot1dStpHelloTime OBJECT-TYPE 770 SYNTAX Timeout 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "The amount of time between the transmission of 775 Configuration bridge PDUs by this node on any port when 776 it is the root of the spanning tree or trying to become 777 so, in units of hundredths of a second. This is the 778 actual value that this bridge is currently using." 779 REFERENCE 780 "IEEE 802.1D-1990: Section 4.5.3.5" 781 ::= { dot1dStp 9 } 783 dot1dStpHoldTime OBJECT-TYPE 784 SYNTAX Integer32 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "This time value determines the interval length 789 during which no more than two Configuration bridge 790 PDUs shall be transmitted by this node, in units 791 of hundredths of a second." 792 REFERENCE 793 "IEEE 802.1D-1990: Section 4.5.3.14" 794 ::= { dot1dStp 10 } 796 dot1dStpForwardDelay OBJECT-TYPE 797 SYNTAX Timeout 798 MAX-ACCESS read-only 799 STATUS current 800 DESCRIPTION 801 "This time value, measured in units of hundredths of a 802 second, controls how fast a port changes its spanning 803 state when moving towards the Forwarding state. The 804 value determines how long the port stays in each of the 805 Listening and Learning states, which precede the 806 Forwarding state. This value is also used, when a 807 topology change has been detected and is underway, to 808 age all dynamic entries in the Forwarding Database. 809 [Note that this value is the one that this bridge is 810 currently using, in contrast to 811 dot1dStpBridgeForwardDelay which is the value that this 812 bridge and all others would start using if/when this 813 bridge were to become the root.]" 814 REFERENCE 815 "IEEE 802.1D-1990: Section 4.5.3.6" 816 ::= { dot1dStp 11 } 818 dot1dStpBridgeMaxAge OBJECT-TYPE 819 SYNTAX Timeout (600..4000) 820 MAX-ACCESS read-write 821 STATUS current 822 DESCRIPTION 823 "The value that all bridges use for MaxAge when this 824 bridge is acting as the root. Note that 802.1D-1990 825 specifies that the range for this parameter is related 826 to the value of dot1dStpBridgeHelloTime. The 827 granularity of this timer is specified by 802.1D-1990 to 828 be 1 second. An agent may return a badValue error if a 829 set is attempted to a value which is not a whole number 830 of seconds." 831 REFERENCE 832 "IEEE 802.1D-1990: Section 4.5.3.8" 833 ::= { dot1dStp 12 } 835 dot1dStpBridgeHelloTime OBJECT-TYPE 836 SYNTAX Timeout (100..1000) 837 MAX-ACCESS read-write 838 STATUS current 839 DESCRIPTION 840 "The value that all bridges use for HelloTime when this 841 bridge is acting as the root. The granularity of this 842 timer is specified by 802.1D- 1990 to be 1 second. An 843 agent may return a badValue error if a set is attempted 844 to a value which is not a whole number of seconds." 845 REFERENCE 846 "IEEE 802.1D-1990: Section 4.5.3.9" 847 ::= { dot1dStp 13 } 849 dot1dStpBridgeForwardDelay OBJECT-TYPE 850 SYNTAX Timeout (400..3000) 851 MAX-ACCESS read-write 852 STATUS current 853 DESCRIPTION 854 "The value that all bridges use for ForwardDelay when 855 this bridge is acting as the root. Note that 856 802.1D-1990 specifies that the range for this parameter 857 is related to the value of dot1dStpBridgeMaxAge. The 858 granularity of this timer is specified by 802.1D-1990 to 859 be 1 second. An agent may return a badValue error if a 860 set is attempted to a value which is not a whole number 861 of seconds." 862 REFERENCE 863 "IEEE 802.1D-1990: Section 4.5.3.10" 864 ::= { dot1dStp 14 } 866 -- ---------------------------------------------------------- -- 867 -- The Spanning Tree Port Table 868 -- ---------------------------------------------------------- -- 870 dot1dStpPortTable OBJECT-TYPE 871 SYNTAX SEQUENCE OF Dot1dStpPortEntry 872 MAX-ACCESS not-accessible 873 STATUS current 874 DESCRIPTION 875 "A table that contains port-specific information 876 for the Spanning Tree Protocol." 877 ::= { dot1dStp 15 } 879 dot1dStpPortEntry OBJECT-TYPE 880 SYNTAX Dot1dStpPortEntry 881 MAX-ACCESS not-accessible 882 STATUS current 883 DESCRIPTION 884 "A list of information maintained by every port about 885 the Spanning Tree Protocol state for that port." 886 INDEX { dot1dStpPort } 887 ::= { dot1dStpPortTable 1 } 889 Dot1dStpPortEntry ::= 890 SEQUENCE { 891 dot1dStpPort 892 Integer32, 893 dot1dStpPortPriority 894 Integer32, 895 dot1dStpPortState 896 INTEGER, 897 dot1dStpPortEnable 898 INTEGER, 899 dot1dStpPortPathCost 900 Integer32, 901 dot1dStpPortDesignatedRoot 902 BridgeId, 903 dot1dStpPortDesignatedCost 904 Integer32, 905 dot1dStpPortDesignatedBridge 906 BridgeId, 907 dot1dStpPortDesignatedPort 908 OCTET STRING, 909 dot1dStpPortForwardTransitions 910 Counter32 911 } 913 dot1dStpPort OBJECT-TYPE 914 SYNTAX Integer32 (1..65535) 915 MAX-ACCESS not-accessible 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-1990: Section 6.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 Permissible values are 0-240, in steps of 16." 934 REFERENCE 935 " IEEE 802.1t clause 8.10.2, Table 8-4, clause 14.3." 936 ::= { dot1dStpPortEntry 2 } 938 dot1dStpPortState OBJECT-TYPE 939 SYNTAX INTEGER { 940 disabled(1), 941 blocking(2), 942 listening(3), 943 learning(4), 944 forwarding(5), 945 broken(6) 946 } 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "The port's current state as defined by application of 951 the Spanning Tree Protocol. This state controls what 952 action a port takes on reception of a frame. If the 953 bridge has detected a port that is malfunctioning it 954 will place that port into the broken(6) state. For 955 ports which are disabled (see dot1dStpPortEnable), this 956 object will have a value of disabled(1)." 957 REFERENCE 958 "IEEE 802.1D-1990: Section 4.5.5.2" 959 ::= { dot1dStpPortEntry 3 } 961 dot1dStpPortEnable OBJECT-TYPE 962 SYNTAX INTEGER { 963 enabled(1), 964 disabled(2) 965 } 966 MAX-ACCESS read-write 967 STATUS current 968 DESCRIPTION 969 "The enabled/disabled status of the port." 970 REFERENCE 971 "IEEE 802.1D-1990: Section 4.5.5.2" 972 ::= { dot1dStpPortEntry 4 } 974 dot1dStpPortPathCost OBJECT-TYPE 975 SYNTAX Integer32 (1..65535) 976 MAX-ACCESS read-write 977 STATUS current 978 DESCRIPTION 979 "The contribution of this port to the path cost of 980 paths towards the spanning tree root which include 981 this port. 802.1D-1990 recommends that the 982 default value of this parameter be in inverse 983 proportion to the speed of the attached LAN. 984 The permissible values must be extended to 1-200,000,000." 985 REFERENCE 986 " IEEE 802.1t clause 8.10.2, Table 8-5." 987 ::= { dot1dStpPortEntry 5 } 989 dot1dStpPortDesignatedRoot OBJECT-TYPE 990 SYNTAX BridgeId 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "The unique Bridge Identifier of the Bridge 995 recorded as the Root in the Configuration BPDUs 996 transmitted by the Designated Bridge for the 997 segment to which the port is attached." 998 REFERENCE 999 "IEEE 802.1D-1990: Section 4.5.5.4" 1000 ::= { dot1dStpPortEntry 6 } 1002 dot1dStpPortDesignatedCost OBJECT-TYPE 1003 SYNTAX Integer32 1004 MAX-ACCESS read-only 1005 STATUS current 1006 DESCRIPTION 1007 "The path cost of the Designated Port of the segment 1008 connected to this port. This value is compared to the 1009 Root Path Cost field in received bridge PDUs." 1010 REFERENCE 1011 "IEEE 802.1D-1990: Section 4.5.5.5" 1012 ::= { dot1dStpPortEntry 7 } 1014 dot1dStpPortDesignatedBridge OBJECT-TYPE 1015 SYNTAX BridgeId 1016 MAX-ACCESS read-only 1017 STATUS current 1018 DESCRIPTION 1019 "The Bridge Identifier of the bridge which this 1020 port considers to be the Designated Bridge for 1021 this port's segment." 1022 REFERENCE 1023 "IEEE 802.1D-1990: Section 4.5.5.6" 1024 ::= { dot1dStpPortEntry 8 } 1026 dot1dStpPortDesignatedPort OBJECT-TYPE 1027 SYNTAX OCTET STRING (SIZE (2)) 1028 MAX-ACCESS read-only 1029 STATUS current 1030 DESCRIPTION 1031 "The Port Identifier of the port on the Designated 1032 Bridge for this port's segment." 1033 REFERENCE 1034 "IEEE 802.1D-1990: Section 4.5.5.7" 1035 ::= { dot1dStpPortEntry 9 } 1037 dot1dStpPortForwardTransitions OBJECT-TYPE 1038 SYNTAX Counter32 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "The number of times this port has transitioned 1043 from the Learning state to the Forwarding state." 1044 ::= { dot1dStpPortEntry 10 } 1046 -- ---------------------------------------------------------- -- 1047 -- the dot1dTp group 1048 -- ---------------------------------------------------------- -- 1049 -- Implementation of the dot1dTp group is optional. It is 1050 -- implemented by those bridges that support the transparent 1051 -- bridging mode. A transparent or SRT bridge will implement 1052 -- this group. 1053 -- ---------------------------------------------------------- -- 1055 dot1dTpLearnedEntryDiscards OBJECT-TYPE 1056 SYNTAX Counter32 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "The total number of Forwarding Database entries, which 1061 have been or would have been learnt, but have been 1062 discarded due to a lack of space to store them in the 1063 Forwarding Database. If this counter is increasing, it 1064 indicates that the Forwarding Database is regularly 1065 becoming full (a condition which has unpleasant 1066 performance effects on the subnetwork). If this counter 1067 has a significant value but is not presently increasing, 1068 it indicates that the problem has been occurring but is 1069 not persistent." 1070 REFERENCE 1071 "IEEE 802.1D-1990: Section 6.7.1.1.3" 1073 ::= { dot1dTp 1 } 1075 dot1dTpAgingTime OBJECT-TYPE 1076 SYNTAX Integer32 (10..1000000) 1077 MAX-ACCESS read-write 1078 STATUS current 1079 DESCRIPTION 1080 "The timeout period in seconds for aging out 1081 dynamically learned forwarding information. 1082 802.1D-1990 recommends a default of 300 seconds." 1083 REFERENCE 1084 "IEEE 802.1D-1990: Section 6.7.1.1.3" 1085 ::= { dot1dTp 2 } 1087 -- ---------------------------------------------------------- -- 1088 -- The Forwarding Database for Transparent Bridges 1089 -- ---------------------------------------------------------- -- 1091 dot1dTpFdbTable OBJECT-TYPE 1092 SYNTAX SEQUENCE OF Dot1dTpFdbEntry 1093 MAX-ACCESS not-accessible 1094 STATUS current 1095 DESCRIPTION 1096 "A table that contains information about unicast 1097 entries for which the bridge has forwarding and/or 1098 filtering information. This information is used 1099 by the transparent bridging function in 1100 determining how to propagate a received frame." 1101 ::= { dot1dTp 3 } 1103 dot1dTpFdbEntry OBJECT-TYPE 1104 SYNTAX Dot1dTpFdbEntry 1105 MAX-ACCESS not-accessible 1106 STATUS current 1107 DESCRIPTION 1108 "Information about a specific unicast MAC address 1109 for which the bridge has some forwarding and/or 1110 filtering information." 1111 INDEX { dot1dTpFdbAddress } 1112 ::= { dot1dTpFdbTable 1 } 1114 Dot1dTpFdbEntry ::= 1115 SEQUENCE { 1116 dot1dTpFdbAddress 1117 MacAddress, 1118 dot1dTpFdbPort 1119 Integer32, 1120 dot1dTpFdbStatus 1121 INTEGER 1122 } 1124 dot1dTpFdbAddress OBJECT-TYPE 1125 SYNTAX MacAddress 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "A unicast MAC address for which the bridge has 1130 forwarding and/or filtering information." 1131 REFERENCE 1132 "IEEE 802.1D-1990: Section 3.9.1, 3.9.2" 1133 ::= { dot1dTpFdbEntry 1 } 1135 dot1dTpFdbPort OBJECT-TYPE 1136 SYNTAX Integer32 1137 MAX-ACCESS read-only 1138 STATUS current 1139 DESCRIPTION 1140 "Either the value '0', or the port number of the port on 1141 which a frame having a source address equal to the value 1142 of the corresponding instance of dot1dTpFdbAddress has 1143 been seen. A value of '0' indicates that the port 1144 number has not been learned but that the bridge does 1145 have some forwarding/filtering information about this 1146 address (e.g. in the dot1dStaticTable). Implementors 1147 are encouraged to assign the port value to this object 1148 whenever it is learned even for addresses for which the 1149 corresponding value of dot1dTpFdbStatus is not 1150 learned(3)." 1151 ::= { dot1dTpFdbEntry 2 } 1153 dot1dTpFdbStatus OBJECT-TYPE 1154 SYNTAX INTEGER { 1155 other(1), 1156 invalid(2), 1157 learned(3), 1158 self(4), 1159 mgmt(5) 1160 } 1161 MAX-ACCESS read-only 1162 STATUS current 1163 DESCRIPTION 1164 "The status of this entry. The meanings of the 1165 values are: 1166 other(1) - none of the following. This would 1167 include the case where some other MIB object 1168 (not the corresponding instance of 1169 dot1dTpFdbPort, nor an entry in the 1170 dot1dStaticTable) is being used to determine if 1171 and how frames addressed to the value of the 1172 corresponding instance of dot1dTpFdbAddress are 1173 being forwarded. 1174 invalid(2) - this entry is not longer valid (e.g., 1175 it was learned but has since aged-out), but has 1176 not yet been flushed from the table. 1177 learned(3) - the value of the corresponding instance 1178 of dot1dTpFdbPort was learned, and is being 1179 used. 1180 self(4) - the value of the corresponding instance of 1181 dot1dTpFdbAddress represents one of the bridge's 1182 addresses. The corresponding instance of 1183 dot1dTpFdbPort indicates which of the bridge's 1184 ports has this address. 1185 mgmt(5) - the value of the corresponding instance of 1186 dot1dTpFdbAddress is also the value of an 1187 existing instance of dot1dStaticAddress." 1188 ::= { dot1dTpFdbEntry 3 } 1190 -- ---------------------------------------------------------- -- 1191 -- Port Table for Transparent Bridges 1192 -- ---------------------------------------------------------- -- 1194 dot1dTpPortTable OBJECT-TYPE 1195 SYNTAX SEQUENCE OF Dot1dTpPortEntry 1196 MAX-ACCESS not-accessible 1197 STATUS current 1198 DESCRIPTION 1199 "A table that contains information about every port that 1200 is associated with this transparent bridge." 1201 ::= { dot1dTp 4 } 1203 dot1dTpPortEntry OBJECT-TYPE 1204 SYNTAX Dot1dTpPortEntry 1205 MAX-ACCESS not-accessible 1206 STATUS current 1207 DESCRIPTION 1208 "A list of information for each port of a transparent 1209 bridge." 1210 INDEX { dot1dTpPort } 1211 ::= { dot1dTpPortTable 1 } 1213 Dot1dTpPortEntry ::= 1214 SEQUENCE { 1215 dot1dTpPort 1216 Integer32, 1217 dot1dTpPortMaxInfo 1218 Integer32, 1219 dot1dTpPortInFrames 1220 Counter32, 1221 dot1dTpPortOutFrames 1222 Counter32, 1223 dot1dTpPortInDiscards 1224 Counter32 1225 } 1227 dot1dTpPort OBJECT-TYPE 1228 SYNTAX Integer32 (1..65535) 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "The port number of the port for which this entry 1233 contains Transparent bridging management information." 1234 ::= { dot1dTpPortEntry 1 } 1236 -- It would be nice if we could use ifMtu as the size of the 1237 -- largest INFO field, but we can't because ifMtu is defined 1238 -- to be the size that the (inter-)network layer can use which 1239 -- can differ from the MAC layer (especially if several layers 1240 -- of encapsulation are used). 1242 dot1dTpPortMaxInfo OBJECT-TYPE 1243 SYNTAX Integer32 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "The maximum size of the INFO (non-MAC) field that 1248 this port will receive or transmit." 1249 ::= { dot1dTpPortEntry 2 } 1251 dot1dTpPortInFrames OBJECT-TYPE 1252 SYNTAX Counter32 1253 MAX-ACCESS read-only 1254 STATUS current 1255 DESCRIPTION 1256 "The number of frames that have been received by this 1257 port from its segment. Note that a frame received on the 1258 interface corresponding to this port is only counted by 1259 this object if and only if it is for a protocol being 1260 processed by the local bridging function, including 1261 bridge management frames." 1262 REFERENCE 1263 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1264 ::= { dot1dTpPortEntry 3 } 1266 dot1dTpPortOutFrames OBJECT-TYPE 1267 SYNTAX Counter32 1268 MAX-ACCESS read-only 1269 STATUS current 1270 DESCRIPTION 1271 "The number of frames that have been transmitted by this 1272 port to its segment. Note that a frame transmitted on 1273 the interface corresponding to this port is only counted 1274 by this object if and only if it is for a protocol being 1275 processed by the local bridging function, including 1276 bridge management frames." 1277 REFERENCE 1278 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1279 ::= { dot1dTpPortEntry 4 } 1281 dot1dTpPortInDiscards OBJECT-TYPE 1282 SYNTAX Counter32 1283 MAX-ACCESS read-only 1284 STATUS current 1285 DESCRIPTION 1286 "Count of valid frames received which were discarded 1287 (i.e., filtered) by the Forwarding Process." 1288 REFERENCE 1289 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1290 ::= { dot1dTpPortEntry 5 } 1292 -- ---------------------------------------------------------- -- 1293 -- The Static (Destination-Address Filtering) Database 1294 -- ---------------------------------------------------------- -- 1295 -- Implementation of this group is optional. 1296 -- ---------------------------------------------------------- -- 1298 dot1dStaticTable OBJECT-TYPE 1299 SYNTAX SEQUENCE OF Dot1dStaticEntry 1300 MAX-ACCESS not-accessible 1301 STATUS current 1302 DESCRIPTION 1303 "A table containing filtering information configured 1304 into the bridge by (local or network) management 1305 specifying the set of ports to which frames received 1306 from specific ports and containing specific destination 1307 addresses are allowed to be forwarded. The value of 1308 zero in this table as the port number from which frames 1309 with a specific destination address are received, is 1310 used to specify all ports for which there is no specific 1311 entry in this table for that particular destination 1312 address. Entries are valid for unicast and for 1313 group/broadcast addresses." 1314 REFERENCE 1315 "IEEE 802.1D-1990: Section 6.7.2" 1316 ::= { dot1dStatic 1 } 1318 dot1dStaticEntry OBJECT-TYPE 1319 SYNTAX Dot1dStaticEntry 1320 MAX-ACCESS not-accessible 1321 STATUS current 1322 DESCRIPTION 1324 "Filtering information configured into the bridge by 1325 (local or network) management specifying the set of 1326 ports to which frames received from a specific port and 1327 containing a specific destination address are allowed to 1328 be forwarded." 1329 REFERENCE 1330 "IEEE 802.1D-1990: Section 6.7.2" 1331 INDEX { dot1dStaticAddress, dot1dStaticReceivePort } 1332 ::= { dot1dStaticTable 1 } 1334 Dot1dStaticEntry ::= 1335 SEQUENCE { 1336 dot1dStaticAddress 1337 MacAddress, 1338 dot1dStaticReceivePort 1339 Integer32, 1340 dot1dStaticAllowedToGoTo 1341 OCTET STRING, 1342 dot1dStaticStatus 1343 INTEGER 1344 } 1346 dot1dStaticAddress OBJECT-TYPE 1347 SYNTAX MacAddress 1348 MAX-ACCESS not-accessible 1349 STATUS current 1350 DESCRIPTION 1351 "The destination MAC address in a frame to which this 1352 entry's filtering information applies. This object can 1353 take the value of a unicast address, a group address or 1354 the broadcast address." 1355 REFERENCE 1356 "IEEE 802.1D-1990: Section 3.9.1, 3.9.2" 1357 ::= { dot1dStaticEntry 1 } 1359 dot1dStaticReceivePort OBJECT-TYPE 1360 SYNTAX Integer32 (1..65535) 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "Either the value '0', or the port number of the port 1365 from which a frame must be received in order for this 1366 entry's filtering information to apply. A value of zero 1367 indicates that this entry applies on all ports of the 1368 bridge for which there is no other applicable entry." 1369 ::= { dot1dStaticEntry 2 } 1371 dot1dStaticAllowedToGoTo OBJECT-TYPE 1373 SYNTAX OCTET STRING 1374 MAX-ACCESS read-write 1375 STATUS current 1376 DESCRIPTION 1377 "The set of ports to which frames received from a 1378 specific port and destined for a specific MAC address, 1379 are allowed to be forwarded. Each octet within the 1380 value of this object specifies a set of eight ports, 1381 with the first octet specifying ports 1 through 8, the 1382 second octet specifying ports 9 through 16, etc. Within 1383 each octet, the most significant bit represents the 1384 lowest numbered port, and the least significant bit 1385 represents the highest numbered port. Thus, each port 1386 of the bridge is represented by a single bit within the 1387 value of this object. If that bit has a value of '1' 1388 then that port is included in the set of ports; the port 1389 is not included if its bit has a value of '0'. (Note 1390 that the setting of the bit corresponding to the port 1391 from which a frame is received is irrelevant.) The 1392 default value of this object is a string of ones of 1393 appropriate length." 1394 ::= { dot1dStaticEntry 3 } 1396 dot1dStaticStatus OBJECT-TYPE 1397 SYNTAX INTEGER { 1398 other(1), 1399 invalid(2), 1400 permanent(3), 1401 deleteOnReset(4), 1402 deleteOnTimeout(5) 1403 } 1404 MAX-ACCESS read-write 1405 STATUS current 1406 DESCRIPTION 1407 "This object indicates the status of this entry. 1408 The default value is permanent(3). 1409 other(1) - this entry is currently in use but the 1410 conditions under which it will remain so are 1411 different from each of the following values. 1412 invalid(2) - writing this value to the object 1413 removes the corresponding entry. 1414 permanent(3) - this entry is currently in use and 1415 will remain so after the next reset of the 1416 bridge. 1417 deleteOnReset(4) - this entry is currently in use 1418 and will remain so until the next reset of the 1419 bridge. 1420 deleteOnTimeout(5) - this entry is currently in use 1421 and will remain so until it is aged out." 1422 ::= { dot1dStaticEntry 4 } 1424 -- ---------------------------------------------------------- -- 1425 -- Notifications for use by Bridges 1426 -- ---------------------------------------------------------- -- 1427 -- Notifications for the Spanning Tree Protocol 1428 -- ---------------------------------------------------------- -- 1430 newRoot NOTIFICATION-TYPE 1431 -- OBJECTS { } 1432 STATUS current 1433 DESCRIPTION 1434 "The newRoot trap indicates that the sending agent has 1435 become the new root of the Spanning Tree; the trap is 1436 sent by a bridge soon after its election as the new 1437 root, e.g., upon expiration of the Topology Change Timer 1438 immediately subsequent to its election. Implementation 1439 of this trap is optional." 1440 ::= { dot1dNotification 1 } 1442 topologyChange NOTIFICATION-TYPE 1443 -- OBJECTS { } 1444 STATUS current 1445 DESCRIPTION 1446 "A topologyChange trap is sent by a bridge when any of 1447 its configured ports transitions from the Learning state 1448 to the Forwarding state, or from the Forwarding state to 1449 the Blocking state. The trap is not sent if a newRoot 1450 trap is sent for the same transition. Implementation of 1451 this trap is optional." 1452 ::= { dot1dNotification 2 } 1454 -- ---------------------------------------------------------- -- 1455 -- IEEE 802.1D MIB - Conformance Information 1456 -- ---------------------------------------------------------- -- 1458 dot1dGroups OBJECT IDENTIFIER ::= { dot1dConformance 1 } 1459 dot1dCompliances OBJECT IDENTIFIER ::= { dot1dConformance 2 } 1461 -- ---------------------------------------------------------- -- 1462 -- units of conformance 1463 -- ---------------------------------------------------------- -- 1465 -- ---------------------------------------------------------- -- 1466 -- the dot1dBase group 1467 -- ---------------------------------------------------------- -- 1469 dot1dBaseBridgeGroup OBJECT-GROUP 1470 OBJECTS { 1471 dot1dBaseBridgeAddress, 1472 dot1dBaseNumPorts, 1473 dot1dBaseType 1474 } 1475 STATUS current 1476 DESCRIPTION 1477 "Bridge level information for this device." 1478 ::= { dot1dGroups 1 } 1480 dot1dBasePortGroup OBJECT-GROUP 1481 OBJECTS { 1482 dot1dBasePortIfIndex, 1483 dot1dBasePortCircuit, 1484 dot1dBasePortDelayExceededDiscards, 1485 dot1dBasePortMtuExceededDiscards 1486 } 1487 STATUS current 1488 DESCRIPTION 1489 "Information for each port on this device." 1490 ::= { dot1dGroups 2 } 1492 -- ---------------------------------------------------------- -- 1493 -- the dot1dStp group 1494 -- ---------------------------------------------------------- -- 1496 dot1dStpBridgeGroup OBJECT-GROUP 1497 OBJECTS { 1498 dot1dStpProtocolSpecification, 1499 dot1dStpPriority, 1500 dot1dStpTimeSinceTopologyChange, 1501 dot1dStpTopChanges, 1502 dot1dStpDesignatedRoot, 1503 dot1dStpRootCost, 1504 dot1dStpRootPort, 1505 dot1dStpMaxAge, 1506 dot1dStpHelloTime, 1507 dot1dStpHoldTime, 1508 dot1dStpForwardDelay, 1509 dot1dStpBridgeMaxAge, 1510 dot1dStpBridgeHelloTime, 1511 dot1dStpBridgeForwardDelay 1512 } 1513 STATUS current 1514 DESCRIPTION 1515 "Bridge level Spanning Tree data for this device." 1516 ::= { dot1dGroups 3 } 1518 dot1dStpPortGroup OBJECT-GROUP 1519 OBJECTS { 1520 dot1dStpPortPriority, 1521 dot1dStpPortState, 1522 dot1dStpPortEnable, 1523 dot1dStpPortPathCost, 1524 dot1dStpPortDesignatedRoot, 1525 dot1dStpPortDesignatedCost, 1526 dot1dStpPortDesignatedBridge, 1527 dot1dStpPortDesignatedPort, 1528 dot1dStpPortForwardTransitions 1529 } 1530 STATUS current 1531 DESCRIPTION 1532 "Spanning Tree data for each port on this device." 1533 ::= { dot1dGroups 4 } 1535 -- ---------------------------------------------------------- -- 1536 -- the dot1dTp group 1537 -- ---------------------------------------------------------- -- 1539 dot1dTpBridgeGroup OBJECT-GROUP 1540 OBJECTS { 1541 dot1dTpLearnedEntryDiscards, 1542 dot1dTpAgingTime 1543 } 1544 STATUS current 1545 DESCRIPTION 1546 "Bridge level Transparent Bridging data." 1547 ::= { dot1dGroups 5 } 1549 dot1dTpFdbGroup OBJECT-GROUP 1550 OBJECTS { 1551 dot1dTpFdbPort, 1552 dot1dTpFdbStatus 1553 } 1554 STATUS current 1555 DESCRIPTION 1556 "Filtering Database information for the Bridge." 1557 ::= { dot1dGroups 6 } 1559 dot1dTpGroup OBJECT-GROUP 1560 OBJECTS { 1561 dot1dTpPortMaxInfo, 1562 dot1dTpPortInFrames, 1563 dot1dTpPortOutFrames, 1564 dot1dTpPortInDiscards 1565 } 1566 STATUS current 1567 DESCRIPTION 1568 "Dynamic Filtering Database information for each port of 1569 the Bridge." 1570 ::= { dot1dGroups 7 } 1572 -- ---------------------------------------------------------- -- 1573 -- The Static (Destination-Address Filtering) Database 1574 -- ---------------------------------------------------------- -- 1576 dot1dStaticGroup OBJECT-GROUP 1577 OBJECTS { 1578 dot1dStaticAllowedToGoTo, 1579 dot1dStaticStatus 1580 } 1581 STATUS current 1582 DESCRIPTION 1583 "Static Filtering Database information for each port of 1584 the Bridge." 1585 ::= { dot1dGroups 8 } 1587 -- ---------------------------------------------------------- -- 1588 -- The Trap Notfication Group 1589 -- ---------------------------------------------------------- -- 1591 dot1dNotificationGroup NOTIFICATION-GROUP 1592 NOTIFICATIONS { 1593 newRoot, 1594 topologyChange 1595 } 1596 STATUS current 1597 DESCRIPTION 1598 "Group of objects describing notifications (traps)." 1599 ::= { dot1dGroups 9 } 1601 -- ---------------------------------------------------------- -- 1602 -- compliance statements 1603 -- ---------------------------------------------------------- -- 1605 bridgeCompliance MODULE-COMPLIANCE 1606 STATUS current 1607 DESCRIPTION 1608 "The compliance statement for device support of bridging 1609 services." 1611 MODULE 1612 MANDATORY-GROUPS { 1613 dot1dBaseBridgeGroup, 1614 dot1dBasePortGroup 1615 } 1617 GROUP dot1dStpBridgeGroup 1618 DESCRIPTION 1619 "Implementation of this group is mandatory for 1620 bridges that support the Spanning Tree Protocol." 1622 GROUP dot1dStpPortGroup 1623 DESCRIPTION 1624 "Implementation of this group is mandatory for 1625 bridges that support the Spanning Tree Protocol." 1627 GROUP dot1dTpBridgeGroup 1628 DESCRIPTION 1629 "Implementation of this group is mandatory for 1630 bridges that support the transparent bridging 1631 mode. A transparent or SRT bridge will implement 1632 this group." 1634 GROUP dot1dTpFdbGroup 1635 DESCRIPTION 1636 "Implementation of this group is mandatory for 1637 bridges that support the transparent bridging 1638 mode. A transparent or SRT bridge will implement 1639 this group." 1641 GROUP dot1dTpGroup 1642 DESCRIPTION 1643 "Implementation of this group is mandatory for 1644 bridges that support the transparent bridging 1645 mode. A transparent or SRT bridge will implement 1646 this group." 1648 GROUP dot1dStaticGroup 1649 DESCRIPTION 1650 "Implementation of this group is optional." 1652 GROUP dot1dNotificationGroup 1653 DESCRIPTION 1654 "Implementation of this group is optional." 1655 ::= { dot1dCompliances 1 } 1657 END 1659 4. Security Considerations 1661 There are a number of management objects defined in this MIB that 1662 have a MAX-ACCESS clause of read-write and/or read-create. Such 1663 objects may be considered sensitive or vulnerable in some network 1664 environments. The support for SET operations in a non-secure 1665 environment without proper protection can have a negative effect on 1666 network operations. 1668 SNMPv1 by itself is not a secure environment. Even if the network 1669 itself is secure (for example by using IPSec), even then, there is no 1670 control as to who on the secure network is allowed to access and 1671 GET/SET (read/change/create/delete) the objects in this MIB. 1673 It is recommended that the implementers consider the security 1674 features as provided by the SNMPv3 framework. Specifically, the use 1675 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1676 based Access Control Model RFC 2575 [RFC2575] is recommended. 1678 It is then a customer/user responsibility to ensure that the SNMP 1679 entity giving access to an instance of this MIB, is properly 1680 configured to give access to the objects only to those principals 1681 (users) that have legitimate rights to indeed GET or SET 1682 (change/create/delete) them. 1684 5. Acknowledgments 1686 The MIB presented in this memo is a direct translation of the BRIDGE 1687 MIB defined in [RFC1493], to the SMIv2 syntax required for current 1688 IETF MIB standards. 1690 The original authors were E. Decker, P. Langille, A Rijsinghani and 1691 K. McCloghrie. Further acknowledgement is given to the members of 1692 the original Bridge Working Group in [RFC1493]. 1694 This document was produced on behalf of the Bridge MIB Working Group 1695 in the Operations and Management area of the Internet Engineering 1696 Task Force. 1698 The authors wish to thank the members of the Bridge MIB Working Group 1699 for their many comments and suggestions which improved this effort. 1701 6. References 1703 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1704 for Describing SNMP Management Frameworks", RFC 2571, April 1705 1999. 1707 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1708 of Management Information for TCP/IP-based Internets", STD 1709 16, RFC 1155, May 1990. 1711 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1712 16, RFC 1212, March 1991. 1714 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1715 SNMP", RFC 1215, March 1991. 1717 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1718 Rose, M., and S. Waldbusser, "Structure of Management 1719 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1720 1999. 1722 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1723 Rose, M., and S. Waldbusser, "Textual Conventions for 1724 SMIv2", STD 58, RFC 2579, April 1999. 1726 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1727 Rose, M., and S. Waldbusser, "Conformance Statements for 1728 SMIv2", STD 58, RFC 2580, April 1999. 1730 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1731 Network Management Protocol", STD 15, RFC 1157, May 1990. 1733 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1734 "Introduction to Community-based SNMPv2", RFC 1901, January 1735 1996. 1737 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1738 "Transport Mappings for Version 2 of the Simple Network 1739 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1741 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1742 Processing and Dispatching for the Simple Network Management 1743 Protocol (SNMP)", RFC 2572, April 1999. 1745 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1746 (USM) for version 3 of the Simple Network Management 1747 Protocol (SNMPv3)", RFC 2574, April 1999. 1749 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1750 "Protocol Operations for Version 2 of the Simple Network 1751 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1753 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1754 RFC 2573, April 1999. 1756 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1757 Access Control Model (VACM) for the Simple Network 1758 Management Protocol (SNMP)", RFC 2575, April 1999. 1760 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1761 "Introduction to Version 3 of the Internet-standard Network 1762 Management Framework", RFC 2570, April 1999. 1764 [IEEE8021D] ANSI/IEEE Standard 802.1D-1990 MAC Bridges, IEEE Project 802 1765 Local and Metropolitan Area Networks, (March 8, 1991). 1767 [ISO8021D] ISO DIS 10038 MAC Bridges. 1769 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1770 MIB", RFC 2863, June 2000. 1772 [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1773 "Management Information Base for Version 2 of the Simple 1774 Network Management Protocol (SNMPv2)", RFC 1907, January 1775 1996. 1777 7. Changes from RFC 1493 1779 The following changes have been made from RFC 1493. 1781 (1) Translated the MIB definition to use SMIv2. 1783 (2) Updated the SNMP Framework and references to comply with the 1784 current IETF guidelines. 1786 (3) Updated the Security section to comply with current IETF 1787 guidelines. 1789 The following chnages have been made from 1790 draft-ietf-bridge-bridgemib-smiv2-00.txt 1792 (1) Misc. description refernces to IEEE 802.1d documents 1794 (2) dot1dNotificationGroup changed from dot1dTrapGroup 1796 (3) Misc. additions to some descriptions 1798 8. Authors' Addresses 1800 K.C. Norseth 1801 Enterasys Networks 1802 2691 S. Decker Lake Lane 1803 Salt Lake City, Utah 84119 1804 Phone: +1 801 887 9823 1805 Email: knorseth@enterasys.com 1807 9. Full Copyright 1809 Copyright (C) The Internet Society (2001). All Rights Reserved. 1811 This document and translations of it may be copied and furnished to 1812 others, and derivative works that comment on or otherwise explain it 1813 or assist in its implmentation may be prepared, copied, published and 1814 distributed, in whole or in part, without restriction of any kind, 1815 provided that the above copyright notice and this paragraph are 1816 included on all such copies and derivative works. However, this 1817 document itself may not be modified in any way, such as by removing 1818 the copyright notice or references to the Internet Society or other 1819 Internet organizations, except as needed for the purpose of 1820 developing Internet standards in which case the procedures for 1821 copyrights defined in the Internet Standards process must be 1822 followed, or as required to translate it into languages other than 1823 English. 1825 The limited permissions granted above are perpetual and will not be 1826 revoked by the Internet Society or its successors or assigns. 1828 This document and the information contained herein is provided on an 1829 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1830 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1831 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1832 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1833 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1835 Table of Contents 1837 1 The SNMP Management Framework ................................ 2 1838 2 Overview ..................................................... 3 1839 2.1 Structure of MIB ........................................... 3 1840 2.1.1 The dot1dBase Group ...................................... 5 1841 2.1.2 The dot1dStp Group ....................................... 5 1842 2.1.3 The dot1dSr Group ........................................ 6 1843 2.1.4 The dot1dTp Group ........................................ 6 1844 2.1.5 The dot1dStatic Group .................................... 6 1845 2.2 Relationship to Other MIBs ................................. 6 1846 2.2.1 Relationship to the 'system' group ....................... 6 1847 2.2.2 Relationship to the 'interfaces' group ................... 6 1848 2.3 Textual Conventions ........................................ 7 1849 3 Definitions .................................................. 7 1850 4 Security Considerations ...................................... 32 1851 5 Acknowledgments .............................................. 32 1852 6 References ................................................... 33 1853 7 Changes from RFC 1493 and Previous Drafts .................... 34 1854 8 Authors' Addresses ........................................... 34 1855 9 Full Copyright ............................................... 34