idnits 2.17.1 draft-ietf-bridge-sr-smiv2-obj-00.txt: 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-04-26) 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. == 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. ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 3. Overview' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 8. Security Considerations' ) ** 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 13 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 158 has weird spacing: '...sidered usefu...' == Line 534 has weird spacing: '...by this port ...' -- 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 () is 739384 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? '8' on line 785 looks like a reference -- Missing reference section? '1' on line 752 looks like a reference -- Missing reference section? '18' on line 819 looks like a reference -- Missing reference section? '2' on line 757 looks like a reference -- Missing reference section? '3' on line 761 looks like a reference -- Missing reference section? '4' on line 764 looks like a reference -- Missing reference section? '11' on line 797 looks like a reference -- Missing reference section? '12' on line 801 looks like a reference -- Missing reference section? '14' on line 805 looks like a reference -- Missing reference section? '16' on line 811 looks like a reference -- Missing reference section? '17' on line 816 looks like a reference -- Missing reference section? '5' on line 769 looks like a reference -- Missing reference section? '6' on line 774 looks like a reference -- Missing reference section? '7' on line 779 looks like a reference -- Missing reference section? '9' on line 789 looks like a reference -- Missing reference section? '10' on line 793 looks like a reference -- Missing reference section? '13' on line 803 looks like a reference -- Missing reference section? '15' on line 808 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 3 warnings (==), 20 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects for 3 Source Routing Bridges in the SNMPv2 SMI 5 7 20 February 13:28:00 EST 1996 9 Draft Expiration Date: August 1996 11 Eric B. Decker 12 cisco Systems, Inc. 13 cire@cisco.com 15 Keith McCloghrie 16 cisco Systems, Inc. 17 kzm@cisco.com 19 Paul Langille 20 Ascom Nexion, Inc. 21 langille@nexen.com 23 Anil Rijsinghani 24 Digital Equipment Corporation 25 anil@netcad.enet.dec.com 27 Status of this Memo 29 This document is an Internet Draft. Internet Drafts are 30 working documents of the Internet Engineering Task Force 31 (IETF), its Areas, and its Working Groups. Note that other 32 groups may also distribute working documents as Internet 33 Drafts. 35 Internet Drafts are valid for a maximum of six months and may 36 be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet Drafts as reference 38 material or to cite them other than as a "work in progress". 40 1. Introduction 42 This memo defines a portion of the Management Information Base 43 (MIB) for use with network management protocols in the 44 Internet community. In particular, it defines managed objects 45 used for managing source routing and source routing 46 transparent bridges. These bridges are also required to 47 implement relevant groups in the Bridge MIB [8]. 49 The MIB module contained in this memo is updated to be defined 50 using the SNMPv2 SMI [1], but is otherwise identical to that 51 contained in [18]. 53 2. The SNMPv2 Network Management Framework 55 The SNMPv2 Network Management Framework consists of three 56 major components. They are: 58 o RFC 1902 [1] which defines the SMI, the mechanisms used 59 for describing and naming objects for the purpose of 60 management. 62 o STD 17, RFC 1213 [2] defines MIB-II, the core set of 63 managed objects for the Internet suite of protocols. 65 o RFC 1157 [3] and/or RFC 1905 [4] which defines the 66 protocol used for network access to managed objects. 68 The Framework permits new objects to be defined for the 69 purpose of experimentation and evaluation. 71 2.1. Object Definitions 73 Managed objects are accessed via a virtual information store, 74 termed the Management Information Base or MIB. Objects in the 75 MIB are defined using the subset of Abstract Syntax Notation 76 One (ASN.1) defined in the SMI. In particular, each object 77 object type is named by an OBJECT IDENTIFIER, an 78 administratively assigned name. The object type together with 79 an object instance serves to uniquely identify a specific 80 instantiation of the object. For human convenience, we often 81 use a textual string, termed the descriptor, to refer to the 82 object type. 84 3. Overview 86 A common device present in many networks is the Bridge. This 87 device is used to connect Local Area Network segments below 88 the network layer. There are two major modes defined for this 89 bridging; transparent and source route. The transparent 90 method of bridging is defined in the IEEE 802.1d MAC Bridge 91 specification [11]. Source route bridging has been defined by 92 I.B.M. and is described in the Token Ring Architecture 93 Reference[12], as well as the IEEE 802.5M SRT Bridge 94 Operations Addendum [14] to 802.1d. This memo defines objects 95 needed for management of a source routing bridge, and is an 96 extension to the SNMP Bridge MIB [8]. 98 An explicit attempt was made to keep this MIB as simple as 99 possible. This was accomplished by applying the following 100 criteria to objects proposed for inclusion: 102 (1) Start with a small set of essential objects and add only 103 as further objects are needed. 105 (2) Require objects be essential for either fault or 106 configuration management. 108 (3) Consider evidence of current use and/or utility. 110 (4) Limit the total of objects. 112 (5) Exclude objects which are simply derivable from others in 113 this or other MIBs. 115 (6) Avoid causing critical sections to be heavily 116 instrumented. The guideline that was followed is one 117 counter per critical section per layer. 119 3.1. Structure of MIB 121 Objects in this MIB are arranged into groups. Each group is 122 organized as a set of related objects. The overall structure 123 and assignment of objects to their groups is shown below. 124 Where appropriate, the corresponding management object name 125 found in IEEE 802.1d[11] and IEEE 802.5M [14] is also 126 included. 128 SR Bridge MIB Name IEEE Name 130 dot1dSr 131 PortTable 132 Port SourceRoutingPort 133 HopCount 134 LocalSegment .SegmentNumber 135 BridgeNum .BridgeNumber 136 TargetSegment 137 LargestFrame .LargestFrameSize 138 STESpanMode .LimitedBroadcastMode 139 SpecInFrames BridgePort 140 .ValidSRFramesReceived 141 SpecOutFrames .ValidSRForwardedOutbound 142 ApeInFrames 143 ApeOutFrames .BroadcastFramesForwarded 144 SteInFrames 145 SteOutFrames .BroadcastFramesForwarded 146 SegmentMismatchDiscards .DiscardInvalidRI 147 DuplicateSegmentDiscards .LanIdMismatch 148 HopCountExceededDiscards .FramesDiscardedHopCountExceeded 150 The following IEEE management objects have not been included 151 in the SR Bridge MIB for the indicated reasons. 153 IEEE Object Disposition 155 SourceRoutingPort 156 The following objects were NOT 157 included in this MIB because they are 158 redundant or not considered useful. 159 .LimitedBroadcastEnable 160 .DiscardLackOfBuffers 161 .DiscardErrorDetails 162 .DiscardTargetLANInoperable 163 .ValidSRDiscardedInbound 164 .BroadcastBytesForwarded 165 .NonBroadcastBytesForwarded 166 .FramesNotReceivedDueToCongestion 167 .FramesDiscardedDueToInternalError 169 3.1.1. The dot1dSr Group 171 This group contains the objects that describe the entity's 172 state with respect to source route bridging. If source 173 routing is not supported, this group will not be implemented. 174 This group is applicable to source route only, and SRT 175 bridges. 177 3.1.2. The dot1dPortPair Group 179 Implementation of this group is optional. This group is 180 implemented by those bridges that support the port-pair 181 multiport model of the source route bridging mode as defined 182 in the IEEE 802.5M SRT Addendum to 802.1d. 184 3.2. Relationship to Other MIBs 186 As described above, some IEEE 802.1d management objects have 187 not been included in this MIB because they overlap with 188 objects in other MIBs applicable to a bridge implementing this 189 MIB. In particular, it is assumed that a bridge implementing 190 this MIB will also implement (at least) the Bridge MIB [8] and 191 the 'system' group [16] and the 'interfaces' group [17]. 193 3.2.1. Relationship to the Bridge MIB 195 The Bridge MIB [8] must be implemented by all bridges, 196 including transparent, SR and SRT bridges. The SR bridge MIB 197 is an extension to the Bridge MIB. 199 3.2.2. Relationship to the 'system' group 201 In [16], the 'system' group is defined as being mandatory for 202 all systems such that each managed entity contains one 203 instance of each object in the 'system' group. Thus, those 204 objects apply to the entity as a whole irrespective of whether 205 the entity's sole functionality is bridging, or whether 206 bridging is only a subset of the entity's functionality. 208 3.2.3. Relationship to the 'interfaces' group 210 In [17], the 'interfaces' group is defined as being mandatory 211 for all systems and contains information on an entity's 212 interfaces, where each interface is thought of as being 213 attached to a `subnetwork'. (Note that this term is not to be 214 confused with `subnet' which refers to an addressing 215 partitioning scheme used in the Internet suite of protocols.) 216 The term 'segment' is used in this memo to refer to such a 217 subnetwork. 219 Implicit in this MIB is the notion of ports on a bridge. Each 220 of these ports is associated with one interface of the 221 'interfaces' group, and in most situations, each port is 222 associated with a different interface. However, there are 223 situations in which multiple ports are associated with the 224 same interface. An example of such a situation would be 225 several ports, each corresponding one-to-one with several X.25 226 virtual circuits, but all on the same interface. 228 Each port is uniquely identified by a port number. A port 229 number has no mandatory relationship to an interface number, 230 but in the simple case, a port number will have the same value 231 as the corresponding interface's interface number. 233 Some entities provide other services in addition to bridging 234 with respect to the data sent and received by their 235 interfaces. In such situations, only a subset of the data 236 sent/received on an interface is within the domain of the 237 entity's bridging functionality. This subset is considered to 238 be delineated according to a set of protocols, with some 239 protocols being bridged, and other protocols not being 240 bridged. For example, in an entity which exclusively performed 241 bridging, all protocols would be considered as being bridged, 242 whereas in an entity which performed IP routing on IP 243 datagrams and only bridged other protocols, only the non-IP 244 data would be considered as being bridged. 246 Thus, this MIB (and in particular, its counters) are 247 applicable only to that subset of the data on an entity's 248 interfaces which is sent/received for a protocol being 249 bridged. All such data is sent/received via the ports of the 250 bridge. 252 4. Changes from RFC 1525 254 (1) Removed dot1dSrPortLanIdMismatches, as it is redundant 255 with dot1dSrPortSegmentMismatchDiscards. 257 (2) Replaced the words "explorer frames" in the definition of 258 dot1dSrPortSegmentMismatchDiscards with the words "ARE 259 and STE explorer frames" for clarification. 261 (3) Revised definition of dot1dSrPortHopCount. 263 5. Definitions 265 SR-BRIDGE-MIB DEFINITIONS ::= BEGIN 267 IMPORTS 268 MODULE-IDENTITY, OBJECT-TYPE, 269 Integer32,Counter32, Gauge32 FROM SNMPv2-SMI 270 dot1dBridge, dot1dBridge FROM BRIDGE-MIB 271 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-TC; 273 -- groups in the SR MIB 275 -- dot1dSr is imported from the Bridge MIB 277 dot1dSr MODULE-IDENTITY 278 LAST-UPDATED "9202201328Z" 279 ORGANIZATION "IETF Bridge MIB Working Group" 280 CONTACT-INFO 281 " Anil Rijsinghani 282 Postal: Digital Equipment Corporation 283 550 King St 284 Littleton, MA 01460. 286 Email: anil@netcad.enet.dec.com" 287 DESCRIPTION 288 "The MIB module for 802.1d Source Routing Bridges." 289 ::= { dot1dBridge 3 } 291 dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 } 292 -- use 10, to be safe 294 -- the dot1dSr group 296 -- this group is implemented by those bridges that 297 -- support the source route bridging mode, including Source 298 -- Routing and SRT bridges. 300 dot1dSrPortTable OBJECT-TYPE 301 SYNTAX SEQUENCE OF Dot1dSrPortEntry 302 MAX-ACCESS not-accessible 303 STATUS current 304 DESCRIPTION 305 "A table that contains information about every 306 port that is associated with this source route 307 bridge." 308 ::= { dot1dSr 1 } 310 dot1dSrPortEntry OBJECT-TYPE 311 SYNTAX Dot1dSrPortEntry 312 MAX-ACCESS not-accessible 313 STATUS current 314 DESCRIPTION 315 "A list of information for each port of a source 316 route bridge." 317 INDEX { dot1dSrPort } 318 ::= { dot1dSrPortTable 1 } 320 Dot1dSrPortEntry ::= 321 SEQUENCE { 322 dot1dSrPort INTEGER, 323 dot1dSrPortHopCount Integer32, 324 dot1dSrPortLocalSegment Integer32, 325 dot1dSrPortBridgeNum Integer32, 326 dot1dSrPortTargetSegment Integer32, 327 dot1dSrPortLargestFrame Integer32, 328 dot1dSrPortSTESpanMode INTEGER, 329 dot1dSrPortSpecInFrames Counter32, 330 dot1dSrPortSpecOutFrames Counter32, 331 dot1dSrPortApeInFrames Counter32, 332 dot1dSrPortApeOutFrames Counter32, 333 dot1dSrPortSteInFrames Counter32, 334 dot1dSrPortSteOutFrames Counter32, 335 dot1dSrPortSegmentMismatchDiscards Counter32, 336 dot1dSrPortDuplicateSegmentDiscards Counter32, 337 dot1dSrPortHopCountExceededDiscards Counter32, 338 dot1dSrPortDupLanIdOrTreeErrors Counter32 339 } 341 dot1dSrPort OBJECT-TYPE 342 SYNTAX INTEGER (1..65535) 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The port number of the port for which this entry 347 contains Source Route management information." 348 ::= { dot1dSrPortEntry 1 } 350 dot1dSrPortHopCount OBJECT-TYPE 351 SYNTAX Integer32 352 MAX-ACCESS read-write 353 STATUS current 354 DESCRIPTION 355 "The maximum number of route descriptors allowed 356 in All Routes Explorer frames transmitted on this 357 port." 358 ::= { dot1dSrPortEntry 2 } 360 dot1dSrPortLocalSegment OBJECT-TYPE 361 SYNTAX Integer32 362 MAX-ACCESS read-write 363 STATUS current 364 DESCRIPTION 365 "The segment number that uniquely identifies the 366 segment to which this port is connected. Current 367 source routing protocols limit this value to the 368 range: 0 through 4095. (The value 0 is used by 369 some management applications for special test 370 cases.) A value of 65535 signifies that no segment 371 number is assigned to this port." 372 ::= { dot1dSrPortEntry 3 } 374 dot1dSrPortBridgeNum OBJECT-TYPE 375 SYNTAX Integer32 376 MAX-ACCESS read-write 377 STATUS current 378 DESCRIPTION 379 "A bridge number uniquely identifies a bridge when 380 more than one bridge is used to span the same two 381 segments. Current source routing protocols limit 382 this value to the range: 0 through 15. A value of 383 65535 signifies that no bridge number is assigned 384 to this bridge." 385 ::= { dot1dSrPortEntry 4 } 387 dot1dSrPortTargetSegment OBJECT-TYPE 388 SYNTAX Integer32 389 MAX-ACCESS read-write 390 STATUS current 391 DESCRIPTION 392 "The segment number that corresponds to the target 393 segment this port is considered to be connected to 394 by the bridge. Current source routing protocols 395 limit this value to the range: 0 through 4095. 396 (The value 0 is used by some management 397 applications for special test cases.) A value of 398 65535 signifies that no target segment is assigned 399 to this port." 400 ::= { dot1dSrPortEntry 5 } 402 -- It would be nice if we could use ifMtu as the size of the 403 -- largest frame, but we can't because ifMtu is defined to be 404 -- the size that the (inter-)network layer can use which can 405 -- differ from the MAC layer (especially if several layers of 406 -- encapsulation are used). 408 dot1dSrPortLargestFrame OBJECT-TYPE 409 SYNTAX Integer32 410 MAX-ACCESS read-write 411 STATUS current 412 DESCRIPTION 413 "The maximum size of the INFO field (LLC and 414 above) that this port can send/receive. It does 415 not include any MAC level (framing) octets. The 416 value of this object is used by this bridge to 417 determine whether a modification of the 418 LargestFrame (LF, see [14]) field of the Routing 419 Control field of the Routing Information Field is 420 necessary. 422 64 valid values are defined by the IEEE 802.5M SRT 423 Addendum: 516, 635, 754, 873, 993, 1112, 1231, 424 1350, 1470, 1542, 1615, 1688, 1761, 1833, 1906, 425 1979, 2052, 2345, 2638, 2932, 3225, 3518, 3812, 426 4105, 4399, 4865, 5331, 5798, 6264, 6730, 7197, 427 7663, 8130, 8539, 8949, 9358, 9768, 10178, 10587, 428 10997, 11407, 12199, 12992, 13785, 14578, 15370, 429 16163, 16956, 17749, 20730, 23711, 26693, 29674, 430 32655, 35637, 38618, 41600, 44591, 47583, 50575, 431 53567, 56559, 59551, and 65535. 433 An illegal value will not be accepted by the 434 bridge." 435 ::= { dot1dSrPortEntry 6 } 437 dot1dSrPortSTESpanMode OBJECT-TYPE 438 SYNTAX INTEGER { 439 auto-span(1), 440 disabled(2), 441 forced(3) 442 } 443 MAX-ACCESS read-write 444 STATUS current 445 DESCRIPTION 446 "Determines how this port behaves when presented 447 with a Spanning Tree Explorer frame. The value 448 'disabled(2)' indicates that the port will not 449 accept or send Spanning Tree Explorer packets; any 450 STE packets received will be silently discarded. 451 The value 'forced(3)' indicates the port will 452 always accept and propagate Spanning Tree Explorer 453 frames. This allows a manually configured 454 Spanning Tree for this class of packet to be 455 configured. Note that unlike transparent 456 bridging, this is not catastrophic to the network 457 if there are loops. The value 'auto-span(1)' can 458 only be returned by a bridge that both implements 459 the Spanning Tree Protocol and has use of the 460 protocol enabled on this port. The behavior of the 461 port for Spanning Tree Explorer frames is 462 determined by the state of dot1dStpPortState. If 463 the port is in the 'forwarding' state, the frame 464 will be accepted or propagated. Otherwise, it 465 will be silently discarded." 466 ::= { dot1dSrPortEntry 7 } 468 dot1dSrPortSpecInFrames OBJECT-TYPE 469 SYNTAX Counter32 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION 473 "The number of Specifically Routed frames, also 474 referred to as Source Routed Frames, that have 475 been received from this port's segment." 476 ::= { dot1dSrPortEntry 8 } 478 dot1dSrPortSpecOutFrames OBJECT-TYPE 479 SYNTAX Counter32 480 MAX-ACCESS read-only 481 STATUS current 482 DESCRIPTION 483 "The number of Specifically Routed frames, also 484 referred to as Source Routed Frames, that this 485 port has transmitted on its segment." 486 ::= { dot1dSrPortEntry 9 } 488 dot1dSrPortApeInFrames OBJECT-TYPE 489 SYNTAX Counter32 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "The number of All Paths Explorer frames, also 494 referred to as All Routes Explorer frames, that 495 have been received by this port from its segment." 496 ::= { dot1dSrPortEntry 10 } 498 dot1dSrPortApeOutFrames OBJECT-TYPE 499 SYNTAX Counter32 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The number of all Paths Explorer Frames, also 504 referred to as All Routes Explorer frames, that 505 have been transmitted by this port on its 506 segment." 507 ::= { dot1dSrPortEntry 11 } 509 dot1dSrPortSteInFrames OBJECT-TYPE 510 SYNTAX Counter32 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "The number of spanning tree explorer frames that 515 have been received by this port from its segment." 516 ::= { dot1dSrPortEntry 12 } 518 dot1dSrPortSteOutFrames OBJECT-TYPE 519 SYNTAX Counter32 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "The number of spanning tree explorer frames that 524 have been transmitted by this port on its 525 segment." 526 ::= { dot1dSrPortEntry 13 } 528 dot1dSrPortSegmentMismatchDiscards OBJECT-TYPE 529 SYNTAX Counter32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "The number of ARE and STE explorer frames that 534 have been discarded by this port because the 535 routing descriptor field contained an invalid 536 adjacent segment value." 537 ::= { dot1dSrPortEntry 14 } 539 dot1dSrPortDuplicateSegmentDiscards OBJECT-TYPE 540 SYNTAX Counter32 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "The number of frames that have been discarded by 545 this port because the routing descriptor field 546 contained a duplicate segment identifier." 547 ::= { dot1dSrPortEntry 15 } 549 dot1dSrPortHopCountExceededDiscards OBJECT-TYPE 550 SYNTAX Counter32 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "The number of explorer frames that have been 555 discarded by this port because the Routing 556 Information Field has exceeded the maximum route 557 descriptor length." 558 ::= { dot1dSrPortEntry 16 } 560 dot1dSrPortDupLanIdOrTreeErrors OBJECT-TYPE 561 SYNTAX Counter32 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "The number of duplicate LAN IDs or Tree errors. 566 This helps in detection of problems in networks 567 containing older IBM Source Routing Bridges." 568 ::= { dot1dSrPortEntry 17 } 570 -- scalar object in dot1dSr 572 dot1dSrBridgeLfMode OBJECT-TYPE 573 SYNTAX INTEGER { 574 mode3(1), 575 mode6(2) 576 } 577 MAX-ACCESS read-write 578 STATUS current 579 DESCRIPTION 580 "Indicates whether the bridge operates using older 581 3 bit length negotiation fields or the newer 6 bit 582 length field in its RIF." 583 ::= { dot1dSr 2 } 585 -- The Port-Pair Database 587 -- Implementation of this group is optional. 589 -- This group is implemented by those bridges that support the 590 -- direct multiport model of the source route bridging mode as 591 -- defined in the IEEE 802.5 SRT Addendum to 802.1d. 593 -- Bridges implementing this group may report 65535 for 594 -- dot1dSrPortBridgeNumber and dot1dSrPortTargetSegment, indicating 595 -- that those objects are not applicable. 597 dot1dPortPairTableSize OBJECT-TYPE 598 SYNTAX Gauge32 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "The total number of entries in the Bridge Port 603 Pair Database." 604 ::= { dot1dPortPair 1 } 606 -- the Bridge Port-Pair table 608 -- this table represents port pairs within a bridge forming 609 -- a unique bridge path, as defined in the IEEE 802.5M SRT 610 -- Addendum. 612 dot1dPortPairTable OBJECT-TYPE 613 SYNTAX SEQUENCE OF Dot1dPortPairEntry 614 MAX-ACCESS not-accessible 615 STATUS current 616 DESCRIPTION 617 "A table that contains information about every 618 port pair database entity associated with this 619 source routing bridge." 620 ::= { dot1dPortPair 2 } 622 dot1dPortPairEntry OBJECT-TYPE 623 SYNTAX Dot1dPortPairEntry 624 MAX-ACCESS not-accessible 625 STATUS current 626 DESCRIPTION 627 "A list of information for each port pair entity 628 of a bridge." 630 INDEX { dot1dPortPairLowPort, dot1dPortPairHighPort } 631 ::= { dot1dPortPairTable 1 } 633 Dot1dPortPairEntry ::= 634 SEQUENCE { 635 dot1dPortPairLowPort INTEGER, 636 dot1dPortPairHighPort INTEGER, 637 dot1dPortPairBridgeNum Integer32, 638 dot1dPortPairBridgeState INTEGER 639 } 641 dot1dPortPairLowPort OBJECT-TYPE 642 SYNTAX INTEGER (1..65535) 643 MAX-ACCESS read-write 644 STATUS current 645 DESCRIPTION 646 "The port number of the lower numbered port for 647 which this entry contains port pair database 648 information." 649 ::= { dot1dPortPairEntry 1 } 651 dot1dPortPairHighPort OBJECT-TYPE 652 SYNTAX INTEGER (1..65535) 653 MAX-ACCESS read-write 654 STATUS current 655 DESCRIPTION 656 "The port number of the higher numbered port for 657 which this entry contains port pair database 658 information." 659 ::= { dot1dPortPairEntry 2 } 661 dot1dPortPairBridgeNum OBJECT-TYPE 662 SYNTAX Integer32 663 MAX-ACCESS read-write 664 STATUS current 665 DESCRIPTION 666 "A bridge number that uniquely identifies the path 667 provided by this source routing bridge between the 668 segments connected to dot1dPortPairLowPort and 669 dot1dPortPairHighPort. The purpose of bridge 670 number is to disambiguate between multiple paths 671 connecting the same two LANs." 672 ::= { dot1dPortPairEntry 3 } 674 dot1dPortPairBridgeState OBJECT-TYPE 675 SYNTAX INTEGER { 676 enabled(1), 677 disabled(2), 678 invalid(3) 679 } 680 MAX-ACCESS read-write 681 STATUS current 682 DESCRIPTION 683 "The state of dot1dPortPairBridgeNum. Writing 684 'invalid(3)' to this object removes the 685 corresponding entry." 686 ::= { dot1dPortPairEntry 4 } 688 -- conformance information 690 srBridgeConformance OBJECT IDENTIFIER ::= { dot1dBridge 11 } 692 srBridgeGroups OBJECT IDENTIFIER ::= { srBridgeConformance 1} 693 srBridgeCompliances OBJECT IDENTIFIER ::= { srBridgeConformance 2} 695 -- compliance statements 697 srBridgeCompliance MODULE-COMPLIANCE 698 STATUS current 699 DESCRIPTION 700 "The compliance statement for SNMPv2 entities which 701 implement the SR Bridge MIB." 703 MODULE -- this module 704 MANDATORY-GROUPS { dot1dSr } 706 ::= { srBridgeCompliances 1 } 708 -- units of conformance 710 dot1dSr OBJECT-GROUP 711 OBJECTS { dot1dSrPort, dot1dSrPortHopCount, 712 dot1dSrPortLocalSegment, dot1dSrPortBridgeNum, 713 dot1dSrPortTargetSegment, dot1dSrPortLargestFrame, 714 dot1dSrPortSTESpanMode, dot1dSrPortSpecInFrames, 715 dot1dSrPortSpecOutFrames, dot1dSrPortApeInFrames, 716 dot1dSrPortApeOutFrames, dot1dSrPortSteInFrames, 717 dot1dSrPortSteOutFrames, 718 dot1dSrPortSegmentMismatchDiscards, 719 dot1dSrPortDuplicateSegmentDiscards, 720 dot1dSrPortHopCountExceededDiscards, 721 dot1dSrPortDupLanIdOrTreeErrors } 722 STATUS current 723 DESCRIPTION 724 "A collection of objects providing management 725 information for source route bridges." 726 ::= { dot1dBridge 3 } 728 dot1dPortPair OBJECT-GROUP 729 OBJECTS { dot1dPortPairLowPort, dot1dPortPairHighPort 730 dot1dPortPairBridgeNum, dot1dPortPairBridgeState } 732 STATUS current 733 DESCRIPTION 734 "A collection of objects implemented by those SR 735 bridges that support the direct multiport model of the 736 source route bridging mode as defined in the IEEE SRT 737 specification." 738 ::= { dot1dBridge 10 } 740 END 741 6. Acknowledgments 743 This document was produced on behalf of the Bridge MIB Working 744 Group in the NM area of the Internet Engineering Task Force. 746 The authors wish to thank the members of the Bridge MIB 747 Working Group for their many comments and suggestions which 748 improved this effort. 750 7. References 752 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 753 and S. Waldbusser, "Structure of Management Information 754 for version 2 of the Simple Network Management Protocol 755 (SNMPv2)", RFC 1902, January 1996. 757 [2] McCloghrie, K., and M. Rose, Editors, "Management 758 Information Base for Network Management of TCP/IP-based 759 internets: MIB-II", STD 17, RFC 1213, March 1991. 761 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 762 "Simple Network Management Protocol", RFC 1157, May 1990. 764 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 765 and S. Waldbusser, "Protocol Operations for version 2 of 766 the Simple Network Management Protocol (SNMPv2)", RFC 767 1905, January 1996. 769 [5] Rose M., and K. McCloghrie, "Structure and Identification 770 of Management Information for TCP/IP-based internets", 771 STD 16, RFC 1155, Performance Systems International, 772 Hughes LAN Systems, May 1990. 774 [6] McCloghrie K., and M. Rose, Editors, "Management 775 Information Base for Network Management of TCP/IP-based 776 internets", STD 17, RFC 1213, Performance Systems 777 International, March 1991. 779 [7] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 780 "Simple Network Management Protocol", STD 15, RFC 1157, 781 SNMP Research, Performance Systems International, 782 Performance Systems International, MIT Laboratory for 783 Computer Science, May 1990. 785 [8] Decker, E., Langille, P., Rijsinghani, A., and 786 McCloghrie, K., "Definitions of Managed Objects for 787 Bridges", RFC 1493, July 1993. 789 [9] Rose, M., and K. McCloghrie, Editors, "Concise MIB 790 Definitions", STD 16, RFC 1212, Performance Systems 791 International, Hughes LAN Systems, March 1991. 793 [10] Rose, M., Editor, "A Convention for Defining Traps for 794 use with the SNMP", RFC 1215, Performance Systems 795 International, March 1991. 797 [11] ANSI/IEEE Standard 802.1D-1990 MAC Bridges, IEEE Project 798 802 Local and Metropolitan Area Networks, (March 8, 799 1991). 801 [12] I.B.M. Token Ring Architecture Reference. 803 [13] ISO DIS 10038 MAC Bridges. 805 [14] ANSI/IEEE P802.5M-Draft 7, "Source Routing Transparent 806 Bridge Operation", IEEE Project 802 (1991). 808 [15] ANSI/IEEE 802.1y, "Source Routing Tutorial for End System 809 Operation", September, 1990) 811 [16] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 812 and S. Waldbusser, "Management Information Base for 813 version 2 of the Simple Network Management Protocol 814 (SNMPv2)", RFC1905, January 1996. 816 [17] McCloghrie, K., and F. Kastenholz, "Evolution of the 817 Interfaces Group of MIB-II", RFC 1573, January 1994. 819 [18] Decker, E., McCloghrie, K., Langille, P., and A. 820 Rijsinghani, "Definitions of Managed Objects for Source 821 Routing Bridges", Internet Draft, 19 Feb 1996 [Work in 822 Progress]. 824 8. Security Considerations 826 Security issues are not discussed in this memo. 828 9. Authors' Address 830 Eric B. Decker 831 cisco Systems, Inc. 832 170 West Tasman Drive, 833 San Jose CA 95134 834 (408) 526 8241 835 cire@cisco.com 837 Keith McCloghrie 838 cisco Systems, Inc. 839 170 West Tasman Drive, 840 San Jose CA 95134 841 (408) 526 5260 842 kzm@cisco.com 844 Paul Langille 845 Ascom Nexion, Inc. 846 289 Great Road 847 Acton, MA 01720-4739 848 (508) 266 3401 849 langille@nexen.com 851 Anil Rijsinghani 852 Digital Equipment Corporation 853 550 King Street 854 Littleton, MA 01460 855 (508) 486 6786 856 anil@netcad.enet.dec.com 857 Table of Contents 859 1 Introduction .......................................... 2 860 2 The SNMPv2 Network Management Framework ............... 3 861 2.1 Object Definitions .................................. 3 862 3 Overview .............................................. 4 863 3.1 Structure of MIB .................................... 4 864 3.1.1 The dot1dSr Group ................................. 6 865 3.1.2 The dot1dPortPair Group ........................... 6 866 3.2 Relationship to Other MIBs .......................... 6 867 3.2.1 Relationship to the Bridge MIB .................... 6 868 3.2.2 Relationship to the 'system' group ................ 6 869 3.2.3 Relationship to the 'interfaces' group ............ 6 870 4 Changes from RFC 1525 ................................. 7 871 5 Definitions ........................................... 9 872 5.1 Groups in the SR MIB ................................ 9 873 5.2 The dot1dSr Group Definitions ....................... 10 874 5.3 The dot1dPortPair Group Definitions ................. 18 875 6 Acknowledgments ....................................... 23 876 7 References ............................................ 24 877 8 Security Considerations ............................... 26 878 9 Authors' Address ...................................... 26