idnits 2.17.1 draft-ietf-bridge-objects-01.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-03-29) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** 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. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** 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 an Authors' Addresses Section. ** There are 31 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [5], [6], [9,10], [7], [8], [9], [10], [11], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (October 1992) is 11488 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 section? '7' on line 1566 looks like a reference -- Missing reference section? '3' on line 1542 looks like a reference -- Missing reference section? '8' on line 1572 looks like a reference -- Missing reference section? '9' on line 1577 looks like a reference -- Missing reference section? '10' on line 1582 looks like a reference -- Missing reference section? '11' on line 1586 looks like a reference -- Missing reference section? '6' on line 1560 looks like a reference -- Missing reference section? '1' on line 1531 looks like a reference -- Missing reference section? '2' on line 1537 looks like a reference -- Missing reference section? '4' on line 1548 looks like a reference -- Missing reference section? '5' on line 1554 looks like a reference Summary: 16 errors (**), 0 flaws (~~), 2 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Bridge MIB October 1992 4 Definitions of Managed Objects 5 for Bridges 7 26 October 17:53:30 EST 1992 9 Draft Expiration Date: March 1993 11 Eric B. Decker 12 cisco Systems, Inc. 13 cire@cisco.com 15 Paul Langille & Anil Rijsinghani 16 Digital Equipment Corporation 17 anil@levers.enet.dec.com 18 langille@edwin.enet.dec.com 20 Keith McCloghrie 21 Hughes LAN Systems, Inc. 22 kzm@hls.com 24 1. Abstract 26 This memo defines a portion of the Management Information Base 27 (MIB) for use with network management protocols in TCP/IP 28 based internets. In particular it defines objects for 29 managing MAC bridges based on the IEEE 802.1D-1990 standard 30 between Local Area Network (LAN) segments. Provisions are 31 made for support of transparent bridging. Provisions are also 32 made so that these objects apply to bridges connected by 33 subnetworks other than LAN segments. 35 2. Status of this Memo 37 This document will be submitted to the RFC editor as an 38 extension to the SNMP MIB. Distribution of this memo is 39 unlimited. Please send comments to the authors. 41 This document is an Internet Draft. Internet Drafts are 42 working documents of the Internet Engineering Task Force 43 (IETF), its Areas, and its Working Groups. Note that other 44 groups may also distribute working documents as Internet 45 Drafts. 47 Internet Drafts are draft documents valid for a maximum of six 48 months. Internet Drafts may be updated, replaced, or obsoleted 49 by other documents at any time. It is not appropriate to use 50 Internet Drafts as reference material or to cite them other 51 than as a "working draft" or "work in progress." 53 Please check the I-D abstract listing contained in each 54 Internet Draft directory to learn the current status of this 55 or any other Internet Draft. 57 3. The Network Management Framework 59 The Internet-standard Network Management Framework consists of 60 three components. They are: 62 RFC 1155 which defines the SMI, the mechanisms used for 63 describing and naming objects for the purpose of 64 management. RFC 1212 defines a more concise description 65 mechanism, which is wholly consistent with the SMI. 67 RFC 1156 which defines MIB-I, the core set of managed 68 objects for the Internet suite of protocols. RFC 1213, 69 defines MIB-II, an evolution of MIB-I based on 70 implementation experience and new operational requirements. 72 RFC 1157 which defines the SNMP, the protocol used for 73 network access to managed objects. 75 The Framework permits new objects to be defined for the 76 purpose of experimentation and evaluation. 78 4. Objects 80 Managed objects are accessed via a virtual information store, 81 termed the Management Information Base or MIB. Objects in the 82 MIB are defined using the subset of Abstract Syntax Notation 83 One (ASN.1) [7] defined in the SMI. In particular, each 84 object has a name, a syntax, and an encoding. The name is an 85 object identifier, an administratively assigned name, which 86 specifies an object type. The object type together with an 87 object instance serves to uniquely identify a specific 88 instantiation of the object. For human convenience, we often 89 use a textual string, termed the OBJECT DESCRIPTOR, to also 90 refer to the object type. 92 The syntax of an object type defines the abstract data 93 structure corresponding to that object type. The ASN.1 94 language is used for this purpose. However, the SMI [3] 95 purposely restricts the ASN.1 constructs which may be used. 96 These restrictions are explicitly made for simplicity. 98 The encoding of an object type is simply how that object type 99 is represented using the object type's syntax. Implicitly 100 tied to the notion of an object type's syntax and encoding is 101 how the object type is represented when being transmitted on 102 the network. 104 The SMI specifies the use of the basic encoding rules of ASN.1 105 [8], subject to the additional requirements imposed by the 106 SNMP. 108 4.1. Format of Definitions 110 Section 6 contains the specification of all object types 111 contained in this MIB module. The object types are defined 112 using the conventions defined in the SMI, as amended by the 113 extensions specified in [9,10]. 115 5. Overview 117 A common device present in many networks is the Bridge. This 118 device is used to connect Local Area Network segments below 119 the network layer. 121 There are two major modes defined for this bridging; 122 transparent and source route. The transparent method of 123 bridging is defined in the draft IEEE 802.1d 124 specification[11]. This memo defines those objects needed for 125 the management of a bridging entity operating in the 126 transparent mode, as well as some objects applicable to all 127 types of bridges. 129 To be consistent with IAB directives and good engineering 130 practice, an explicit attempt was made to keep this MIB as 131 simple as possible. This was accomplished by applying the 132 following criteria to objects proposed for inclusion: 134 (1) Start with a small set of essential objects and add only 135 as further objects are needed. 137 (2) Require objects be essential for either fault or 138 configuration management. 140 (3) Consider evidence of current use and/or utility. 142 (4) Limit the total of objects. 144 (5) Exclude objects which are simply derivable from others in 145 this or other MIBs. 147 (6) Avoid causing critical sections to be heavily 148 instrumented. The guideline that was followed is one 149 counter per critical section per layer. 151 5.1. Structure of MIB 153 Objects in this MIB are arranged into groups. Each group is 154 organized as a set of related objects. The overall structure 155 and assignment of objects to their groups is shown below. 156 Where appropriate the corresponding IEEE 802.1d[11] management 157 object name is also included. 159 Bridge MIB Name IEEE 802.1d Name 161 dot1dBridge 162 dot1dBase 163 BridgeAddress Bridge.BridgeAddress 164 NumPorts Bridge.NumberOfPorts 165 Type 166 PortTable 167 Port BridgePort.PortNumber 168 IfIndex 169 Circuit 170 DelayExceededDiscards .DiscardTransitDelay 171 MtuExceededDiscards .DiscardOnError 172 dot1dStp 173 ProtocolSpecification 174 Priority SpanningTreeProtocol 175 .BridgePriority 176 TimeSinceTopologyChange .TimeSinceTopologyChange 177 TopChanges .TopologyChangeCount 178 DesignatedRoot .DesignatedRoot 179 RootCost .RootCost 180 RootPort .RootPort 181 MaxAge .MaxAge 182 HelloTime .HelloTime 183 HoldTime .HoldTime 184 ForwardDelay .ForwardDelay 185 BridgeMaxAge .BridgeMaxAge 186 BridgeHelloTime .BridgeHelloTime 187 BridgeForwardDelay .BridgeForwardDelay 188 PortTable 189 Port SpanningTreeProtocolPort 190 .PortNumber 191 Priority .PortPriority 192 State .SpanningTreeState 193 Enable 194 PathCost .PortPathCost 195 DesignatedRoot .DesignatedRoot 196 DesignatedCost .DesignatedCost 197 DesignatedBridge .DesignatedBridge 198 DesignatedPort .DesignatedPort 199 ForwardTransitions 201 dot1dTp 202 LearnedEntryDiscards BridgeFilter.DatabaseSize 203 .NumDynamic,NumStatic 204 AgingTime BridgeFilter.AgingTime 205 FdbTable 206 Address 207 Port 208 Status 209 PortTable 210 Port 211 MaxInfo 212 InFrames BridgePort.FramesReceived 213 OutFrames .ForwardOutbound 214 InDiscards .DiscardInbound 215 dot1dStatic 216 StaticTable 217 Address 218 ReceivePort 219 AllowedToGoTo 220 Status 222 The following IEEE 802.1d management objects have not been 223 included in the Bridge MIB for the indicated reasons. 225 IEEE 802.1d Object Disposition 227 Bridge.BridgeName Same as sysDescr (MIB II) 228 Bridge.BridgeUpTime Same as sysUpTime (MIB II) 229 Bridge.PortAddresses Same as ifPhysAddress (MIB II) 230 BridgePort.PortName Same as ifDescr (MIB II) 231 BridgePort.PortType Same as ifType (MIB II) 232 BridgePort.RoutingType Derivable from the implemented 233 groups 235 SpanningTreeProtocol 236 .BridgeIdentifier Combination of dot1dStpPriority 237 and dot1dBaseBridgeAddress 238 .TopologyChange Since this is transitory, it 239 is not considered useful. 240 SpanningTreeProtocolPort 241 .Uptime Same as ifLastChange (MIB II) 242 .PortIdentifier Combination of dot1dStpPort 243 and dot1dStpPortPriority 245 .TopologyChangeAcknowledged Since this is transitory, it 246 is not considered useful. 247 .DiscardLackOfBuffers Redundant 249 Transmission Priority These objects are not required 250 as per the Pics Proforma and 251 not considered useful. 252 .TransmissionPriorityName 253 .OutboundUserPriority 254 .OutboundAccessPriority 256 5.1.1. The dot1dBase Group 258 This mandatory group contains the objects which are applicable 259 to all types of bridges. 261 5.1.2. The dot1dStp Group 263 This group contains the objects that denote the bridge's state 264 with respect to the Spanning Tree Protocol. If a node does 265 not implemented the Spanning Tree Protocol, this group will 266 not be implemented. 268 5.1.3. The dot1dSr Group 270 This group contains the objects that describe the entity's 271 state with respect to source route bridging. If source 272 routing is not supported this group will not be implemented. 273 This group is applicable to source route only, and SRT 274 bridges. This group will be described in a separate document 275 applicable only to source route bridging. 277 5.1.4. The dot1dTp Group 279 This group contains objects that describe the entity's state 280 with respect to transparent bridging. If transparent bridging 281 is not supported this group will not be implemented. This 282 group is applicable to transparent only and SRT bridges. 284 5.1.5. The dot1dStatic Group 286 This group contains objects that describe the entity's state 287 with respect to destination-address filtering. If 288 destination-address filtering is not supported this group will 289 not be implemented. This group is applicable to any type of 290 bridge which performs destination-address filtering. 292 5.2. Relationship to Other MIBs 294 As described above, some IEEE 802.1d management objects have 295 not been included in this MIB because they overlap with 296 objects in other MIBs applicable to a bridge implementing this 297 MIB. In particular, it is assumed that a bridge implementing 298 this MIB will also implement (at least) the 'system' group and 299 the 'interfaces' group defined in MIB-II [6]. 301 5.2.1. Relationship to the 'system' group 303 In MIB-II, the 'system' group is defined as being mandatory 304 for all systems such that each managed entity contains one 305 instance of each object in the 'system' group. Thus, those 306 objects apply to the entity as a whole irrespective of whether 307 the entity's sole functionality is bridging, or whether 308 bridging is only a subset of the entity's functionality. 310 5.2.2. Relationship to the 'interfaces' group 312 In MIB-II, the 'interfaces' group is defined as being 313 mandatory for all systems and contains information on an 314 entity's interfaces, where each interface is thought of as 315 being attached to a `subnetwork'. (Note that this term is not 316 to be confused with `subnet' which refers to an addressing 317 partitioning scheme used in the Internet suite of protocols.) 318 The term 'segment' is used in this memo to refer to such a 319 subnetwork, whether it be an Ethernet segment, a 'ring', a WAN 320 link, or even an X.25 virtual circuit. 322 Implicit in this Bridge MIB is the notion of ports on a 323 bridge. Each of these ports is associated with one interface 324 of the 'interfaces' group, and in most situations, each port 325 is associated with a different interface. However, there are 326 situations in which multiple ports are associated with the 327 same interface. An example of such a situation would be 328 several ports each corresponding one-to-one with several X.25 329 virtual circuits but all on the same interface. 331 Each port is uniquely identified by a port number. A port 332 number has no mandatory relationship to an interface number, 333 but in the simple case a port number will have the same value 334 as the corresponding interface's interface number. Port 335 numbers are in the range (1..dot1dBaseNumPorts). 337 Some entities perform other functionality as well as bridging 338 through the sending and receiving of data on their interfaces. 339 In such situations, only a subset of the data sent/received on 340 an interface is within the domain of the entity's bridging 341 functionality. This subset is considered to be delineated 342 according to a set of protocols, with some protocols being 343 bridged, and other protocols not being bridged. For example, 344 in an entity which exclusively performed bridging, all 345 protocols would be considered as being bridged, whereas in an 346 entity which performed IP routing on IP datagrams and only 347 bridged other protocols, only the non-IP data would be 348 considered as being bridged. 350 Thus, this Bridge MIB (and in particular, its counters) are 351 applicable only to that subset of the data on an entity's 352 interfaces which is sent/received for a protocol being 353 bridged. All such data is sent/received via the ports of the 354 bridge. 356 5.3. Textual Conventions 358 The datatypes, MacAddress, BridgeId and Timeout, are used as 359 textual conventions in this document. These textual 360 conventions have NO effect on either the syntax nor the 361 semantics of any managed object. Objects defined using these 362 conventions are always encoded by means of the rules that 363 define their primitive type. Hence, no changes to the SMI or 364 the SNMP are necessary to accommodate these textual 365 conventions which are adopted merely for the convenience of 366 readers. 368 6. Changes from RFC 1286 370 (1) Updated all text to remove references to source route 371 bridging where not applicable. SR MIB will be a separate 372 document. 374 (2) Removed dot1dSrPortTable. Retained OID definition of 375 dot1dSr. 377 (3) Updated all references of "draft P802.1d/D9" to "IEEE 378 802.1D-1990". 380 (4) Updated bibliography. 382 (5) Added clarification to description of dot1dPortPathCost. 384 (6) Put recommended default in description of 385 dot1dStaticAllowedToGoTo. 387 (7) Put recommended default in description of 388 dot1dStaticStatus. 390 (8) Put recommended default in description of 391 dot1dTpAgingTime. Specified range of (10..1000000). 393 (9) Updated all port number syntaxes, when used as index, to 394 use the range (1..65535). 396 (10) Updated definition of dot1dTpPortInFrames and 397 dot1dTpPortOutFrames. 399 (11) Added text to the traps indicating that they are 400 optional. 402 (12) Clarified definition of dot1dStpForwardDelay. 404 7. Definitions 406 RFCXXXX-MIB DEFINITIONS ::= BEGIN 408 IMPORTS 409 Counter, TimeTicks 410 FROM RFC1155-SMI 411 mib-2 412 FROM RFC1213-MIB 413 OBJECT-TYPE 414 FROM RFC-1212 415 TRAP-TYPE 416 FROM RFC-1215; 418 -- All representations of MAC addresses in this MIB Module use, 419 -- as a textual convention (i.e. this convention does not affect 420 -- their encoding), the data type: 422 MacAddress ::= OCTET STRING (SIZE (6)) -- a 6 octet address in 423 -- the "canonical" order 424 -- defined by IEEE 802.1a, i.e., as if it were transmitted least 425 -- significant bit first, even though 802.5 (in contrast to other 426 -- 802.x protocols) requires MAC addresses to be transmitted most 427 -- significant bit first. 428 -- 429 -- 16-bit addresses, if needed, are represented by setting their 430 -- upper 4 octets to all 0's, i.e., AAFF would be represented 431 -- as 00000000AAFF. 433 -- Similarly, all representations of Bridge-Id in this MIB Module 434 -- use, as a textual convention (i.e. this convention does not affect 435 -- their encoding), the data type: 437 BridgeId ::= OCTET STRING (SIZE (8)) -- the Bridge-Identifier as 438 -- used in the Spanning Tree 439 -- Protocol to uniquely identify a bridge. Its first two octets 440 -- (in network byte order) contain a priority value and its last 441 -- 6 octets contain the MAC address used to refer to a bridge in a 442 -- unique fashion (typically, the numerically smallest MAC address 443 -- of all ports on the bridge). 445 -- Several objects in this MIB module represent values of timers 446 -- used by the Spanning Tree Protocol. In this MIB, these timers 447 -- have values in units of hundreths of a second (i.e. 1/100 secs). 448 -- These timers, when stored in a Spanning Tree Protocol's BPDU, 449 -- are in units of 1/256 seconds. Note, however, that 802.1D-1990 450 -- specifies a settable granularity of no more than 1 second for 451 -- these timers. To avoid ambiguity, a data type is defined here 452 -- as a textual convention and all representation of these timers 453 -- in this MIB module are defined using this data type. An algorithm 454 -- is also defined for converting between the different units, to 455 -- ensure a timer's value is not distorted by multiple conversions. 456 -- The data type is: 458 Timeout ::= INTEGER -- a STP timer in units of 1/100 seconds 460 -- To convert a Timeout value into a value in units of 461 -- 1/256 seconds, the following algorithm should be used: 462 -- 463 -- b = floor( (n * 256) / 100) 464 -- 465 -- where: 466 -- floor = quotient [ignore remainder] 467 -- n is the value in 1/100 second units 468 -- b is the value in 1/256 second units 469 -- 470 -- To convert the value from 1/256 second units back to 471 -- 1/100 seconds, the following algorithm should be used: 472 -- 473 -- n = ceiling( (b * 100) / 256) 474 -- 475 -- where: 476 -- ceiling = quotient [if remainder is 0], or 477 -- quotient + 1 [if remainder is non-zero] 478 -- n is the value in 1/100 second units 479 -- b is the value in 1/256 second units 480 -- 481 -- Note: it is important that the arithmetic operations are done 482 -- in the order specified (i.e., multiply first, divide second). 484 dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 } 486 -- groups in the Bridge MIB 488 dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 } 490 dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 } 492 dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 } 493 -- separately documented 495 dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 } 497 dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 } 499 -- the dot1dBase group 501 -- Implementation of the dot1dBase group is mandatory for all 502 -- bridges. 504 dot1dBaseBridgeAddress OBJECT-TYPE 505 SYNTAX MacAddress 506 ACCESS read-only 507 STATUS mandatory 508 DESCRIPTION 509 "The MAC address used by this bridge when it must 510 be referred to in a unique fashion. It is 511 recommended that this be the numerically smallest 512 MAC address of all ports that belong to this 513 bridge. However it is only required to be unique. 514 When concatenated with dot1dStpPriority a unique 515 BridgeIdentifier is formed which is used in the 516 Spanning Tree Protocol." 517 REFERENCE 518 "IEEE 802.1D-1990: Sections 6.4.1.1.3 and 3.12.5" 519 ::= { dot1dBase 1 } 521 dot1dBaseNumPorts OBJECT-TYPE 522 SYNTAX INTEGER 523 ACCESS read-only 524 STATUS mandatory 525 DESCRIPTION 526 "The number of ports controlled by this bridging 527 entity." 529 REFERENCE 530 "IEEE 802.1D-1990: Section 6.4.1.1.3" 531 ::= { dot1dBase 2 } 533 dot1dBaseType OBJECT-TYPE 534 SYNTAX INTEGER { 535 unknown(1), 536 transparent-only(2), 537 sourceroute-only(3), 538 srt(4) 539 } 540 ACCESS read-only 541 STATUS mandatory 542 DESCRIPTION 543 "Indicates what type of bridging this bridge can 544 perform. If a bridge is actually performing a 545 certain type of bridging this will be indicated by 546 entries in the port table for the given type." 547 ::= { dot1dBase 3 } 549 -- The Generic Bridge Port Table 551 dot1dBasePortTable OBJECT-TYPE 552 SYNTAX SEQUENCE OF Dot1dBasePortEntry 553 ACCESS not-accessible 554 STATUS mandatory 555 DESCRIPTION 556 "A table that contains generic information about 557 every port that is associated with this bridge. 558 Transparent, source-route, and srt ports are 559 included." 560 ::= { dot1dBase 4 } 562 dot1dBasePortEntry OBJECT-TYPE 563 SYNTAX Dot1dBasePortEntry 564 ACCESS not-accessible 565 STATUS mandatory 566 DESCRIPTION 567 "A list of information for each port of the 568 bridge." 569 REFERENCE 570 "IEEE 802.1D-1990: Section 6.4.2, 6.6.1" 571 INDEX { dot1dBasePort } 572 ::= { dot1dBasePortTable 1 } 574 Dot1dBasePortEntry ::= 575 SEQUENCE { 576 dot1dBasePort 577 INTEGER, 578 dot1dBasePortIfIndex 579 INTEGER, 580 dot1dBasePortCircuit 581 OBJECT IDENTIFIER, 582 dot1dBasePortDelayExceededDiscards 583 Counter, 584 dot1dBasePortMtuExceededDiscards 585 Counter 586 } 588 dot1dBasePort OBJECT-TYPE 589 SYNTAX INTEGER (1..65535) 590 ACCESS read-only 591 STATUS mandatory 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 INTEGER 599 ACCESS read-only 600 STATUS mandatory 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 ACCESS read-only 610 STATUS mandatory 611 DESCRIPTION 612 "For a port which (potentially) has the same value 613 of dot1dBasePortIfIndex as another port on the 614 same bridge, this object contains the name of an 615 object instance unique to this port. For example, 616 in the case where multiple ports correspond one- 617 to-one with multiple X.25 virtual circuits, this 618 value might identify an (e.g., the first) object 619 instance associated with the X.25 virtual circuit 620 corresponding to this port. 622 For a port which has a unique value of 623 dot1dBasePortIfIndex, this object can have the 624 value { 0 0 }." 625 ::= { dot1dBasePortEntry 3 } 627 dot1dBasePortDelayExceededDiscards OBJECT-TYPE 628 SYNTAX Counter 629 ACCESS read-only 630 STATUS mandatory 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 Counter 642 ACCESS read-only 643 STATUS mandatory 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 -- the dot1dStp group 654 -- Implementation of the dot1dStp group is optional. It is 655 -- implemented by those bridges that support the Spanning Tree 656 -- Protocol. 658 dot1dStpProtocolSpecification OBJECT-TYPE 659 SYNTAX INTEGER { 660 unknown(1), 661 decLb100(2), 662 ieee8021d(3) 663 } 664 ACCESS read-only 665 STATUS mandatory 666 DESCRIPTION 667 "An indication of what version of the Spanning 668 Tree Protocol is being run. The value 669 'decLb100(2)' indicates the DEC LANbridge 100 670 Spanning Tree protocol. IEEE 802.1d 671 implementations will return 'ieee8021d(3)'. If 672 future versions of the IEEE Spanning Tree Protocol 673 are released that are incompatible with the 674 current version a new value will be defined." 675 ::= { dot1dStp 1 } 677 dot1dStpPriority OBJECT-TYPE 678 SYNTAX INTEGER (0..65535) 679 ACCESS read-write 680 STATUS mandatory 681 DESCRIPTION 682 "The value of the write-able portion of the Bridge 683 ID, i.e., the first two octets of the (8 octet 684 long) Bridge ID. The other (last) 6 octets of the 685 Bridge ID are given by the value of 686 dot1dBaseBridgeAddress." 687 REFERENCE 688 "IEEE 802.1D-1990: Section 4.5.3.7" 689 ::= { dot1dStp 2 } 691 dot1dStpTimeSinceTopologyChange OBJECT-TYPE 692 SYNTAX TimeTicks 693 ACCESS read-only 694 STATUS mandatory 695 DESCRIPTION 696 "The time (in hundredths of a second) since the 697 last time a topology change was detected by the 698 bridge entity." 699 REFERENCE 700 "IEEE 802.1D-1990: Section 6.8.1.1.3" 701 ::= { dot1dStp 3 } 703 dot1dStpTopChanges OBJECT-TYPE 704 SYNTAX Counter 705 ACCESS read-only 706 STATUS mandatory 707 DESCRIPTION 708 "The total number of topology changes detected by 709 this bridge since the management entity was last 710 reset or initialized." 711 REFERENCE 712 "IEEE 802.1D-1990: Section 6.8.1.1.3" 713 ::= { dot1dStp 4 } 715 dot1dStpDesignatedRoot OBJECT-TYPE 716 SYNTAX BridgeId 717 ACCESS read-only 718 STATUS mandatory 719 DESCRIPTION 720 "The bridge identifier of the root of the spanning 721 tree as determined by the Spanning Tree Protocol 722 as executed by this node. This value is used as 723 the Root Identifier parameter in all Configuration 724 Bridge PDUs originated by this node." 725 REFERENCE 726 "IEEE 802.1D-1990: Section 4.5.3.1" 727 ::= { dot1dStp 5 } 729 dot1dStpRootCost OBJECT-TYPE 730 SYNTAX INTEGER 731 ACCESS read-only 732 STATUS mandatory 733 DESCRIPTION 734 "The cost of the path to the root as seen from 735 this bridge." 736 REFERENCE 737 "IEEE 802.1D-1990: Section 4.5.3.2" 738 ::= { dot1dStp 6 } 740 dot1dStpRootPort OBJECT-TYPE 741 SYNTAX INTEGER 742 ACCESS read-only 743 STATUS mandatory 744 DESCRIPTION 745 "The port number of the port which offers the 746 lowest cost path from this bridge to the root 747 bridge." 748 REFERENCE 749 "IEEE 802.1D-1990: Section 4.5.3.3" 750 ::= { dot1dStp 7 } 752 dot1dStpMaxAge OBJECT-TYPE 753 SYNTAX Timeout 754 ACCESS read-only 755 STATUS mandatory 756 DESCRIPTION 757 "The maximum age of Spanning Tree Protocol 758 information learned from the network on any port 759 before it is discarded, in units of hundredths of 760 a second. This is the actual value that this 761 bridge is currently using." 762 REFERENCE 763 "IEEE 802.1D-1990: Section 4.5.3.4" 764 ::= { dot1dStp 8 } 766 dot1dStpHelloTime OBJECT-TYPE 767 SYNTAX Timeout 768 ACCESS read-only 769 STATUS mandatory 770 DESCRIPTION 771 "The amount of time between the transmission of 772 Configuration bridge PDUs by this node on any port 773 when it is the root of the spanning tree or trying 774 to become so, in units of hundredths of a second. 775 This is the actual value that this bridge is 776 currently using." 777 REFERENCE 778 "IEEE 802.1D-1990: Section 4.5.3.5" 779 ::= { dot1dStp 9 } 781 dot1dStpHoldTime OBJECT-TYPE 782 SYNTAX INTEGER 783 ACCESS read-only 784 STATUS mandatory 785 DESCRIPTION 786 "This time value determines the interval length 787 during which no more than two Configuration bridge 788 PDUs shall be transmitted by this node, in units 789 of hundredths of a second." 790 REFERENCE 791 "IEEE 802.1D-1990: Section 4.5.3.14" 792 ::= { dot1dStp 10 } 794 dot1dStpForwardDelay OBJECT-TYPE 795 SYNTAX Timeout 796 ACCESS read-only 797 STATUS mandatory 798 DESCRIPTION 799 "This time value, measured in units of hundredths 800 of a second, controls how fast a port changes its 801 spanning state when moving towards the Forwarding 802 state. The value determines how long the port 803 stays in each of the Listening and Learning 804 states, which precede the Forwarding state. This 805 value is also used, when a topology change has 806 been detected and is underway, to age all dynamic 807 entries in the Forwarding Database. [Note that 808 this value is the one that this bridge is 809 currently using, in contrast to 810 dot1dStpBridgeForwardDelay which is the value that 811 this bridge and all others would start using 812 if/when this bridge were to become the root.]" 813 REFERENCE 814 "IEEE 802.1D-1990: Section 4.5.3.6" 815 ::= { dot1dStp 11 } 817 dot1dStpBridgeMaxAge OBJECT-TYPE 818 SYNTAX Timeout (600..4000) 819 ACCESS read-write 820 STATUS mandatory 821 DESCRIPTION 822 "The value that all bridges use for MaxAge when 823 this bridge is acting as the root. Note that 824 802.1D-1990 specifies that the range for this 825 parameter is related to the value of 826 dot1dStpBridgeHelloTime. The granularity of this 827 timer is specified by 802.1D-1990 to be 1 second. 828 An agent may return a badValue error if a set is 829 attempted to a value which is not a whole number 830 of seconds." 832 REFERENCE 833 "IEEE 802.1D-1990: Section 4.5.3.8" 834 ::= { dot1dStp 12 } 836 dot1dStpBridgeHelloTime OBJECT-TYPE 837 SYNTAX Timeout (100..1000) 838 ACCESS read-write 839 STATUS mandatory 840 DESCRIPTION 841 "The value that all bridges use for HelloTime when 842 this bridge is acting as the root. The 843 granularity of this timer is specified by 802.1D- 844 1990 to be 1 second. An agent may return a 845 badValue error if a set is attempted to a value 846 which is not a whole number of seconds." 847 REFERENCE 848 "IEEE 802.1D-1990: Section 4.5.3.9" 849 ::= { dot1dStp 13 } 851 dot1dStpBridgeForwardDelay OBJECT-TYPE 852 SYNTAX Timeout (400..3000) 853 ACCESS read-write 854 STATUS mandatory 855 DESCRIPTION 856 "The value that all bridges use for ForwardDelay 857 when this bridge is acting as the root. Note that 858 802.1D-1990 specifies that the range for this 859 parameter is related to the value of 860 dot1dStpBridgeMaxAge. The granularity of this 861 timer is specified by 802.1D-1990 to be 1 second. 862 An agent may return a badValue error if a set is 863 attempted to a value which is not a whole number 864 of seconds." 865 REFERENCE 866 "IEEE 802.1D-1990: Section 4.5.3.10" 867 ::= { dot1dStp 14 } 869 -- The Spanning Tree Port Table 871 dot1dStpPortTable OBJECT-TYPE 872 SYNTAX SEQUENCE OF Dot1dStpPortEntry 873 ACCESS not-accessible 874 STATUS mandatory 875 DESCRIPTION 876 "A table that contains port-specific information 877 for the Spanning Tree Protocol." 878 ::= { dot1dStp 15 } 880 dot1dStpPortEntry OBJECT-TYPE 881 SYNTAX Dot1dStpPortEntry 882 ACCESS not-accessible 883 STATUS mandatory 884 DESCRIPTION 885 "A list of information maintained by every port 886 about the Spanning Tree Protocol state for that 887 port." 888 INDEX { dot1dStpPort } 889 ::= { dot1dStpPortTable 1 } 891 Dot1dStpPortEntry ::= 892 SEQUENCE { 893 dot1dStpPort 894 INTEGER, 895 dot1dStpPortPriority 896 INTEGER, 897 dot1dStpPortState 898 INTEGER, 899 dot1dStpPortEnable 900 INTEGER, 901 dot1dStpPortPathCost 902 INTEGER, 903 dot1dStpPortDesignatedRoot 904 BridgeId, 905 dot1dStpPortDesignatedCost 906 INTEGER, 907 dot1dStpPortDesignatedBridge 908 BridgeId, 909 dot1dStpPortDesignatedPort 910 OCTET STRING, 911 dot1dStpPortForwardTransitions 912 Counter 913 } 915 dot1dStpPort OBJECT-TYPE 916 SYNTAX INTEGER (1..65535) 917 ACCESS read-only 918 STATUS mandatory 919 DESCRIPTION 920 "The port number of the port for which this entry 921 contains Spanning Tree Protocol management 922 information." 923 REFERENCE 924 "IEEE 802.1D-1990: Section 6.8.2.1.2" 925 ::= { dot1dStpPortEntry 1 } 927 dot1dStpPortPriority OBJECT-TYPE 928 SYNTAX INTEGER (0..255) 929 ACCESS read-write 930 STATUS mandatory 931 DESCRIPTION 932 "The value of the priority field which is 933 contained in the first (in network byte order) 934 octet of the (2 octet long) Port ID. The other 935 octet of the Port ID is given by the value of 936 dot1dStpPort." 937 REFERENCE 938 "IEEE 802.1D-1990: Section 4.5.5.1" 939 ::= { dot1dStpPortEntry 2 } 941 dot1dStpPortState OBJECT-TYPE 942 SYNTAX INTEGER { 943 disabled(1), 944 blocking(2), 945 listening(3), 946 learning(4), 947 forwarding(5), 948 broken(6) 949 } 950 ACCESS read-only 951 STATUS mandatory 952 DESCRIPTION 953 "The port's current state as defined by 954 application of the Spanning Tree Protocol. This 955 state controls what action a port takes on 956 reception of a frame. If the bridge has detected 957 a port that is malfunctioning it will place that 958 port into the broken(6) state. For ports which 959 are disabled (see dot1dStpPortEnable), this object 960 will have a value of disabled(1)." 961 REFERENCE 962 "IEEE 802.1D-1990: Section 4.5.5.2" 963 ::= { dot1dStpPortEntry 3 } 965 dot1dStpPortEnable OBJECT-TYPE 966 SYNTAX INTEGER { 967 enabled(1), 968 disabled(2) 969 } 970 ACCESS read-write 971 STATUS mandatory 972 DESCRIPTION 973 "The enabled/disabled status of the port." 974 REFERENCE 975 "IEEE 802.1D-1990: Section 4.5.5.2" 976 ::= { dot1dStpPortEntry 4 } 978 dot1dStpPortPathCost OBJECT-TYPE 979 SYNTAX INTEGER (1..65535) 980 ACCESS read-write 981 STATUS mandatory 982 DESCRIPTION 983 "The contribution of this port to the path cost of 984 paths towards the spanning tree root which include 985 this port. 802.1D-1990 recommends that the 986 default value of this parameter be in inverse 987 proportion to the speed of the attached LAN." 988 REFERENCE 989 "IEEE 802.1D-1990: Section 4.5.5.3" 990 ::= { dot1dStpPortEntry 5 } 992 dot1dStpPortDesignatedRoot OBJECT-TYPE 993 SYNTAX BridgeId 994 ACCESS read-only 995 STATUS mandatory 996 DESCRIPTION 997 "The unique Bridge Identifier of the Bridge 998 recorded as the Root in the Configuration BPDUs 999 transmitted by the Designated Bridge for the 1000 segment to which the port is attached." 1001 REFERENCE 1002 "IEEE 802.1D-1990: Section 4.5.5.4" 1003 ::= { dot1dStpPortEntry 6 } 1005 dot1dStpPortDesignatedCost OBJECT-TYPE 1006 SYNTAX INTEGER 1007 ACCESS read-only 1008 STATUS mandatory 1009 DESCRIPTION 1010 "The path cost of the Designated Port of the 1011 segment connected to this port. This value is 1012 compared to the Root Path Cost field in received 1013 bridge PDUs." 1014 REFERENCE 1015 "IEEE 802.1D-1990: Section 4.5.5.5" 1016 ::= { dot1dStpPortEntry 7 } 1018 dot1dStpPortDesignatedBridge OBJECT-TYPE 1019 SYNTAX BridgeId 1020 ACCESS read-only 1021 STATUS mandatory 1022 DESCRIPTION 1023 "The Bridge Identifier of the bridge which this 1024 port considers to be the Designated Bridge for 1025 this port's segment." 1026 REFERENCE 1027 "IEEE 802.1D-1990: Section 4.5.5.6" 1028 ::= { dot1dStpPortEntry 8 } 1030 dot1dStpPortDesignatedPort OBJECT-TYPE 1031 SYNTAX OCTET STRING (SIZE (2)) 1032 ACCESS read-only 1033 STATUS mandatory 1034 DESCRIPTION 1035 "The Port Identifier of the port on the Designated 1036 Bridge for this port's segment." 1037 REFERENCE 1038 "IEEE 802.1D-1990: Section 4.5.5.7" 1039 ::= { dot1dStpPortEntry 9 } 1041 dot1dStpPortForwardTransitions OBJECT-TYPE 1042 SYNTAX Counter 1043 ACCESS read-only 1044 STATUS mandatory 1045 DESCRIPTION 1046 "The number of times this port has transitioned 1047 from the Learning state to the Forwarding state." 1048 ::= { dot1dStpPortEntry 10 } 1050 -- the dot1dTp group 1052 -- Implementation of the dot1dTp group is optional. It is 1053 -- implemented by those bridges that support the transparent 1054 -- bridging mode. A transparent or SRT bridge will implement 1055 -- this group. 1057 dot1dTpLearnedEntryDiscards OBJECT-TYPE 1058 SYNTAX Counter 1059 ACCESS read-only 1060 STATUS mandatory 1061 DESCRIPTION 1062 "The total number of Forwarding Database entries, 1063 which have been or would have been learnt, but 1064 have been discarded due to a lack of space to 1065 store them in the Forwarding Database. If this 1066 counter is increasing, it indicates that the 1067 Forwarding Database is regularly becoming full (a 1068 condition which has unpleasant performance effects 1069 on the subnetwork). If this counter has a 1070 significant value but is not presently increasing, 1071 it indicates that the problem has been occurring 1072 but is not persistent." 1073 REFERENCE 1074 "IEEE 802.1D-1990: Section 6.7.1.1.3" 1075 ::= { dot1dTp 1 } 1077 dot1dTpAgingTime OBJECT-TYPE 1078 SYNTAX INTEGER (10..1000000) 1079 ACCESS read-write 1080 STATUS mandatory 1081 DESCRIPTION 1082 "The timeout period in seconds for aging out 1083 dynamically learned forwarding information. 1084 802.1D-1990 recommends a default of 300 seconds." 1085 REFERENCE 1086 "IEEE 802.1D-1990: Section 6.7.1.1.3" 1087 ::= { dot1dTp 2 } 1089 -- The Forwarding Database for Transparent Bridges 1091 dot1dTpFdbTable OBJECT-TYPE 1092 SYNTAX SEQUENCE OF Dot1dTpFdbEntry 1093 ACCESS not-accessible 1094 STATUS mandatory 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 ACCESS not-accessible 1106 STATUS mandatory 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 INTEGER, 1120 dot1dTpFdbStatus 1121 INTEGER 1122 } 1124 dot1dTpFdbAddress OBJECT-TYPE 1125 SYNTAX MacAddress 1126 ACCESS read-only 1127 STATUS mandatory 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 INTEGER 1137 ACCESS read-only 1138 STATUS mandatory 1139 DESCRIPTION 1140 "Either the value '0', or the port number of the 1141 port on which a frame having a source address 1142 equal to the value of the corresponding instance 1143 of dot1dTpFdbAddress has been seen. A value of 1144 '0' indicates that the port number has not been 1145 learned but that the bridge does have some 1146 forwarding/filtering information about this 1147 address (e.g. in the dot1dStaticTable). 1148 Implementors are encouraged to assign the port 1149 value to this object whenever it is learned even 1150 for addresses for which the corresponding value of 1151 dot1dTpFdbStatus is not learned(3)." 1152 ::= { dot1dTpFdbEntry 2 } 1154 dot1dTpFdbStatus OBJECT-TYPE 1155 SYNTAX INTEGER { 1156 other(1), 1157 invalid(2), 1158 learned(3), 1159 self(4), 1160 mgmt(5) 1161 } 1162 ACCESS read-only 1163 STATUS mandatory 1164 DESCRIPTION 1165 "The status of this entry. The meanings of the 1166 values are: 1168 other(1) : none of the following. This would 1169 include the case where some other 1170 MIB object (not the corresponding 1171 instance of dot1dTpFdbPort, nor an 1172 entry in the dot1dStaticTable) is 1173 being used to determine if and how 1174 frames addressed to the value of 1175 the corresponding instance of 1176 dot1dTpFdbAddress are being 1177 forwarded. 1179 invalid(2) : this entry is not longer valid 1180 (e.g., it was learned but has since 1181 aged-out), but has not yet been 1182 flushed from the table. 1184 learned(3) : the value of the corresponding 1185 instance of dot1dTpFdbPort was 1186 learned, and is being used. 1188 self(4) : the value of the corresponding 1189 instance of dot1dTpFdbAddress 1190 represents one of the bridge's 1191 addresses. The corresponding 1192 instance of dot1dTpFdbPort 1193 indicates which of the bridge's 1194 ports has this address. 1196 mgmt(5) : the value of the corresponding 1197 instance of dot1dTpFdbAddress is 1198 also the value of an existing 1199 instance of dot1dStaticAddress." 1200 ::= { dot1dTpFdbEntry 3 } 1202 -- Port Table for Transparent Bridges 1204 dot1dTpPortTable OBJECT-TYPE 1205 SYNTAX SEQUENCE OF Dot1dTpPortEntry 1206 ACCESS not-accessible 1207 STATUS mandatory 1208 DESCRIPTION 1209 "A table that contains information about every 1210 port that is associated with this transparent 1211 bridge." 1212 ::= { dot1dTp 4 } 1214 dot1dTpPortEntry OBJECT-TYPE 1215 SYNTAX Dot1dTpPortEntry 1216 ACCESS not-accessible 1217 STATUS mandatory 1218 DESCRIPTION 1219 "A list of information for each port of a 1220 transparent bridge." 1221 INDEX { dot1dTpPort } 1222 ::= { dot1dTpPortTable 1 } 1224 Dot1dTpPortEntry ::= 1225 SEQUENCE { 1226 dot1dTpPort 1227 INTEGER, 1228 dot1dTpPortMaxInfo 1229 INTEGER, 1230 dot1dTpPortInFrames 1231 Counter, 1232 dot1dTpPortOutFrames 1233 Counter, 1234 dot1dTpPortInDiscards 1235 Counter 1236 } 1238 dot1dTpPort OBJECT-TYPE 1239 SYNTAX INTEGER (1..65535) 1240 ACCESS read-only 1241 STATUS mandatory 1242 DESCRIPTION 1243 "The port number of the port for which this entry 1244 contains Transparent bridging management 1245 information." 1246 ::= { dot1dTpPortEntry 1 } 1248 -- It would be nice if we could use ifMtu as the size of the 1249 -- largest INFO field, but we can't because ifMtu is defined 1250 -- to be the size that the (inter-)network layer can use which 1251 -- can differ from the MAC layer (especially if several layers 1252 -- of encapsulation are used). 1254 dot1dTpPortMaxInfo OBJECT-TYPE 1255 SYNTAX INTEGER 1256 ACCESS read-only 1257 STATUS mandatory 1258 DESCRIPTION 1259 "The maximum size of the INFO (non-MAC) field that 1260 this port will receive or transmit." 1261 ::= { dot1dTpPortEntry 2 } 1263 dot1dTpPortInFrames OBJECT-TYPE 1264 SYNTAX Counter 1265 ACCESS read-only 1266 STATUS mandatory 1267 DESCRIPTION 1268 "The number of frames that have been received by 1269 this port from its segment. Note that a frame 1270 received on the interface corresponding to this 1271 port is only counted by this object if and only if 1272 it is for a protocol being processed by the local 1273 bridging function, including bridge management 1274 frames." 1275 REFERENCE 1276 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1277 ::= { dot1dTpPortEntry 3 } 1279 dot1dTpPortOutFrames OBJECT-TYPE 1280 SYNTAX Counter 1281 ACCESS read-only 1282 STATUS mandatory 1283 DESCRIPTION 1284 "The number of frames that have been transmitted 1285 by this port to its segment. Note that a frame 1286 transmitted on the interface corresponding to this 1287 port is only counted by this object if and only if 1288 it is for a protocol being processed by the local 1289 bridging function, including bridge management 1290 frames." 1291 REFERENCE 1292 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1293 ::= { dot1dTpPortEntry 4 } 1295 dot1dTpPortInDiscards OBJECT-TYPE 1296 SYNTAX Counter 1297 ACCESS read-only 1298 STATUS mandatory 1299 DESCRIPTION 1300 "Count of valid frames received which were 1301 discarded (i.e., filtered) by the Forwarding 1302 Process." 1303 REFERENCE 1304 "IEEE 802.1D-1990: Section 6.6.1.1.3" 1305 ::= { dot1dTpPortEntry 5 } 1307 -- The Static (Destination-Address Filtering) Database 1309 -- Implementation of this group is optional. 1311 dot1dStaticTable OBJECT-TYPE 1312 SYNTAX SEQUENCE OF Dot1dStaticEntry 1313 ACCESS not-accessible 1314 STATUS mandatory 1315 DESCRIPTION 1316 "A table containing filtering information 1317 configured into the bridge by (local or network) 1318 management specifying the set of ports to which 1319 frames received from specific ports and containing 1320 specific destination addresses are allowed to be 1321 forwarded. The value of zero in this table as the 1322 port number from which frames with a specific 1323 destination address are received, is used to 1324 specify all ports for which there is no specific 1325 entry in this table for that particular 1326 destination address. Entries are valid for 1327 unicast and for group/broadcast addresses." 1328 REFERENCE 1329 "IEEE 802.1D-1990: Section 6.7.2" 1330 ::= { dot1dStatic 1 } 1332 dot1dStaticEntry OBJECT-TYPE 1333 SYNTAX Dot1dStaticEntry 1334 ACCESS not-accessible 1335 STATUS mandatory 1336 DESCRIPTION 1337 "Filtering information configured into the bridge 1338 by (local or network) management specifying the 1339 set of ports to which frames received from a 1340 specific port and containing a specific 1341 destination address are allowed to be forwarded." 1342 REFERENCE 1343 "IEEE 802.1D-1990: Section 6.7.2" 1344 INDEX { dot1dStaticAddress, dot1dStaticReceivePort } 1345 ::= { dot1dStaticTable 1 } 1347 Dot1dStaticEntry ::= 1348 SEQUENCE { 1349 dot1dStaticAddress 1350 MacAddress, 1352 dot1dStaticReceivePort 1353 INTEGER, 1354 dot1dStaticAllowedToGoTo 1355 OCTET STRING, 1356 dot1dStaticStatus 1357 INTEGER 1358 } 1360 dot1dStaticAddress OBJECT-TYPE 1361 SYNTAX MacAddress 1362 ACCESS read-write 1363 STATUS mandatory 1364 DESCRIPTION 1365 "The destination MAC address in a frame to which 1366 this entry's filtering information applies. This 1367 object can take the value of a unicast address, a 1368 group address or the broadcast address." 1369 REFERENCE 1370 "IEEE 802.1D-1990: Section 3.9.1, 3.9.2" 1371 ::= { dot1dStaticEntry 1 } 1373 dot1dStaticReceivePort OBJECT-TYPE 1374 SYNTAX INTEGER 1375 ACCESS read-write 1376 STATUS mandatory 1377 DESCRIPTION 1378 "Either the value '0', or the port number of the 1379 port from which a frame must be received in order 1380 for this entry's filtering information to apply. 1381 A value of zero indicates that this entry applies 1382 on all ports of the bridge for which there is no 1383 other applicable entry." 1384 ::= { dot1dStaticEntry 2 } 1386 dot1dStaticAllowedToGoTo OBJECT-TYPE 1387 SYNTAX OCTET STRING 1388 ACCESS read-write 1389 STATUS mandatory 1390 DESCRIPTION 1391 "The set of ports to which frames received from a 1392 specific port and destined for a specific MAC 1393 address, are allowed to be forwarded. Each octet 1394 within the value of this object specifies a set of 1395 eight ports, with the first octet specifying ports 1396 1 through 8, the second octet specifying ports 9 1397 through 16, etc. Within each octet, the most 1398 significant bit represents the lowest numbered 1399 port, and the least significant bit represents the 1400 highest numbered port. Thus, each port of the 1401 bridge is represented by a single bit within the 1402 value of this object. If that bit has a value of 1403 '1' then that port is included in the set of 1404 ports; the port is not included if its bit has a 1405 value of '0'. (Note that the setting of the bit 1406 corresponding to the port from which a frame is 1407 received is irrelevant.) The default value of 1408 this object is a string of ones of appropriate 1409 length." 1410 ::= { dot1dStaticEntry 3 } 1412 dot1dStaticStatus OBJECT-TYPE 1413 SYNTAX INTEGER { 1414 other(1), 1415 invalid(2), 1416 permanent(3), 1417 deleteOnReset(4), 1418 deleteOnTimeout(5) 1419 } 1420 ACCESS read-write 1421 STATUS mandatory 1422 DESCRIPTION 1423 "This object indicates the status of this entry. 1424 The default value is permanent(3). 1426 other(1) - this entry is currently in use but 1427 the conditions under which it will 1428 remain so are different from each of the 1429 following values. 1430 invalid(2) - writing this value to the object 1431 removes the corresponding entry. 1432 permanent(3) - this entry is currently in use 1433 and will remain so after the next reset 1434 of the bridge. 1435 deleteOnReset(4) - this entry is currently in 1436 use and will remain so until the next 1437 reset of the bridge. 1438 deleteOnTimeout(5) - this entry is currently 1439 in use and will remain so until it is 1440 aged out." 1441 ::= { dot1dStaticEntry 4 } 1443 -- Traps for use by Bridges 1445 -- Traps for the Spanning Tree Protocol 1447 newRoot TRAP-TYPE 1448 ENTERPRISE dot1dBridge 1449 DESCRIPTION 1450 "The newRoot trap indicates that the sending agent 1451 has become the new root of the Spanning Tree; the 1452 trap is sent by a bridge soon after its election 1453 as the new root, e.g., upon expiration of the 1454 Topology Change Timer immediately subsequent to 1455 its election. Implementation of this trap is 1456 optional." 1457 ::= 1 1459 topologyChange TRAP-TYPE 1460 ENTERPRISE dot1dBridge 1461 DESCRIPTION 1462 "A topologyChange trap is sent by a bridge when 1463 any of its configured ports transitions from the 1464 Learning state to the Forwarding state, or from 1465 the Forwarding state to the Blocking state. The 1466 trap is not sent if a newRoot trap is sent for the 1467 same transition. Implementation of this trap is 1468 optional." 1469 ::= 2 1471 END 1472 8. Acknowledgments 1474 This document was produced on behalf of the Bridge Sub-Working 1475 Group of the SNMP Working Group of the Internet Engineering 1476 Task Force. Over the course of its deliberations, the working 1477 group received four separate documents for consideration as 1478 the basis for its work. The first was submitted by Stan Froyd 1479 of Advanced Computer Communications; the second by Richard Fox 1480 of SynOptics; the third by Eric Decker of cisco Inc. and Keith 1481 McCloghrie of Hughes LAN Systems; and the fourth by Paul 1482 Langille and Anil Rijsinghani of Digital Equipment Corp. After 1483 considering the submissions, the working group chose to 1484 proceed with a document formed as a conjunction of the latter 1485 two submissions. This document is the result. 1487 The authors wish to thank the members of the Bridge Working 1488 Group for their many comments and suggestions which improved 1489 this effort. In particular, Fred Baker (chairman of the 1490 working group) of ACC, Steve Sherry of Xyplex, and Frank 1491 Kastenholz of Clearpoint Research Corp. Others members of the 1492 Bridge Working Group who contributed to this effort are: 1494 Bill Anderson, Mitre 1495 Karl Auerbach, Epilogue 1496 Fred Baker, ACC (chair) 1497 Terry Bradley, Wellfleet 1498 Ted Brunner, Bellcore 1499 Jeffrey Buffum, Apollo 1500 Chris ChioTasso, Fibronics 1501 Anthony Chung, HLS 1502 Chuck Davin, MIT-LCS 1503 Andy Davis, Spider 1504 Eric Decker, cisco 1505 Nadya El-Afandi, Network Systems 1506 Gary Ellis,HP/Apollo 1507 Richard Fox, SynOptics 1508 Stan Froyd, ACC 1509 Frank Kastenholz, Clearpoint Research 1510 Shirnshon Kaufman, 1511 Jim Kinder, Fibercom 1512 Cheryl Krupczak,NCR 1513 Paul Langille, Digital 1514 Peter Lin,Vitalink 1515 Keith McCloghrie, HLS 1516 Donna McMaster, SynOptics 1517 Dave Perkins, 3Com 1518 Jim Reinstedler, Ungermann Bass 1519 Anil Rijsinghani, Digital 1520 Mark Schaefer, David Systems 1521 Steve Sherry, Xyplex 1522 Bob Stewart, Xyplex 1523 Emil Sturniolo, 1524 Kevin Synott, Retix 1525 Ian Thomas, Chipcom 1526 Maurice Turcott, Racal 1527 Fei Xu, 1529 9. References 1531 [1] V. Cerf, IAB Recommendations for the Development of 1532 Internet Network Management Standards. Internet Working 1533 Group Request for Comments 1052. Network Information 1534 Center, SRI International, Menlo Park, California, 1535 (April, 1988). 1537 [2] V. Cerf, Report of the Second Ad Hoc Network Management 1538 Review Group, Internet Working Group Request for Comments 1539 1109. Network Information Center, SRI International, 1540 Menlo Park, California, (August, 1989). 1542 [3] M.T. Rose and K. McCloghrie, Structure and Identification 1543 of Management Information for TCP/IP-based internets, 1544 Internet Working Group Request for Comments 1155. 1545 Network Information Center, SRI International, Menlo 1546 Park, California, (May, 1990). 1548 [4] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, 1549 Simple Network Management Protocol, Internet Working 1550 Group Request for Comments 1157. Network Information 1551 Center, SRI International, Menlo Park, California, (May, 1552 1990). 1554 [5] K. McCloghrie and M.T. Rose (editors), Management 1555 Information Base for Network Management of TCP/IP-based 1556 internets: MIB-II, Internet Working Group Request for 1557 Comments 1213. Network Information Center, SRI 1558 International, Menlo Park, California, (March, 1991). 1560 [6] Information processing systems - Open Systems 1561 Interconnection - Specification of Abstract Syntax 1562 Notation One (ASN.1), International Organization for 1563 Standardization. International Standard 8824, (December, 1564 1987). 1566 [7] Information processing systems - Open Systems 1567 Interconnection - Specification of Basic Encoding Rules 1568 for Abstract Notation One (ASN.1), International 1569 Organization for Standardization. International Standard 1570 8825, (December, 1987). 1572 [8] M.T. Rose, K. McCloghrie (editors), Concise MIB 1573 Definitions, Internet Working Group Request for Comments 1574 1212. Network Information Center, SRI International, 1575 Menlo Park, California, (March, 1991). 1577 [9] M.T. Rose (editor), A Convention for Defining Traps for 1578 use with the SNMP, Internet Working Group Request for 1579 Comments 1215. Network Information Center, SRI 1580 International, Menlo Park, California, (March, 1991). 1582 [10] ANSI/IEEE Standard 802.1D-1990 MAC Bridges, IEEE Project 1583 802 Local and Metropolitan Area Networks, (March 8, 1584 1991). 1586 [11] ISO DIS 10038 MAC Bridges 1587 Table of Contents 1589 1 Abstract .............................................. 1 1590 2 Status of this Memo ................................... 1 1591 3 The Network Management Framework ...................... 2 1592 4 Objects ............................................... 2 1593 4.1 Format of Definitions ............................... 3 1594 5 Overview .............................................. 4 1595 5.1 Structure of MIB .................................... 4 1596 5.1.1 The dot1dBase Group ............................... 7 1597 5.1.2 The dot1dStp Group ................................ 7 1598 5.1.3 The dot1dSr Group ................................. 7 1599 5.1.4 The dot1dTp Group ................................. 7 1600 5.1.5 The dot1dStatic Group ............................. 7 1601 5.2 Relationship to Other MIBs .......................... 8 1602 5.2.1 Relationship to the 'system' group ................ 8 1603 5.2.2 Relationship to the 'interfaces' group ............ 8 1604 5.3 Textual Conventions ................................. 9 1605 6 Changes from RFC 1286 ................................. 9 1606 7 Definitions ........................................... 11 1607 7.1 Groups in the Bridge MIB ............................ 12 1608 7.2 The dot1dBase Group Definitions ..................... 13 1609 7.3 The dot1dStp Group Definitions ...................... 17 1610 7.4 The dot1dTp Group Definitions ....................... 26 1611 7.5 The dot1dStatic Group Definitions ................... 32 1612 7.6 Traps for use by Bridges ............................ 35 1613 8 Acknowledgments ....................................... 36 1614 9 References ............................................ 38 1616 Draft Expiration Date: March 1993