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