idnits 2.17.1 draft-ietf-bridge-bridgemib-smiv2-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** 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 1 longer page, the longest (page 1) being 67 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 (June 2001) is 8352 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 1677, 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 1752, 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. -------------------------------------------------------------------------------- 2 Internet Draft Editor of this version: 3 Expires December 2001 E. Bell 4 draft-ietf-bridge-bridgemib-smiv2-00.txt 3Com Corp. 5 Obsoletes: 1493 Authors of previous version: 6 E. Decker 7 cisco Systems, Inc. 8 P. Langille 9 Newbridge Networks 10 A. Rijhsinghani 11 Enterasys Networks 12 K. McCloghrie 13 cisco Systems, Inc. 14 June 2001 16 Definitions of Managed Objects for Bridges 18 Status of this Memo 20 This document is an Internet Draft and is in full conformance with 21 all provisions of Section 10 of RFC2026. Internet Drafts are working 22 documents of the Internet Engineering Task Force (IETF), its Areas, 23 and its Working Groups. Note that other groups may also distribute 24 working documents as Internet Drafts. 26 Internet Drafts are draft documents valid for a maximum of six 27 months. Internet Drafts may be updated, replaced, or obsoleted by 28 other documents at any time. It is not appropriate to use Internet 29 Drafts as reference material or to cite them other than as a "working 30 draft" or "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/1id-abstracts.html 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 To learn the current status of any Internet-Draft, please check the 39 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 40 Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe), 41 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 43 Copyright Notice 45 Copyright (C) The Internet Society (2001). All Rights Reserved. 47 Abstract 49 This memo defines a portion of the Management Information Base (MIB) 50 for use with network management protocols in TCP/IP based internets. 51 In particular it defines objects for managing MAC bridges based on 52 the IEEE 802.1D-1990 standard between Local Area Network (LAN) 53 segments. Provisions are made for support of transparent bridging. 54 Provisions are also made so that these objects apply to bridges 55 connected by subnetworks other than LAN segments. 57 The MIB presented in this memo is a direct translation of the BRIDGE 58 MIB defined in [RFC1493], to the SMIv2 syntax required for current 59 IETF MIB standards. This memo obsoletes RFC 1493. 61 1. The SNMP Management Framework 63 The SNMP Management Framework presently consists of five major 64 components: 66 o An overall architecture, described in RFC 2571 [RFC2571]. 68 o Mechanisms for describing and naming objects and events for the 69 purpose of management. The first version of this Structure of 70 Management Information (SMI) is called SMIv1 and described in 71 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 72 1215 [RFC1215]. The second version, called SMIv2, is described 73 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 74 STD 58, RFC 2580 [RFC2580]. 76 o Message protocols for transferring management information. The 77 first version of the SNMP message protocol is called SNMPv1 and 78 described in STD 15, RFC 1157 [RFC1157]. A second version of 79 the SNMP message protocol, which is not an Internet standards 80 track protocol, is called SNMPv2c and described in RFC 1901 81 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 82 message protocol is called SNMPv3 and described in RFC 1906 83 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 85 o Protocol operations for accessing management information. The 86 first set of protocol operations and associated PDU formats is 87 described in STD 15, RFC 1157 [RFC1157]. A second set of 88 protocol operations and associated PDU formats is described in 89 RFC 1905 [RFC1905]. 91 o A set of fundamental applications described in RFC 2573 92 [RFC2573] and the view-based access control mechanism described 93 in RFC 2575 [RFC2575]. 95 A more detailed introduction to the current SNMP Management Framework 96 can be found in RFC 2570 [RFC2570]. 98 Managed objects are accessed via a virtual information store, termed 99 the Management Information Base or MIB. Objects in the MIB are 100 defined using the mechanisms defined in the SMI. 102 This memo specifies a MIB module that is compliant to the SMIv2. A 103 MIB conforming to the SMIv1 can be produced through the appropriate 104 translations. The resulting translated MIB must be semantically 105 equivalent, except where objects or events are omitted because no 106 translation is possible (use of Counter64). Some machine readable 107 information in SMIv2 will be converted into textual descriptions in 108 SMIv1 during the translation process. However, this loss of machine 109 readable information is not considered to change the semantics of the 110 MIB. 112 2. Overview 114 A common device present in many networks is the Bridge. This device 115 is used to connect Local Area Network segments below the network 116 layer. 118 There are two major modes defined for this bridging; transparent and 119 source route. The transparent method of bridging is defined in the 120 IEEE 802.1D specification [IEEE8021D]. This memo defines those 121 objects needed for the management of a bridging entity operating in 122 the transparent mode, as well as some objects applicable to all types 123 of bridges. 125 To be consistent with IAB directives and good engineering practice, 126 an explicit attempt was made to keep this MIB as simple as possible. 127 This was accomplished by applying the following criteria to objects 128 proposed for inclusion: 130 (1) Start with a small set of essential objects and add only as 131 further objects are needed. 133 (2) Require objects be essential for either fault or configuration 134 management. 136 (3) Consider evidence of current use and/or utility. 138 (4) Limit the total of objects. 140 (5) Exclude objects which are simply derivable from others in this 141 or other MIBs. 143 (6) Avoid causing critical sections to be heavily instrumented. The 144 guideline that was followed is one counter per critical section 145 per layer. 147 2.1. Structure of MIB 149 Objects in this MIB are arranged into groups. Each group is 150 organized as a set of related objects. The overall structure and 151 assignment of objects to their groups is shown below. Where 152 appropriate the corresponding IEEE 802.1D [IEEE8021D] management 153 object name is also included. 155 Bridge MIB Name IEEE 802.1D Name 157 dot1dBridge 158 dot1dBase 159 BridgeAddress Bridge.BridgeAddress 160 NumPorts Bridge.NumberOfPorts 161 Type 162 PortTable 163 Port BridgePort.PortNumber 164 IfIndex 165 Circuit 166 DelayExceededDiscards .DiscardTransitDelay 167 MtuExceededDiscards .DiscardOnError 168 dot1dStp 169 ProtocolSpecification 170 Priority SpanningTreeProtocol 171 .BridgePriority 172 TimeSinceTopologyChange .TimeSinceTopologyChange 173 TopChanges .TopologyChangeCount 174 DesignatedRoot .DesignatedRoot 175 RootCost .RootCost 176 RootPort .RootPort 177 MaxAge .MaxAge 178 HelloTime .HelloTime 179 HoldTime .HoldTime 180 ForwardDelay .ForwardDelay 181 BridgeMaxAge .BridgeMaxAge 182 BridgeHelloTime .BridgeHelloTime 183 BridgeForwardDelay .BridgeForwardDelay 184 PortTable 185 Port SpanningTreeProtocolPort 186 .PortNumber 187 Priority .PortPriority 188 State .SpanningTreeState 189 Enable 190 PathCost .PortPathCost 191 DesignatedRoot .DesignatedRoot 192 DesignatedCost .DesignatedCost 193 DesignatedBridge .DesignatedBridge 194 DesignatedPort .DesignatedPort 195 ForwardTransitions 196 dot1dTp 197 LearnedEntryDiscards BridgeFilter.DatabaseSize 198 .NumDynamic,NumStatic 199 AgingTime BridgeFilter.AgingTime 200 FdbTable 201 Address 202 Port 203 Status 204 PortTable 205 Port 206 MaxInfo 207 InFrames BridgePort.FramesReceived 208 OutFrames .ForwardOutbound 209 InDiscards .DiscardInbound 210 dot1dStatic 211 StaticTable 212 Address 213 ReceivePort 214 AllowedToGoTo 215 Status 217 The following IEEE 802.1D management objects have not been included 218 in the Bridge MIB for the indicated reasons. 220 IEEE 802.1D Object Disposition 222 Bridge.BridgeName Same as sysDescr (MIB II) 223 Bridge.BridgeUpTime Same as sysUpTime (MIB II) 224 Bridge.PortAddresses Same as ifPhysAddress (MIB II) 225 BridgePort.PortName Same as ifDescr (MIB II) 226 BridgePort.PortType Same as ifType (MIB II) 227 BridgePort.RoutingType Derivable from the implemented 228 groups 230 SpanningTreeProtocol 231 .BridgeIdentifier Combination of dot1dStpPriority 232 and dot1dBaseBridgeAddress 233 .TopologyChange Since this is transitory, it 234 is not considered useful. 235 SpanningTreeProtocolPort 236 .Uptime Same as ifLastChange (MIB II) 237 .PortIdentifier Combination of dot1dStpPort 238 and dot1dStpPortPriority 239 .TopologyChangeAcknowledged Since this is transitory, it 240 is not considered useful. 241 .DiscardLackOfBuffers Redundant 243 Transmission Priority These objects are not required 244 as per the Pics Proforma and 245 not considered useful. 246 .TransmissionPriorityName 247 .OutboundUserPriority 248 .OutboundAccessPriority 250 2.1.1. The dot1dBase Group 252 This mandatory group contains the objects which are applicable to all 253 types of bridges. 255 2.1.2. The dot1dStp Group 257 This group contains the objects that denote the bridge's state with 258 respect to the Spanning Tree Protocol. If a node does not 259 implemented the Spanning Tree Protocol, this group will not be 260 implemented. 262 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 371 ; 373 bridgeMIB MODULE-IDENTITY 374 LAST-UPDATED "200106260000Z" 375 ORGANIZATION "IETF Bridge MIB Working Group" 376 CONTACT-INFO 377 "Email: Bridge-mib@ietf.org" 378 DESCRIPTION 379 "The Bridge MIB module for managing devices that support 380 IEEE 802.1D." 381 REVISION "200106260000Z" 382 DESCRIPTION 383 "Draft 0: initial translation of RFC 1493 to SMIv2." 384 REVISION "199307310000Z" 385 DESCRIPTION 386 "RFC 1493: SMIv1 version." 387 ::= { dot1dBridge 8 } 389 -- ---------------------------------------------------------- -- 390 -- Textual Conventions 391 -- ---------------------------------------------------------- -- 393 -- All representations of MAC addresses in this MIB Module use, 394 -- as a textual convention (i.e. this convention does not affect 395 -- their encoding), the data type MacAddress, defined in 396 -- SNMPv2-TC. 398 -- Similarly, all representations of Bridge-Id in this MIB 399 -- Module use, as a textual convention (i.e. this convention 400 -- does not affect their encoding), the data type: 402 BridgeId ::= TEXTUAL-CONVENTION 403 STATUS current 404 DESCRIPTION 405 "The Bridge-Identifier as used in the Spanning Tree 406 Protocol to uniquely identify a bridge. Its first two 407 octets (in network byte order) contain a priority value 408 and its last 6 octets contain the MAC address used to 409 refer to a bridge in a unique fashion (typically, the 410 numerically smallest MAC address of all ports on the 411 bridge)." 412 SYNTAX OCTET STRING (SIZE (8)) 414 -- Several objects in this MIB module represent values of timers 415 -- used by the Spanning Tree Protocol. In this MIB, these 416 -- timers have values in units of hundreths of a second (i.e. 417 -- 1/100 secs). 418 -- These timers, when stored in a Spanning Tree Protocol's BPDU, 419 -- are in units of 1/256 seconds. Note, however, that 420 -- 802.1D-1990 specifies a settable granularity of no more 421 -- than 1 second for these timers. To avoid ambiguity, a data 422 -- type is defined here as a textual convention and all 423 -- representation of these timers in this MIB module are defined 424 -- using this data type. An algorithm is also defined for 425 -- converting between the different units, to ensure a timer's 426 -- value is not distorted by multiple conversions. 427 -- The data type is: 429 Timeout ::= TEXTUAL-CONVENTION 430 STATUS current 431 DESCRIPTION 432 "A STP timer in units of 1/100 seconds. 434 To convert a Timeout value into a value in units of 435 1/256 seconds, the following algorithm should be used: 437 b = floor( (n * 256) / 100) 439 where: 440 floor = quotient [ignore remainder] 441 n is the value in 1/100 second units 442 b is the value in 1/256 second units 444 To convert the value from 1/256 second units back to 445 1/100 seconds, the following algorithm should be used: 447 n = ceiling( (b * 100) / 256) 449 where: 450 ceiling = quotient [if remainder is 0], or 451 quotient + 1 [if remainder is non-zero] 452 n is the value in 1/100 second units 453 b is the value in 1/256 second units 455 Note: it is important that the arithmetic operations are 456 done in the order specified (i.e., multiply first, 457 divide second)." 458 SYNTAX Integer32 460 -- ---------------------------------------------------------- -- 462 dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 } 464 -- ---------------------------------------------------------- -- 465 -- groups in the Bridge MIB 466 -- ---------------------------------------------------------- -- 468 dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 } 469 dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 } 471 dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 } 472 -- separately documented 474 dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 } 475 dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 } 477 -- Groups defined in the Bridge Mib Extensions: 478 -- pBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 6 } 479 -- qBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 7 } 481 -- The MODULE-IDENTITY for this MIB has been defined above as: 482 -- bridgeMIB MODULE-IDENTITY ::= { dot1dBridge 8 } 484 -- The MODULE-IDENTITY for the Source Routing MIB has been 485 -- defined in that MIB as: 486 -- srMIB MODULE-IDENTITY ::= { dot1dBridge 9 } 488 -- Groups defined in the Source Routing MIB: 489 -- dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 } 491 dot1dConformance OBJECT IDENTIFIER ::= { bridgeMIB 1 } 493 -- ---------------------------------------------------------- -- 494 -- the dot1dBase group 495 -- ---------------------------------------------------------- -- 496 -- Implementation of the dot1dBase group is mandatory for all 497 -- bridges. 498 -- ---------------------------------------------------------- -- 500 dot1dBaseBridgeAddress OBJECT-TYPE 501 SYNTAX MacAddress 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "The MAC address used by this bridge when it must be 506 referred to in a unique fashion. It is recommended 507 that this be the numerically smallest MAC address of all 508 ports that belong to this bridge. However it is only 509 required to be unique. When concatenated with 510 dot1dStpPriority a unique BridgeIdentifier is formed 511 which is used in the Spanning Tree Protocol." 512 REFERENCE 513 "IEEE 802.1D-1990: Sections 6.4.1.1.3 and 3.12.5" 514 ::= { dot1dBase 1 } 516 dot1dBaseNumPorts OBJECT-TYPE 517 SYNTAX Integer32 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The number of ports controlled by this bridging 522 entity." 523 REFERENCE 524 "IEEE 802.1D-1990: Section 6.4.1.1.3" 525 ::= { dot1dBase 2 } 527 dot1dBaseType OBJECT-TYPE 528 SYNTAX INTEGER { 529 unknown(1), 530 transparentOnly(2), 531 sourcerouteOnly(3), 532 srt(4) 533 } 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "Indicates what type of bridging this bridge can 538 perform. If a bridge is actually performing a 539 certain type of bridging this will be indicated by 540 entries in the port table for the given type." 541 ::= { dot1dBase 3 } 543 -- ---------------------------------------------------------- -- 544 -- The Generic Bridge Port Table 545 -- ---------------------------------------------------------- -- 547 dot1dBasePortTable OBJECT-TYPE 548 SYNTAX SEQUENCE OF Dot1dBasePortEntry 549 MAX-ACCESS not-accessible 550 STATUS current 551 DESCRIPTION 552 "A table that contains generic information about every 553 port that is associated with this bridge. Transparent, 554 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-1990: Section 6.4.2, 6.6.1" 566 INDEX { dot1dBasePort } 567 ::= { dot1dBasePortTable 1 } 569 Dot1dBasePortEntry ::= 570 SEQUENCE { 571 dot1dBasePort 572 Integer32, 573 dot1dBasePortIfIndex 574 Integer32, 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 not-accessible 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 Integer32 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "The value of the instance of the ifIndex object, 598 defined in MIB-II, 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-1990: Section 6.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." 642 REFERENCE 643 "IEEE 802.1D-1990: Section 6.6.1.1.3" 644 ::= { dot1dBasePortEntry 5 } 646 -- ---------------------------------------------------------- -- 647 -- the dot1dStp group 648 -- ---------------------------------------------------------- -- 649 -- Implementation of the dot1dStp group is optional. It is 650 -- implemented by those bridges that support the Spanning Tree 651 -- Protocol. 652 -- ---------------------------------------------------------- -- 654 dot1dStpProtocolSpecification OBJECT-TYPE 655 SYNTAX INTEGER { 656 unknown(1), 657 decLb100(2), 658 ieee8021d(3) 659 } 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "An indication of what version of the Spanning Tree 664 Protocol is being run. The value 'decLb100(2)' 665 indicates the DEC LANbridge 100 Spanning Tree protocol. 666 IEEE 802.1D implementations will return 'ieee8021d(3)'. 667 If future versions of the IEEE Spanning Tree Protocol 668 are released that are incompatible with the current 669 version a new value will be defined." 670 ::= { dot1dStp 1 } 672 dot1dStpPriority OBJECT-TYPE 673 SYNTAX Integer32 (0..65535) 674 MAX-ACCESS read-write 675 STATUS current 676 DESCRIPTION 677 "The value of the write-able portion of the Bridge ID, 678 i.e., the first two octets of the (8 octet long) Bridge 679 ID. The other (last) 6 octets of the Bridge ID are 680 given by the value of dot1dBaseBridgeAddress." 681 REFERENCE 682 "IEEE 802.1D-1990: Section 4.5.3.7" 683 ::= { dot1dStp 2 } 685 dot1dStpTimeSinceTopologyChange OBJECT-TYPE 686 SYNTAX TimeTicks 687 MAX-ACCESS read-only 688 STATUS current 689 DESCRIPTION 690 "The time (in hundredths of a second) since the 691 last time a topology change was detected by the 692 bridge entity." 693 REFERENCE 694 "IEEE 802.1D-1990: Section 6.8.1.1.3" 695 ::= { dot1dStp 3 } 697 dot1dStpTopChanges OBJECT-TYPE 698 SYNTAX Counter32 699 MAX-ACCESS read-only 700 STATUS current 701 DESCRIPTION 702 "The total number of topology changes detected by 703 this bridge since the management entity was last 704 reset or initialized." 705 REFERENCE 706 "IEEE 802.1D-1990: Section 6.8.1.1.3" 707 ::= { dot1dStp 4 } 709 dot1dStpDesignatedRoot OBJECT-TYPE 710 SYNTAX BridgeId 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "The bridge identifier of the root of the spanning 715 tree as determined by the Spanning Tree Protocol 716 as executed by this node. This value is used as 717 the Root Identifier parameter in all Configuration 718 Bridge PDUs originated by this node." 719 REFERENCE 720 "IEEE 802.1D-1990: Section 4.5.3.1" 721 ::= { dot1dStp 5 } 723 dot1dStpRootCost OBJECT-TYPE 724 SYNTAX Integer32 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "The cost of the path to the root as seen from 729 this bridge." 730 REFERENCE 731 "IEEE 802.1D-1990: Section 4.5.3.2" 732 ::= { dot1dStp 6 } 734 dot1dStpRootPort OBJECT-TYPE 735 SYNTAX Integer32 736 MAX-ACCESS read-only 737 STATUS current 738 DESCRIPTION 739 "The port number of the port which offers the lowest 740 cost path from this bridge to the root bridge." 741 REFERENCE 742 "IEEE 802.1D-1990: Section 4.5.3.3" 743 ::= { dot1dStp 7 } 745 dot1dStpMaxAge OBJECT-TYPE 746 SYNTAX Timeout 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "The maximum age of Spanning Tree Protocol information 751 learned from the network on any port before it is 752 discarded, in units of hundredths of a second. This is 753 the actual value that this bridge is currently using." 754 REFERENCE 755 "IEEE 802.1D-1990: Section 4.5.3.4" 757 ::= { dot1dStp 8 } 759 dot1dStpHelloTime OBJECT-TYPE 760 SYNTAX Timeout 761 MAX-ACCESS read-only 762 STATUS current 763 DESCRIPTION 764 "The amount of time between the transmission of 765 Configuration bridge PDUs by this node on any port when 766 it is the root of the spanning tree or trying to become 767 so, in units of hundredths of a second. This is the 768 actual value that this bridge is currently using." 769 REFERENCE 770 "IEEE 802.1D-1990: Section 4.5.3.5" 771 ::= { dot1dStp 9 } 773 dot1dStpHoldTime OBJECT-TYPE 774 SYNTAX Integer32 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "This time value determines the interval length 779 during which no more than two Configuration bridge 780 PDUs shall be transmitted by this node, in units 781 of hundredths of a second." 782 REFERENCE 783 "IEEE 802.1D-1990: Section 4.5.3.14" 784 ::= { dot1dStp 10 } 786 dot1dStpForwardDelay OBJECT-TYPE 787 SYNTAX Timeout 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "This time value, measured in units of hundredths of a 792 second, controls how fast a port changes its spanning 793 state when moving towards the Forwarding state. The 794 value determines how long the port stays in each of the 795 Listening and Learning states, which precede the 796 Forwarding state. This value is also used, when a 797 topology change has been detected and is underway, to 798 age all dynamic entries in the Forwarding Database. 799 [Note that this value is the one that this bridge is 800 currently using, in contrast to 801 dot1dStpBridgeForwardDelay which is the value that this 802 bridge and all others would start using if/when this 803 bridge were to become the root.]" 804 REFERENCE 805 "IEEE 802.1D-1990: Section 4.5.3.6" 806 ::= { dot1dStp 11 } 808 dot1dStpBridgeMaxAge OBJECT-TYPE 809 SYNTAX Timeout (600..4000) 810 MAX-ACCESS read-write 811 STATUS current 812 DESCRIPTION 813 "The value that all bridges use for MaxAge when this 814 bridge is acting as the root. Note that 802.1D-1990 815 specifies that the range for this parameter is related 816 to the value of dot1dStpBridgeHelloTime. The 817 granularity of this timer is specified by 802.1D-1990 to 818 be 1 second. An agent may return a badValue error if a 819 set is attempted to a value which is not a whole number 820 of seconds." 821 REFERENCE 822 "IEEE 802.1D-1990: Section 4.5.3.8" 823 ::= { dot1dStp 12 } 825 dot1dStpBridgeHelloTime OBJECT-TYPE 826 SYNTAX Timeout (100..1000) 827 MAX-ACCESS read-write 828 STATUS current 829 DESCRIPTION 830 "The value that all bridges use for HelloTime when this 831 bridge is acting as the root. The granularity of this 832 timer is specified by 802.1D- 1990 to be 1 second. An 833 agent may return a badValue error if a set is attempted 834 to a value which is not a whole number of seconds." 835 REFERENCE 836 "IEEE 802.1D-1990: Section 4.5.3.9" 837 ::= { dot1dStp 13 } 839 dot1dStpBridgeForwardDelay OBJECT-TYPE 840 SYNTAX Timeout (400..3000) 841 MAX-ACCESS read-write 842 STATUS current 843 DESCRIPTION 844 "The value that all bridges use for ForwardDelay when 845 this bridge is acting as the root. Note that 846 802.1D-1990 specifies that the range for this parameter 847 is related to the value of dot1dStpBridgeMaxAge. The 848 granularity of this timer is specified by 802.1D-1990 to 849 be 1 second. An agent may return a badValue error if a 850 set is attempted to a value which is not a whole number 851 of seconds." 852 REFERENCE 853 "IEEE 802.1D-1990: Section 4.5.3.10" 854 ::= { dot1dStp 14 } 856 -- ---------------------------------------------------------- -- 857 -- The Spanning Tree Port Table 858 -- ---------------------------------------------------------- -- 860 dot1dStpPortTable OBJECT-TYPE 861 SYNTAX SEQUENCE OF Dot1dStpPortEntry 862 MAX-ACCESS not-accessible 863 STATUS current 864 DESCRIPTION 865 "A table that contains port-specific information 866 for the Spanning Tree Protocol." 867 ::= { dot1dStp 15 } 869 dot1dStpPortEntry OBJECT-TYPE 870 SYNTAX Dot1dStpPortEntry 871 MAX-ACCESS not-accessible 872 STATUS current 873 DESCRIPTION 874 "A list of information maintained by every port about 875 the Spanning Tree Protocol state for that port." 876 INDEX { dot1dStpPort } 877 ::= { dot1dStpPortTable 1 } 879 Dot1dStpPortEntry ::= 880 SEQUENCE { 881 dot1dStpPort 882 Integer32, 883 dot1dStpPortPriority 884 Integer32, 885 dot1dStpPortState 886 INTEGER, 887 dot1dStpPortEnable 888 INTEGER, 889 dot1dStpPortPathCost 890 Integer32, 891 dot1dStpPortDesignatedRoot 892 BridgeId, 893 dot1dStpPortDesignatedCost 894 Integer32, 895 dot1dStpPortDesignatedBridge 896 BridgeId, 897 dot1dStpPortDesignatedPort 898 OCTET STRING, 899 dot1dStpPortForwardTransitions 900 Counter32 901 } 903 dot1dStpPort OBJECT-TYPE 904 SYNTAX Integer32 (1..65535) 905 MAX-ACCESS not-accessible 906 STATUS current 907 DESCRIPTION 908 "The port number of the port for which this entry 909 contains Spanning Tree Protocol management information." 910 REFERENCE 911 "IEEE 802.1D-1990: Section 6.8.2.1.2" 912 ::= { dot1dStpPortEntry 1 } 914 dot1dStpPortPriority OBJECT-TYPE 915 SYNTAX Integer32 (0..255) 916 MAX-ACCESS read-write 917 STATUS current 918 DESCRIPTION 919 "The value of the priority field which is contained in 920 the first (in network byte order) octet of the (2 octet 921 long) Port ID. The other octet of the Port ID is given 922 by the value of dot1dStpPort." 923 REFERENCE 924 "IEEE 802.1D-1990: Section 4.5.5.1" 925 ::= { dot1dStpPortEntry 2 } 927 dot1dStpPortState OBJECT-TYPE 928 SYNTAX INTEGER { 929 disabled(1), 930 blocking(2), 931 listening(3), 932 learning(4), 933 forwarding(5), 934 broken(6) 935 } 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "The port's current state as defined by application of 940 the Spanning Tree Protocol. This state controls what 941 action a port takes on reception of a frame. If the 942 bridge has detected a port that is malfunctioning it 943 will place that port into the broken(6) state. For 944 ports which are disabled (see dot1dStpPortEnable), this 945 object will have a value of disabled(1)." 946 REFERENCE 947 "IEEE 802.1D-1990: Section 4.5.5.2" 948 ::= { dot1dStpPortEntry 3 } 950 dot1dStpPortEnable OBJECT-TYPE 951 SYNTAX INTEGER { 952 enabled(1), 953 disabled(2) 954 } 955 MAX-ACCESS read-write 956 STATUS current 957 DESCRIPTION 958 "The enabled/disabled status of the port." 959 REFERENCE 960 "IEEE 802.1D-1990: Section 4.5.5.2" 961 ::= { dot1dStpPortEntry 4 } 963 dot1dStpPortPathCost OBJECT-TYPE 964 SYNTAX Integer32 (1..65535) 965 MAX-ACCESS read-write 966 STATUS current 967 DESCRIPTION 968 "The contribution of this port to the path cost of 969 paths towards the spanning tree root which include 970 this port. 802.1D-1990 recommends that the 971 default value of this parameter be in inverse 972 proportion to the speed of the attached LAN." 973 REFERENCE 974 "IEEE 802.1D-1990: Section 4.5.5.3" 975 ::= { dot1dStpPortEntry 5 } 977 dot1dStpPortDesignatedRoot OBJECT-TYPE 978 SYNTAX BridgeId 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "The unique Bridge Identifier of the Bridge 983 recorded as the Root in the Configuration BPDUs 984 transmitted by the Designated Bridge for the 985 segment to which the port is attached." 986 REFERENCE 987 "IEEE 802.1D-1990: Section 4.5.5.4" 988 ::= { dot1dStpPortEntry 6 } 990 dot1dStpPortDesignatedCost OBJECT-TYPE 991 SYNTAX Integer32 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "The path cost of the Designated Port of the segment 996 connected to this port. This value is compared to the 997 Root Path Cost field in received bridge PDUs." 998 REFERENCE 999 "IEEE 802.1D-1990: Section 4.5.5.5" 1000 ::= { dot1dStpPortEntry 7 } 1002 dot1dStpPortDesignatedBridge OBJECT-TYPE 1003 SYNTAX BridgeId 1004 MAX-ACCESS read-only 1005 STATUS current 1006 DESCRIPTION 1007 "The Bridge Identifier of the bridge which this 1008 port considers to be the Designated Bridge for 1009 this port's segment." 1010 REFERENCE 1011 "IEEE 802.1D-1990: Section 4.5.5.6" 1012 ::= { dot1dStpPortEntry 8 } 1014 dot1dStpPortDesignatedPort OBJECT-TYPE 1015 SYNTAX OCTET STRING (SIZE (2)) 1016 MAX-ACCESS read-only 1017 STATUS current 1018 DESCRIPTION 1019 "The Port Identifier of the port on the Designated 1020 Bridge for this port's segment." 1021 REFERENCE 1022 "IEEE 802.1D-1990: Section 4.5.5.7" 1023 ::= { dot1dStpPortEntry 9 } 1025 dot1dStpPortForwardTransitions OBJECT-TYPE 1026 SYNTAX Counter32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "The number of times this port has transitioned 1031 from the Learning state to the Forwarding state." 1032 ::= { dot1dStpPortEntry 10 } 1034 -- ---------------------------------------------------------- -- 1035 -- the dot1dTp group 1036 -- ---------------------------------------------------------- -- 1037 -- Implementation of the dot1dTp group is optional. It is 1038 -- implemented by those bridges that support the transparent 1039 -- bridging mode. A transparent or SRT bridge will implement 1040 -- this group. 1041 -- ---------------------------------------------------------- -- 1043 dot1dTpLearnedEntryDiscards OBJECT-TYPE 1044 SYNTAX Counter32 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "The total number of Forwarding Database entries, which 1049 have been or would have been learnt, but have been 1050 discarded due to a lack of space to store them in the 1051 Forwarding Database. If this counter is increasing, it 1052 indicates that the Forwarding Database is regularly 1053 becoming full (a condition which has unpleasant 1054 performance effects on the subnetwork). If this counter 1055 has a significant value but is not presently increasing, 1056 it indicates that the problem has been occurring but is 1057 not persistent." 1059 REFERENCE 1060 "IEEE 802.1D-1990: Section 6.7.1.1.3" 1061 ::= { dot1dTp 1 } 1063 dot1dTpAgingTime OBJECT-TYPE 1064 SYNTAX Integer32 (10..1000000) 1065 MAX-ACCESS read-write 1066 STATUS current 1067 DESCRIPTION 1068 "The timeout period in seconds for aging out 1069 dynamically learned forwarding information. 1070 802.1D-1990 recommends a default of 300 seconds." 1071 REFERENCE 1072 "IEEE 802.1D-1990: Section 6.7.1.1.3" 1073 ::= { dot1dTp 2 } 1075 -- ---------------------------------------------------------- -- 1076 -- The Forwarding Database for Transparent Bridges 1077 -- ---------------------------------------------------------- -- 1079 dot1dTpFdbTable OBJECT-TYPE 1080 SYNTAX SEQUENCE OF Dot1dTpFdbEntry 1081 MAX-ACCESS not-accessible 1082 STATUS current 1083 DESCRIPTION 1084 "A table that contains information about unicast 1085 entries for which the bridge has forwarding and/or 1086 filtering information. This information is used 1087 by the transparent bridging function in 1088 determining how to propagate a received frame." 1089 ::= { dot1dTp 3 } 1091 dot1dTpFdbEntry OBJECT-TYPE 1092 SYNTAX Dot1dTpFdbEntry 1093 MAX-ACCESS not-accessible 1094 STATUS current 1095 DESCRIPTION 1096 "Information about a specific unicast MAC address 1097 for which the bridge has some forwarding and/or 1098 filtering information." 1099 INDEX { dot1dTpFdbAddress } 1100 ::= { dot1dTpFdbTable 1 } 1102 Dot1dTpFdbEntry ::= 1103 SEQUENCE { 1104 dot1dTpFdbAddress 1105 MacAddress, 1106 dot1dTpFdbPort 1107 Integer32, 1108 dot1dTpFdbStatus 1109 INTEGER 1110 } 1112 dot1dTpFdbAddress OBJECT-TYPE 1113 SYNTAX MacAddress 1114 MAX-ACCESS not-accessible 1115 STATUS current 1116 DESCRIPTION 1117 "A unicast MAC address for which the bridge has 1118 forwarding and/or filtering information." 1119 REFERENCE 1120 "IEEE 802.1D-1990: Section 3.9.1, 3.9.2" 1121 ::= { dot1dTpFdbEntry 1 } 1123 dot1dTpFdbPort OBJECT-TYPE 1124 SYNTAX Integer32 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "Either the value '0', or the port number of the port on 1129 which a frame having a source address equal to the value 1130 of the corresponding instance of dot1dTpFdbAddress has 1131 been seen. A value of '0' indicates that the port 1132 number has not been learned but that the bridge does 1133 have some forwarding/filtering information about this 1134 address (e.g. in the dot1dStaticTable). Implementors 1135 are encouraged to assign the port value to this object 1136 whenever it is learned even for addresses for which the 1137 corresponding value of dot1dTpFdbStatus is not 1138 learned(3)." 1139 ::= { dot1dTpFdbEntry 2 } 1141 dot1dTpFdbStatus OBJECT-TYPE 1142 SYNTAX INTEGER { 1143 other(1), 1144 invalid(2), 1145 learned(3), 1146 self(4), 1147 mgmt(5) 1148 } 1149 MAX-ACCESS read-only 1150 STATUS current 1151 DESCRIPTION 1152 "The status of this entry. The meanings of the 1153 values are: 1154 other(1) - none of the following. This would 1155 include the case where some other MIB object 1156 (not the corresponding instance of 1157 dot1dTpFdbPort, nor an entry in the 1158 dot1dStaticTable) is being used to determine if 1159 and how frames addressed to the value of the 1160 corresponding instance of dot1dTpFdbAddress are 1161 being forwarded. 1162 invalid(2) - this entry is not longer valid (e.g., 1163 it was learned but has since aged-out), but has 1164 not yet been flushed from the table. 1165 learned(3) - the value of the corresponding instance 1166 of dot1dTpFdbPort was learned, and is being 1167 used. 1168 self(4) - the value of the corresponding instance of 1169 dot1dTpFdbAddress represents one of the bridge's 1170 addresses. The corresponding instance of 1171 dot1dTpFdbPort indicates which of the bridge's 1172 ports has this address. 1173 mgmt(5) - the value of the corresponding instance of 1174 dot1dTpFdbAddress is also the value of an 1175 existing instance of dot1dStaticAddress." 1176 ::= { dot1dTpFdbEntry 3 } 1178 -- ---------------------------------------------------------- -- 1179 -- Port Table for Transparent Bridges 1180 -- ---------------------------------------------------------- -- 1182 dot1dTpPortTable OBJECT-TYPE 1183 SYNTAX SEQUENCE OF Dot1dTpPortEntry 1184 MAX-ACCESS not-accessible 1185 STATUS current 1186 DESCRIPTION 1187 "A table that contains information about every port that 1188 is associated with this transparent bridge." 1189 ::= { dot1dTp 4 } 1191 dot1dTpPortEntry OBJECT-TYPE 1192 SYNTAX Dot1dTpPortEntry 1193 MAX-ACCESS not-accessible 1194 STATUS current 1195 DESCRIPTION 1196 "A list of information for each port of a transparent 1197 bridge." 1198 INDEX { dot1dTpPort } 1199 ::= { dot1dTpPortTable 1 } 1201 Dot1dTpPortEntry ::= 1202 SEQUENCE { 1203 dot1dTpPort 1204 Integer32, 1205 dot1dTpPortMaxInfo 1206 Integer32, 1207 dot1dTpPortInFrames 1208 Counter32, 1210 dot1dTpPortOutFrames 1211 Counter32, 1212 dot1dTpPortInDiscards 1213 Counter32 1214 } 1216 dot1dTpPort OBJECT-TYPE 1217 SYNTAX Integer32 (1..65535) 1218 MAX-ACCESS not-accessible 1219 STATUS current 1220 DESCRIPTION 1221 "The port number of the port for which this entry 1222 contains Transparent bridging management information." 1223 ::= { dot1dTpPortEntry 1 } 1225 -- It would be nice if we could use ifMtu as the size of the 1226 -- largest INFO field, but we can't because ifMtu is defined 1227 -- to be the size that the (inter-)network layer can use which 1228 -- can differ from the MAC layer (especially if several layers 1229 -- of encapsulation are used). 1231 dot1dTpPortMaxInfo OBJECT-TYPE 1232 SYNTAX Integer32 1233 MAX-ACCESS read-only 1234 STATUS current 1235 DESCRIPTION 1236 "The maximum size of the INFO (non-MAC) field that 1237 this port will receive or transmit." 1238 ::= { dot1dTpPortEntry 2 } 1240 dot1dTpPortInFrames OBJECT-TYPE 1241 SYNTAX Counter32 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "The number of frames that have been received by this 1246 port from its segment. Note that a frame received on the 1247 interface corresponding to this port is only counted by 1248 this object if and only if it is for a protocol being 1249 processed by the local bridging function, including 1250 bridge management frames." 1251 REFERENCE 1252 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1253 ::= { dot1dTpPortEntry 3 } 1255 dot1dTpPortOutFrames OBJECT-TYPE 1256 SYNTAX Counter32 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "The number of frames that have been transmitted by this 1261 port to its segment. Note that a frame transmitted on 1262 the interface corresponding to this port is only counted 1263 by this object if and only if it is for a protocol being 1264 processed by the local bridging function, including 1265 bridge management frames." 1266 REFERENCE 1267 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1268 ::= { dot1dTpPortEntry 4 } 1270 dot1dTpPortInDiscards OBJECT-TYPE 1271 SYNTAX Counter32 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "Count of valid frames received which were discarded 1276 (i.e., filtered) by the Forwarding Process." 1277 REFERENCE 1278 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1279 ::= { dot1dTpPortEntry 5 } 1281 -- ---------------------------------------------------------- -- 1282 -- The Static (Destination-Address Filtering) Database 1283 -- ---------------------------------------------------------- -- 1284 -- Implementation of this group is optional. 1285 -- ---------------------------------------------------------- -- 1287 dot1dStaticTable OBJECT-TYPE 1288 SYNTAX SEQUENCE OF Dot1dStaticEntry 1289 MAX-ACCESS not-accessible 1290 STATUS current 1291 DESCRIPTION 1292 "A table containing filtering information configured 1293 into the bridge by (local or network) management 1294 specifying the set of ports to which frames received 1295 from specific ports and containing specific destination 1296 addresses are allowed to be forwarded. The value of 1297 zero in this table as the port number from which frames 1298 with a specific destination address are received, is 1299 used to specify all ports for which there is no specific 1300 entry in this table for that particular destination 1301 address. Entries are valid for unicast and for 1302 group/broadcast addresses." 1303 REFERENCE 1304 "IEEE 802.1D-1990: Section 6.7.2" 1305 ::= { dot1dStatic 1 } 1307 dot1dStaticEntry OBJECT-TYPE 1308 SYNTAX Dot1dStaticEntry 1309 MAX-ACCESS not-accessible 1310 STATUS current 1311 DESCRIPTION 1312 "Filtering information configured into the bridge by 1313 (local or network) management specifying the set of 1314 ports to which frames received from a specific port and 1315 containing a specific destination address are allowed to 1316 be forwarded." 1317 REFERENCE 1318 "IEEE 802.1D-1990: Section 6.7.2" 1319 INDEX { dot1dStaticAddress, dot1dStaticReceivePort } 1320 ::= { dot1dStaticTable 1 } 1322 Dot1dStaticEntry ::= 1323 SEQUENCE { 1324 dot1dStaticAddress 1325 MacAddress, 1326 dot1dStaticReceivePort 1327 Integer32, 1328 dot1dStaticAllowedToGoTo 1329 OCTET STRING, 1330 dot1dStaticStatus 1331 INTEGER 1332 } 1334 dot1dStaticAddress OBJECT-TYPE 1335 SYNTAX MacAddress 1336 MAX-ACCESS not-accessible 1337 STATUS current 1338 DESCRIPTION 1339 "The destination MAC address in a frame to which this 1340 entry's filtering information applies. This object can 1341 take the value of a unicast address, a group address or 1342 the broadcast address." 1343 REFERENCE 1344 "IEEE 802.1D-1990: Section 3.9.1, 3.9.2" 1345 ::= { dot1dStaticEntry 1 } 1347 dot1dStaticReceivePort OBJECT-TYPE 1348 SYNTAX Integer32 (1..65535) 1349 MAX-ACCESS not-accessible 1350 STATUS current 1351 DESCRIPTION 1352 "Either the value '0', or the port number of the port 1353 from which a frame must be received in order for this 1354 entry's filtering information to apply. A value of zero 1355 indicates that this entry applies on all ports of the 1356 bridge for which there is no other applicable entry." 1357 ::= { dot1dStaticEntry 2 } 1359 dot1dStaticAllowedToGoTo OBJECT-TYPE 1360 SYNTAX OCTET STRING 1361 MAX-ACCESS read-write 1362 STATUS current 1363 DESCRIPTION 1364 "The set of ports to which frames received from a 1365 specific port and destined for a specific MAC address, 1366 are allowed to be forwarded. Each octet within the 1367 value of this object specifies a set of eight ports, 1368 with the first octet specifying ports 1 through 8, the 1369 second octet specifying ports 9 through 16, etc. Within 1370 each octet, the most significant bit represents the 1371 lowest numbered port, and the least significant bit 1372 represents the highest numbered port. Thus, each port 1373 of the bridge is represented by a single bit within the 1374 value of this object. If that bit has a value of '1' 1375 then that port is included in the set of ports; the port 1376 is not included if its bit has a value of '0'. (Note 1377 that the setting of the bit corresponding to the port 1378 from which a frame is received is irrelevant.) The 1379 default value of this object is a string of ones of 1380 appropriate length." 1381 ::= { dot1dStaticEntry 3 } 1383 dot1dStaticStatus OBJECT-TYPE 1384 SYNTAX INTEGER { 1385 other(1), 1386 invalid(2), 1387 permanent(3), 1388 deleteOnReset(4), 1389 deleteOnTimeout(5) 1390 } 1391 MAX-ACCESS read-write 1392 STATUS current 1393 DESCRIPTION 1394 "This object indicates the status of this entry. 1395 The default value is permanent(3). 1396 other(1) - this entry is currently in use but the 1397 conditions under which it will remain so are 1398 different from each of the following values. 1399 invalid(2) - writing this value to the object 1400 removes the corresponding entry. 1401 permanent(3) - this entry is currently in use and 1402 will remain so after the next reset of the 1403 bridge. 1404 deleteOnReset(4) - this entry is currently in use 1405 and will remain so until the next reset of the 1406 bridge. 1407 deleteOnTimeout(5) - this entry is currently in use 1408 and will remain so until it is aged out." 1409 ::= { dot1dStaticEntry 4 } 1411 -- ---------------------------------------------------------- -- 1412 -- Traps for use by Bridges 1413 -- ---------------------------------------------------------- -- 1414 -- Traps for the Spanning Tree Protocol 1415 -- ---------------------------------------------------------- -- 1417 newRoot NOTIFICATION-TYPE 1418 -- OBJECTS { } 1419 STATUS current 1420 DESCRIPTION 1421 "The newRoot trap indicates that the sending agent has 1422 become the new root of the Spanning Tree; the trap is 1423 sent by a bridge soon after its election as the new 1424 root, e.g., upon expiration of the Topology Change Timer 1425 immediately subsequent to its election. Implementation 1426 of this trap is optional." 1427 ::= { dot1dBridge 0 1 } 1429 topologyChange NOTIFICATION-TYPE 1430 -- OBJECTS { } 1431 STATUS current 1432 DESCRIPTION 1433 "A topologyChange trap is sent by a bridge when any of 1434 its configured ports transitions from the Learning state 1435 to the Forwarding state, or from the Forwarding state to 1436 the Blocking state. The trap is not sent if a newRoot 1437 trap is sent for the same transition. Implementation of 1438 this trap is optional." 1439 ::= { dot1dBridge 0 2 } 1441 -- ---------------------------------------------------------- -- 1442 -- IEEE 802.1D MIB - Conformance Information 1443 -- ---------------------------------------------------------- -- 1445 dot1dGroups OBJECT IDENTIFIER ::= { dot1dConformance 1 } 1446 dot1dCompliances OBJECT IDENTIFIER ::= { dot1dConformance 2 } 1448 -- ---------------------------------------------------------- -- 1449 -- units of conformance 1450 -- ---------------------------------------------------------- -- 1452 -- ---------------------------------------------------------- -- 1453 -- the dot1dBase group 1454 -- ---------------------------------------------------------- -- 1456 dot1dBaseBridgeGroup OBJECT-GROUP 1457 OBJECTS { 1458 dot1dBaseBridgeAddress, 1459 dot1dBaseNumPorts, 1460 dot1dBaseType 1462 } 1463 STATUS current 1464 DESCRIPTION 1465 "Bridge level information for this device." 1466 ::= { dot1dGroups 1 } 1468 dot1dBasePortGroup OBJECT-GROUP 1469 OBJECTS { 1470 dot1dBasePortIfIndex, 1471 dot1dBasePortCircuit, 1472 dot1dBasePortDelayExceededDiscards, 1473 dot1dBasePortMtuExceededDiscards 1474 } 1475 STATUS current 1476 DESCRIPTION 1477 "Information for each port on this device." 1478 ::= { dot1dGroups 2 } 1480 -- ---------------------------------------------------------- -- 1481 -- the dot1dStp group 1482 -- ---------------------------------------------------------- -- 1484 dot1dStpBridgeGroup OBJECT-GROUP 1485 OBJECTS { 1486 dot1dStpProtocolSpecification, 1487 dot1dStpPriority, 1488 dot1dStpTimeSinceTopologyChange, 1489 dot1dStpTopChanges, 1490 dot1dStpDesignatedRoot, 1491 dot1dStpRootCost, 1492 dot1dStpRootPort, 1493 dot1dStpMaxAge, 1494 dot1dStpHelloTime, 1495 dot1dStpHoldTime, 1496 dot1dStpForwardDelay, 1497 dot1dStpBridgeMaxAge, 1498 dot1dStpBridgeHelloTime, 1499 dot1dStpBridgeForwardDelay 1500 } 1501 STATUS current 1502 DESCRIPTION 1503 "Bridge level Spanning Tree data for this device." 1504 ::= { dot1dGroups 3 } 1506 dot1dStpPortGroup OBJECT-GROUP 1507 OBJECTS { 1508 dot1dStpPortPriority, 1509 dot1dStpPortState, 1510 dot1dStpPortEnable, 1511 dot1dStpPortPathCost, 1512 dot1dStpPortDesignatedRoot, 1513 dot1dStpPortDesignatedCost, 1514 dot1dStpPortDesignatedBridge, 1515 dot1dStpPortDesignatedPort, 1516 dot1dStpPortForwardTransitions 1517 } 1518 STATUS current 1519 DESCRIPTION 1520 "Spanning Tree data for each port on this device." 1521 ::= { dot1dGroups 4 } 1523 -- ---------------------------------------------------------- -- 1524 -- the dot1dTp group 1525 -- ---------------------------------------------------------- -- 1527 dot1dTpBridgeGroup OBJECT-GROUP 1528 OBJECTS { 1529 dot1dTpLearnedEntryDiscards, 1530 dot1dTpAgingTime 1531 } 1532 STATUS current 1533 DESCRIPTION 1534 "Bridge level Transparent Bridging data." 1535 ::= { dot1dGroups 5 } 1537 dot1dTpFdbGroup OBJECT-GROUP 1538 OBJECTS { 1539 dot1dTpFdbPort, 1540 dot1dTpFdbStatus 1541 } 1542 STATUS current 1543 DESCRIPTION 1544 "Filtering Database information for the Bridge." 1545 ::= { dot1dGroups 6 } 1547 dot1dTpGroup OBJECT-GROUP 1548 OBJECTS { 1549 dot1dTpPortMaxInfo, 1550 dot1dTpPortInFrames, 1551 dot1dTpPortOutFrames, 1552 dot1dTpPortInDiscards 1553 } 1554 STATUS current 1555 DESCRIPTION 1556 "Dynamic Filtering Database information for each port of 1557 the Bridge." 1558 ::= { dot1dGroups 7 } 1560 -- ---------------------------------------------------------- -- 1561 -- The Static (Destination-Address Filtering) Database 1562 -- ---------------------------------------------------------- -- 1564 dot1dStaticGroup OBJECT-GROUP 1565 OBJECTS { 1566 dot1dStaticAllowedToGoTo, 1567 dot1dStaticStatus 1568 } 1569 STATUS current 1570 DESCRIPTION 1571 "Static Filtering Database information for each port of 1572 the Bridge." 1573 ::= { dot1dGroups 8 } 1575 -- ---------------------------------------------------------- -- 1576 -- The Trap Notfication Group 1577 -- ---------------------------------------------------------- -- 1579 dot1dTrapGroup NOTIFICATION-GROUP 1580 NOTIFICATIONS { 1581 newRoot, 1582 topologyChange 1583 } 1584 STATUS current 1585 DESCRIPTION 1586 "Group of objects describing notifications (traps)." 1587 ::= { dot1dGroups 9 } 1589 -- ---------------------------------------------------------- -- 1590 -- compliance statements 1591 -- ---------------------------------------------------------- -- 1593 bridgeCompliance MODULE-COMPLIANCE 1594 STATUS current 1595 DESCRIPTION 1596 "The compliance statement for device support of bridging 1597 services." 1599 MODULE 1600 MANDATORY-GROUPS { 1601 dot1dBaseBridgeGroup, 1602 dot1dBasePortGroup 1603 } 1605 GROUP dot1dStpBridgeGroup 1606 DESCRIPTION 1607 "Implementation of this group is mandatory for 1608 bridges that support the Spanning Tree Protocol." 1610 GROUP dot1dStpPortGroup 1611 DESCRIPTION 1612 "Implementation of this group is mandatory for 1613 bridges that support the Spanning Tree Protocol." 1615 GROUP dot1dTpBridgeGroup 1616 DESCRIPTION 1617 "Implementation of this group is mandatory for 1618 bridges that support the transparent bridging 1619 mode. A transparent or SRT bridge will implement 1620 this group." 1622 GROUP dot1dTpFdbGroup 1623 DESCRIPTION 1624 "Implementation of this group is mandatory for 1625 bridges that support the transparent bridging 1626 mode. A transparent or SRT bridge will implement 1627 this group." 1629 GROUP dot1dTpGroup 1630 DESCRIPTION 1631 "Implementation of this group is mandatory for 1632 bridges that support the transparent bridging 1633 mode. A transparent or SRT bridge will implement 1634 this group." 1636 GROUP dot1dStaticGroup 1637 DESCRIPTION 1638 "Implementation of this group is optional." 1640 ::= { dot1dCompliances 1 } 1642 END 1644 4. Security Considerations 1646 There are a number of management objects defined in this MIB that 1647 have a MAX-ACCESS clause of read-write and/or read-create. Such 1648 objects may be considered sensitive or vulnerable in some network 1649 environments. The support for SET operations in a non-secure 1650 environment without proper protection can have a negative effect on 1651 network operations. 1653 SNMPv1 by itself is not a secure environment. Even if the network 1654 itself is secure (for example by using IPSec), even then, there is no 1655 control as to who on the secure network is allowed to access and 1656 GET/SET (read/change/create/delete) the objects in this MIB. 1658 It is recommended that the implementers consider the security 1659 features as provided by the SNMPv3 framework. Specifically, the use 1660 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1661 based Access Control Model RFC 2575 [RFC2575] is recommended. 1663 It is then a customer/user responsibility to ensure that the SNMP 1664 entity giving access to an instance of this MIB, is properly 1665 configured to give access to the objects only to those principals 1666 (users) that have legitimate rights to indeed GET or SET 1667 (change/create/delete) them. 1669 5. Acknowledgments 1671 The MIB presented in this memo is a direct translation of the BRIDGE 1672 MIB defined in [RFC1493], to the SMIv2 syntax required for current 1673 IETF MIB standards. 1675 The original authors were E. Decker, P. Langille, A Rijsinghani and 1676 K. McCloghrie. Further acknowledgement is given to the members of 1677 the original Bridge Working Group in [RFC1493]. 1679 This document was produced on behalf of the Bridge MIB Working Group 1680 in the Operations and Management area of the Internet Engineering 1681 Task Force. 1683 The authors wish to thank the members of the Bridge MIB Working Group 1684 for their many comments and suggestions which improved this effort. 1686 6. References 1688 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1689 for Describing SNMP Management Frameworks", RFC 2571, April 1690 1999. 1692 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1693 of Management Information for TCP/IP-based Internets", STD 1694 16, RFC 1155, May 1990. 1696 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1697 16, RFC 1212, March 1991. 1699 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1700 SNMP", RFC 1215, March 1991. 1702 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1703 Rose, M., and S. Waldbusser, "Structure of Management 1704 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1705 1999. 1707 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1708 Rose, M., and S. Waldbusser, "Textual Conventions for 1709 SMIv2", STD 58, RFC 2579, April 1999. 1711 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1712 Rose, M., and S. Waldbusser, "Conformance Statements for 1713 SMIv2", STD 58, RFC 2580, April 1999. 1715 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1716 Network Management Protocol", STD 15, RFC 1157, May 1990. 1718 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1719 "Introduction to Community-based SNMPv2", RFC 1901, January 1720 1996. 1722 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1723 "Transport Mappings for Version 2 of the Simple Network 1724 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1726 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1727 Processing and Dispatching for the Simple Network Management 1728 Protocol (SNMP)", RFC 2572, April 1999. 1730 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1731 (USM) for version 3 of the Simple Network Management 1732 Protocol (SNMPv3)", RFC 2574, April 1999. 1734 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1735 "Protocol Operations for Version 2 of the Simple Network 1736 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1738 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1739 RFC 2573, April 1999. 1741 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1742 Access Control Model (VACM) for the Simple Network 1743 Management Protocol (SNMP)", RFC 2575, April 1999. 1745 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1746 "Introduction to Version 3 of the Internet-standard Network 1747 Management Framework", RFC 2570, April 1999. 1749 [IEEE8021D] ANSI/IEEE Standard 802.1D-1990 MAC Bridges, IEEE Project 802 1750 Local and Metropolitan Area Networks, (March 8, 1991). 1752 [ISO8021D] ISO DIS 10038 MAC Bridges. 1754 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1755 MIB", RFC 2863, June 2000. 1757 [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1758 "Management Information Base for Version 2 of the Simple 1759 Network Management Protocol (SNMPv2)", RFC 1907, January 1760 1996. 1762 7. Changes from RFC 1493 1764 The following changes have been made from RFC 1493. 1766 (1) Translated the MIB definition to use SMIv2. 1768 (2) Updated the SNMP Framework and references to comply with the 1769 current IETF guidelines. 1771 (3) Updated the Security section to comply with current IETF 1772 guidelines. 1774 8. Authors' Addresses 1776 Les Bell 1777 3Com Europe Limited 1778 3Com Centre, Boundary Way 1779 Hemel Hempstead 1780 Herts. HP2 7YU 1781 UK 1782 Phone: +44 1442 438025 1783 EMail: Les_Bell@3Com.com 1785 9. Full Copyright 1787 Copyright (C) The Internet Society (2001). All Rights Reserved. 1789 This document and translations of it may be copied and furnished to 1790 others, and derivative works that comment on or otherwise explain it 1791 or assist in its implmentation may be prepared, copied, published and 1792 distributed, in whole or in part, without restriction of any kind, 1793 provided that the above copyright notice and this paragraph are 1794 included on all such copies and derivative works. However, this 1795 document itself may not be modified in any way, such as by removing 1796 the copyright notice or references to the Internet Society or other 1797 Internet organizations, except as needed for the purpose of 1798 developing Internet standards in which case the procedures for 1799 copyrights defined in the Internet Standards process must be 1800 followed, or as required to translate it into languages other than 1801 English. 1803 The limited permissions granted above are perpetual and will not be 1804 revoked by the Internet Society or its successors or assigns. 1806 This document and the information contained herein is provided on an 1807 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1808 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1809 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1810 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1811 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1813 Table of Contents 1815 1 The SNMP Management Framework ................................ 3 1816 2 Overview ..................................................... 4 1817 2.1 Structure of MIB ........................................... 4 1818 2.1.1 The dot1dBase Group ...................................... 6 1819 2.1.2 The dot1dStp Group ....................................... 6 1820 2.1.3 The dot1dSr Group ........................................ 7 1821 2.1.4 The dot1dTp Group ........................................ 7 1822 2.1.5 The dot1dStatic Group .................................... 7 1823 2.2 Relationship to Other MIBs ................................. 7 1824 2.2.1 Relationship to the 'system' group ....................... 7 1825 2.2.2 Relationship to the 'interfaces' group ................... 7 1826 2.3 Textual Conventions ........................................ 8 1827 3 Definitions .................................................. 9 1828 4 Security Considerations ...................................... 35 1829 5 Acknowledgments .............................................. 35 1830 6 References ................................................... 36 1831 7 Changes from RFC 1493 ........................................ 37 1832 8 Authors' Addresses ........................................... 37 1833 9 Full Copyright ............................................... 38