idnits 2.17.1 draft-ietf-hubmib-repeater-dev-03.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-20) 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 90 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Overview' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 7. 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 142 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** There are 89 instances of lines with control characters in the document. ** The abstract seems to contain references ([2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [12], [13], [14], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1972: '... of this object MUST be a valid count...' RFC 2119 keyword, line 2010: '... of this object MUST be a valid count...' RFC 2119 keyword, line 2226: '... of this object MUST be a valid count...' RFC 2119 keyword, line 2260: '... of this object MUST be a valid count...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1678 has weird spacing: '... of the parti...' == Line 2428 has weird spacing: '... object to 'n...' == Line 2635 has weird spacing: '...maximum numbe...' -- 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 (14 September 1996) is 10080 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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? '6' on line 3890 looks like a reference -- Missing reference section? '5' on line 3885 looks like a reference -- Missing reference section? '10' on line 3912 looks like a reference -- Missing reference section? '9' on line 3905 looks like a reference -- Missing reference section? '7' on line 3895 looks like a reference -- Missing reference section? '8' on line 3900 looks like a reference -- Missing reference section? '11' on line 3917 looks like a reference -- Missing reference section? '1' on line 3867 looks like a reference -- Missing reference section? '2' on line 3872 looks like a reference -- Missing reference section? '3' on line 3877 looks like a reference -- Missing reference section? '12' on line 3921 looks like a reference -- Missing reference section? '13' on line 3927 looks like a reference -- Missing reference section? '4' on line 3880 looks like a reference -- Missing reference section? '14' on line 3930 looks like a reference Summary: 15 errors (**), 0 flaws (~~), 5 warnings (==), 17 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft 802.3 Repeater MIB 14 September 1996 4 Definitions of Managed Objects 5 for IEEE 802.3 Repeater Devices 7 14 September 1996 9 11 Kathryn de Graaf 12 3Com Corporation 14 Dan Romascanu 15 Madge Networks (Israel) Ltd. 17 Donna McMaster 18 Coloma Communications 20 Keith McCloghrie 21 Cisco Systems Inc. 23 , 25 Status of this Memo 27 This document is an Internet-Draft. Internet-Drafts are 28 working documents of the Internet Engineering Task Force 29 (IETF), its areas, and its working groups. Note that other 30 groups may also distribute working documents as Internet- 31 Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six 34 months and may be updated, replaced, or obsoleted by other 35 documents at any time. It is inappropriate to use Internet- 36 Drafts as reference material or to cite them other than as a 37 "work in progress". 39 To learn the current status of any Internet-Draft, please 40 check the "1id-abstracts.txt" listing contained in the 41 Internet-Drafts Shadow Directories on ds.internic.net (US East 42 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 43 or munnari.oz.au (Pacific Rim). 45 Abstract 47 This memo defines an experimental portion of the Management 48 Information Base (MIB) for use with network management 49 protocols in the Internet community. In particular, it 50 defines objects for managing IEEE 802.3 10 and 100 Mb/second 51 baseband repeaters based on IEEE Std 802.3 Section 30, "10 & 52 100 Mb/s Management," October 26, 1995. 54 This memo does not specify a standard for the Internet 55 community. 57 1. The SNMP Network Management Framework 59 The SNMP Network Management Framework presently consists of 60 three major components. They are: 62 o the SMI, described in RFC 1902 [6] - the mechanisms used 63 for describing and naming objects for the purpose of 64 management. 66 , 68 o the MIB-II, STD 17, RFC 1213 [5] - the core set of 69 managed objects for the Internet suite of protocols. 71 o the protocol, RFC 1157 [10] and/or RFC 1905 [9] - the 72 protocol used for accessing managed information. 74 Textual conventions are defined in RFC 1903 [7], and 75 conformance statements are defined in RFC 1904 [8]. 77 The Framework permits new objects to be defined for the 78 purpose of experimentation and evaluation. 80 1.1. Object Definitions 82 Managed objects are accessed via a virtual information store, 83 termed the Management Information Base or MIB. Objects in the 84 MIB are defined using the subset of Abstract Syntax Notation 85 One (ASN.1) defined in the SMI. In particular, each object 86 type is named by an OBJECT IDENTIFIER, an administratively 87 assigned name. The object type together with an object 88 instance serves to uniquely identify a specific instantiation 89 of the object. For human convenience, we often use a textual 90 string, termed the descriptor, to refer to the object type. 92 , 93 2. Overview 95 2.1. Relationship to RFC 1516 97 This MIB is intended as a superset of that defined by RFC 1516 98 [11], which will go to historic status. This MIB includes all 99 of the objects contained in that MIB, plus several new ones 100 which provide for significant additional capabilities. 101 Implementors are encouraged to support all applicable 102 conformance groups in order to make the best use of the new 103 functionality provided by this MIB. The new objects provide 104 support for: 106 o multiple repeaters 108 o 100BASE-T management 110 o port TopN capability 112 o address search and topology mapping 114 Certain objects have been deprecated; in particular, those 115 scalar objects used for managing a single repeater are now of 116 minimal use since they are duplicated in the new multiple- 117 repeater definitions. Additional objects have been deprecated 118 based on implementation experience with RFC 1516. 120 2.2. Repeater Management 122 Instances of the object types defined in this memo represent 123 attributes of an IEEE 802.3 (Ethernet-like) repeater, as 124 defined by Section 9, "Repeater Unit for 10 Mb/s Baseband 125 Networks" in the IEEE 802.3/ISO 8802-3 CSMA/CD standard [1], 126 and Section 27, "Repeater for 100 Mb/s Baseband Networks" in 127 the IEEE Standard 802.3u-1995 [2]. 129 These Repeater MIB objects may be used to manage non-standard 130 repeater-like devices, but defining objects to describe 131 implementation-specific properties of non-standard repeater- 132 like devices is outside the scope of this memo. 134 The definitions presented here are based on Section 30.4, 135 "Layer Management for 10 and 100 Mb/s Baseband Repeaters" and 136 Annex 30A, "GDMO Specificataions for 802.3 managed objects" of 138 , 140 [3]. 142 Implementors of these MIB objects should note that [3] 143 explicitly describes when, where, and how various repeater 144 attributes are measured. The IEEE document also describes the 145 effects of repeater actions that may be invoked by 146 manipulating instances of the MIB objects defined here. 148 The counters in this document are defined to be the same as 149 those counters in [3], with the intention that the same 150 instrumentation can be used to implement both the IEEE and 151 IETF management standards. 153 2.3. Structure of the MIB 155 Objects in this MIB are arranged into packages, each of which 156 contains a set of related objects within a broad functional 157 category. Objects within a package are generally defined 158 under the same OID subtree. These packages are intended for 159 organizational convenience ONLY, and have no relation to the 160 conformance groups defined later in the document. 162 2.3.1. Basic Definitions 164 The basic definitions include objects which are applicable to 165 all repeaters: status, parameter and control objects for each 166 repeater within the managed system, for the port groups within 167 the system, and for the individual ports themselves. 169 2.3.2. Monitor Definitions 171 The monitor definitions include monitoring statistics for each 172 repeater within the system and for individual ports. 174 2.3.3. Address Tracking Definitions 176 This collection includes objects for tracking the MAC 177 addresses of the DTEs attached to the ports within the system 178 and for mapping the topology of a network. 180 , 181 Note: These definitions are based on a technology which has 182 been patented by Hewlett-Packard Company. HP has granted 183 rights to this technology to implementors of this MIB. See 184 [12] and [13] for details. 186 2.3.4. Top N Definitions 188 These objects may be used for tracking the ports with the most 189 activity within the system or within particular repeaters. 191 2.4. Relationship to Other MIBs 193 2.4.1. Relationship to MIB-II 195 It is assumed that a repeater implementing this MIB will also 196 implement (at least) the 'system' group defined in MIB-II [5]. 198 2.4.1.1. Relationship to the 'system' group 200 In MIB-II, the 'system' group is defined as being mandatory 201 for all systems such that each managed entity contains one 202 instance of each object in the 'system' group. Thus, those 203 objects apply to the entity even if the entity's sole 204 functionality is management of repeaters. 206 2.4.1.2. Relationship to the 'interfaces' group 208 In MIB-II, the 'interfaces' group is defined as being 209 mandatory for all systems and contains information on an 210 entity's interfaces, where each interface is thought of as 211 being attached to a 'subnetwork'. (Note that this term is not 212 to be confused with 'subnet' which refers to an addressing 213 partitioning scheme used in the Internet suite of protocols.) 215 This Repeater MIB uses the notion of ports on a repeater. The 216 concept of a MIB-II interface has NO specific relationship to 217 a repeater's port. Therefore, the 'interfaces' group applies 218 only to the one (or more) network interfaces on which the 219 entity managing the repeater sends and receives management 220 protocol operations, and does not apply to the repeater's 221 ports. 223 , 224 This is consistent with the physical-layer nature of a 225 repeater. A repeater is a bitwise store-and-forward device. 226 It recognizes activity and bits, but does not process incoming 227 data based on any packet-related information (such as checksum 228 or addresses). A repeater has no MAC address, no MAC 229 implementation, and does not pass packets up to higher-level 230 protocol entities for processing. 232 (When a network management entity is observing a repeater, it 233 may appear as though the repeater is passing packets to a 234 higher-level protocol entity. However, this is only a means 235 of implementing management, and this passing of management 236 information is not part of the repeater functionality.) 238 , 239 3. Definitions 241 SNMP-REPEATER-MIB DEFINITIONS ::= BEGIN 243 IMPORTS 244 Counter32, Counter64, Integer32, Gauge32, TimeTicks, 245 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 246 FROM SNMPv2-SMI 247 TimeStamp, DisplayString, MacAddress, TEXTUAL-CONVENTION, 248 RowStatus, TestAndIncr 249 FROM SNMPv2-TC 250 OBJECT-GROUP, MODULE-COMPLIANCE 251 FROM SNMPv2-CONF 252 OwnerString 253 FROM IF-MIB; 255 snmpRptrMod MODULE-IDENTITY 256 LAST-UPDATED "9609140000Z" 257 ORGANIZATION "IETF HUB MIB Working Group" 258 CONTACT-INFO 259 "WG E-mail: hubmib@hprnd.rose.hp.com 261 Chair: Dan Romascanu 262 Postal: Madge Networks (Israel) Ltd. 263 Atidim Technology Park, Bldg. 3 264 Tel Aviv 61131, Israel 265 Tel: 972-3-6458414, 6458458 266 Fax: 972-3-6487146 267 E-mail: dromasca@madge.com 269 Editor: Kathryn de Graaf 270 Postal: 3Com Corporation 271 118 Turnpike Rd. 272 Southborough, MA 01772 USA 273 Tel: (508)229-1627 274 Fax: (508)490-5882 275 E-mail: kdegraaf@isd.3com.com" 276 DESCRIPTION 277 "Management information for 802.3 repeaters. 279 The following references are used throughout 280 this MIB module: 282 , 284 [IEEE 802.3 Std] 285 refers to IEEE 802.3/ISO 8802-3 Information 286 processing systems - Local area networks - 287 Part 3: Carrier sense multiple access with 288 collision detection (CSMA/CD) access method 289 and physical layer specifications (1993). 291 [IEEE 802.3 Mgt] 292 refers to IEEE 802.3u-1995, '10 Mb/s & 293 100 Mb/s Management, Section 30,' 294 Supplement to ANSI/IEEE 802.3. 296 The following terms are used throughout this 297 MIB module. For complete formal definitions, 298 the IEEE 802.3 standards should be consulted 299 wherever possible: 301 System - A managed entity compliant with this 302 MIB, and incorporating at least one managed 303 802.3 repeater. 305 Chassis - An enclosure for one managed repeater, 306 part of a managed repeater, or several managed 307 repeaters. It typically contains an integral 308 power supply and a variable number of available 309 module slots. 311 Repeater-unit - The portion of the repeater set 312 that is inboard of the physical media interfaces. 313 The physical media interfaces (MAUs, AUIs) may be 314 physically separated from the repeater-unit, or 315 they may be integrated into the same physical 316 package. 318 Trivial repeater-unit - An isolated port that can 319 gather statistics. 321 Group - A recommended, but optional, entity 322 defined by the IEEE 802.3 management standard, 323 in order to support a modular numbering scheme. 324 The classical example allows an implementor to 325 represent field-replaceable units as groups of 326 ports, with the port numbering matching the 327 modular hardware implementation. 329 , 330 System interconnect segment - An internal 331 segment allowing interconnection of ports 332 belonging to different physical entities 333 into the same logical manageable repeater. 334 Examples of implementation might be 335 backplane busses in modular hubs, or 336 chaining cables in stacks of hubs. 338 Stack - A scalable system that may include 339 managed repeaters, in which modularity is 340 achieved by interconnecting a number of 341 different chassis. 343 Module - A building block in a modular 344 chassis. It typically maps into one 'slot'; 345 however, the range of configurations may be 346 very large, with several modules entering 347 one slot, or one module covering several 348 slots. 349 " 350 REVISION "9309010000Z" 351 DESCRIPTION 352 "Published as RFC 1516" 353 REVISION "9210010000Z" 354 DESCRIPTION 355 "Published as RFC 1368" 356 ::= { snmpDot3RptrMgt 5 } 358 snmpDot3RptrMgt OBJECT IDENTIFIER ::= { mib-2 22 } 360 OptMacAddr ::= TEXTUAL-CONVENTION 361 DISPLAY-HINT "1x:" 362 STATUS current 363 DESCRIPTION 364 "Either a 6 octet address in the `canonical' 365 order defined by IEEE 802.1a, i.e., as if it 366 were transmitted least significant bit first 367 if a value is available or a zero length string." 368 REFERENCE 369 "See MacAddress in SNMPv2-TC. The only difference 370 is that a zero length string is allowed as a value 371 for OptMacAddr and not for MacAddress." 373 , 375 SYNTAX OCTET STRING (SIZE (0 | 6)) 377 -- Basic information at the repeater, group, and port level. 379 rptrBasicPackage 380 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 1 } 381 rptrRptrInfo 382 OBJECT IDENTIFIER ::= { rptrBasicPackage 1 } 383 rptrGroupInfo 384 OBJECT IDENTIFIER ::= { rptrBasicPackage 2 } 385 rptrPortInfo 386 OBJECT IDENTIFIER ::= { rptrBasicPackage 3 } 387 rptrAllRptrInfo 388 OBJECT IDENTIFIER ::= { rptrBasicPackage 4 } 390 -- Monitoring information at the repeater, group, and port level. 391 rptrMonitorPackage 392 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 2 } 393 rptrMonitorRptrInfo 394 OBJECT IDENTIFIER ::= { rptrMonitorPackage 1 } 395 rptrMonitorGroupInfo 396 OBJECT IDENTIFIER ::= { rptrMonitorPackage 2 } 397 rptrMonitorPortInfo 398 OBJECT IDENTIFIER ::= { rptrMonitorPackage 3 } 399 rptrMonitorAllRptrInfo 400 OBJECT IDENTIFIER ::= { rptrMonitorPackage 4 } 402 -- Address tracking information at the repeater, group, 403 -- and port level. 404 rptrAddrTrackPackage 405 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 3 } 406 rptrAddrTrackRptrInfo 407 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 1 } 408 rptrAddrTrackGroupInfo 409 -- this subtree is currently unused 410 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 2 } 411 rptrAddrTrackPortInfo 412 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 3 } 414 -- TopN information. 415 rptrTopNPackage 416 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 4 } 417 rptrTopNRptrInfo 419 , 420 -- this subtree is currently unused 421 OBJECT IDENTIFIER ::= { rptrTopNPackage 1 } 422 rptrTopNGroupInfo 423 -- this subtree is currently unused 424 OBJECT IDENTIFIER ::= { rptrTopNPackage 2 } 425 rptrTopNPortInfo 426 OBJECT IDENTIFIER ::= { rptrTopNPackage 3 } 428 -- Old version of basic information at the repeater level. 429 -- 430 -- In a system containing a single managed repeater, 431 -- configuration, status, and control objects for the overall 432 -- repeater. 433 -- 434 -- The objects contained under the rptrRptrInfo subtree are 435 -- intended for backwards compatibility with implementations of 436 -- RFC 1516 [11]. In newer implementations (both single- and 437 -- multiple-repeater implementations) the rptrInfoTable should 438 -- be implemented. It is the preferred source of this information, 439 -- as it contains the values for all repeaters managed by the 440 -- agent. In all cases, the objects in the rptrRptrInfo subtree 441 -- are duplicates of the corresponding objects in the first entry 442 -- of the rptrInfoTable. 444 rptrGroupCapacity OBJECT-TYPE 445 SYNTAX Integer32 (1..2147483647) 446 MAX-ACCESS read-only 447 STATUS deprecated 448 DESCRIPTION 449 "********* THIS OBJECT IS DEPRECATED ********** 451 The rptrGroupCapacity is the number of groups 452 that can be contained within the repeater. Within 453 each managed repeater, the groups are uniquely 454 numbered in the range from 1 to rptrGroupCapacity. 456 Some groups may not be present in the repeater, in 457 which case the actual number of groups present 458 will be less than rptrGroupCapacity. The number 459 of groups present will never be greater than 460 rptrGroupCapacity. 462 Note: In practice, this will generally be the 463 number of field-replaceable units (i.e., modules, 465 , 466 cards, or boards) that can fit in the physical 467 repeater enclosure, and the group numbers will 468 correspond to numbers marked on the physical 469 enclosure." 470 REFERENCE 471 "[IEEE 802.3 Mgt], 30.4.1.1.3, 472 aRepeaterGroupCapacity." 473 ::= { rptrRptrInfo 1 } 475 rptrOperStatus OBJECT-TYPE 476 SYNTAX INTEGER { 477 other(1), -- undefined or unknown 478 ok(2), -- no known failures 479 rptrFailure(3), -- repeater-related failure 480 groupFailure(4), -- group-related failure 481 portFailure(5), -- port-related failure 482 generalFailure(6) -- failure, unspecified type 483 } 484 MAX-ACCESS read-only 485 STATUS deprecated 486 DESCRIPTION 487 "********* THIS OBJECT IS DEPRECATED ********** 489 The rptrOperStatus object indicates the 490 operational state of the repeater. The 491 rptrHealthText object may be consulted for more 492 specific information about the state of the 493 repeater's health. 495 In the case of multiple kinds of failures (e.g., 496 repeater failure and port failure), the value of 497 this attribute shall reflect the highest priority 498 failure in the following order, listed highest 499 priority first: 501 rptrFailure(3) 502 groupFailure(4) 503 portFailure(5) 504 generalFailure(6)." 505 REFERENCE 506 "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState." 507 ::= { rptrRptrInfo 2 } 509 rptrHealthText OBJECT-TYPE 510 SYNTAX DisplayString (SIZE (0..255)) 512 , 513 MAX-ACCESS read-only 514 STATUS deprecated 515 DESCRIPTION 516 "********* THIS OBJECT IS DEPRECATED ********** 518 The health text object is a text string that 519 provides information relevant to the operational 520 state of the repeater. Agents may use this string 521 to provide detailed information on current 522 failures, including how they were detected, and/or 523 instructions for problem resolution. The contents 524 are agent-specific." 525 REFERENCE 526 "[IEEE 802.3 Mgt], 30.4.1.1.6, aRepeaterHealthText." 527 ::= { rptrRptrInfo 3 } 529 rptrReset OBJECT-TYPE 530 SYNTAX INTEGER { 531 noReset(1), 532 reset(2) 533 } 534 MAX-ACCESS read-write 535 STATUS deprecated 536 DESCRIPTION 537 "********* THIS OBJECT IS DEPRECATED ********** 539 Setting this object to reset(2) causes a 540 transition to the START state of Fig 9-2 in 541 section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, 542 and the START state of Fig 27-2 in section 27 543 of that standard for a 100Mb/s repeater. 545 Setting this object to noReset(1) has no effect. 546 The agent will always return the value noReset(1) 547 when this object is read. 549 After receiving a request to set this variable to 550 reset(2), the agent is allowed to delay the reset 551 for a short period. For example, the implementor 552 may choose to delay the reset long enough to allow 553 the SNMP response to be transmitted. In any 554 event, the SNMP response must be transmitted. 556 This action does not reset the management counters 557 defined in this document nor does it affect the 559 , 560 portAdminStatus parameters. Included in this 561 action is the execution of a disruptive Self-Test 562 with the following characteristics: a) The nature 563 of the tests is not specified. b) The test resets 564 the repeater but without affecting management 565 information about the repeater. c) The test does 566 not inject packets onto any segment. d) Packets 567 received during the test may or may not be 568 transferred. e) The test does not interfere with 569 management functions. 571 After performing this self-test, the agent will 572 update the repeater health information (including 573 rptrOperStatus and rptrHealthText), and send a 574 rptrHealth trap." 575 REFERENCE 576 "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." 577 ::= { rptrRptrInfo 4 } 579 rptrNonDisruptTest OBJECT-TYPE 580 SYNTAX INTEGER { 581 noSelfTest(1), 582 selfTest(2) 583 } 584 MAX-ACCESS read-write 585 STATUS deprecated 586 DESCRIPTION 587 "********* THIS OBJECT IS DEPRECATED ********** 589 Setting this object to selfTest(2) causes the 590 repeater to perform a agent-specific, non- 591 disruptive self-test that has the following 592 characteristics: a) The nature of the tests is 593 not specified. b) The test does not change the 594 state of the repeater or management information 595 about the repeater. c) The test does not inject 596 packets onto any segment. d) The test does not 597 prevent the relay of any packets. e) The test 598 does not interfere with management functions. 600 After performing this test, the agent will update 601 the repeater health information (including 602 rptrOperStatus and rptrHealthText) and send a 603 rptrHealth trap. 605 , 606 Note that this definition allows returning an 607 'okay' result after doing a trivial test. 609 Setting this object to noSelfTest(1) has no 610 effect. The agent will always return the value 611 noSelfTest(1) when this object is read." 612 REFERENCE 613 "[IEEE 802.3 Mgt], 30.4.1.2.2, 614 acExecuteNonDisruptiveSelfTest." 615 ::= { rptrRptrInfo 5 } 617 rptrTotalPartitionedPorts OBJECT-TYPE 618 SYNTAX Gauge32 619 MAX-ACCESS read-only 620 STATUS deprecated 621 DESCRIPTION 622 "********* THIS OBJECT IS DEPRECATED ********** 624 This object returns the total number of ports in 625 the repeater whose current state meets all three 626 of the following criteria: rptrPortOperStatus 627 does not have the value notPresent(3), 628 rptrPortAdminStatus is enabled(1), and 629 rptrPortAutoPartitionState is autoPartitioned(2)." 630 ::= { rptrRptrInfo 6 } 632 -- Basic information at the group level. 633 -- 634 -- Configuration and status objects for each 635 -- managed group in the system, independent 636 -- of whether there is one or more managed 637 -- repeater-units in the system. 639 rptrGroupTable OBJECT-TYPE 640 SYNTAX SEQUENCE OF RptrGroupEntry 641 MAX-ACCESS not-accessible 642 STATUS current 643 DESCRIPTION 644 "Table of descriptive and status information about 645 the groups of ports." 646 ::= { rptrGroupInfo 1 } 648 rptrGroupEntry OBJECT-TYPE 650 , 651 SYNTAX RptrGroupEntry 652 MAX-ACCESS not-accessible 653 STATUS current 654 DESCRIPTION 655 "An entry in the table, containing information 656 about a single group of ports." 657 INDEX { rptrGroupIndex } 658 ::= { rptrGroupTable 1 } 660 RptrGroupEntry ::= 661 SEQUENCE { 662 rptrGroupIndex 663 Integer32, 664 rptrGroupDescr 665 DisplayString, 666 rptrGroupObjectID 667 OBJECT IDENTIFIER, 668 rptrGroupOperStatus 669 INTEGER, 670 rptrGroupLastOperStatusChange 671 TimeTicks, 672 rptrGroupPortCapacity 673 Integer32 674 } 676 rptrGroupIndex OBJECT-TYPE 677 SYNTAX Integer32 (1..2147483647) 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "This object identifies the group within the 682 system for which this entry contains 683 information." 684 REFERENCE 685 "[IEEE 802.3 Mgt], 30.4.2.1.1, aGroupID." 686 ::= { rptrGroupEntry 1 } 688 rptrGroupDescr OBJECT-TYPE 689 SYNTAX DisplayString (SIZE (0..255)) 690 MAX-ACCESS read-only 691 STATUS deprecated 692 DESCRIPTION 693 "********* THIS OBJECT IS DEPRECATED ********** 695 A textual description of the group. This value 697 , 698 should include the full name and version 699 identification of the group's hardware type and 700 indicate how the group is differentiated from 701 other types of groups in the repeater. Plug-in 702 Module, Rev A' or 'Barney Rubble 10BASE-T 4-port 703 SIMM socket Version 2.1' are examples of valid 704 group descriptions. 706 It is mandatory that this only contain printable 707 ASCII characters." 708 ::= { rptrGroupEntry 2 } 710 rptrGroupObjectID OBJECT-TYPE 711 SYNTAX OBJECT IDENTIFIER 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The vendor's authoritative identification of the 716 group. This value may be allocated within the SMI 717 enterprises subtree (1.3.6.1.4.1) and provides a 718 straight-forward and unambiguous means for 719 determining what kind of group is being managed. 721 For example, this object could take the value 722 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, 723 Inc.' was assigned the subtree 1.3.6.1.4.1.4242, 724 and had assigned the identifier 725 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 726 6-Port FOIRL Plug-in Module.'" 727 ::= { rptrGroupEntry 3 } 729 rptrGroupOperStatus OBJECT-TYPE 730 SYNTAX INTEGER { 731 other(1), 732 operational(2), 733 malfunctioning(3), 734 notPresent(4), 735 underTest(5), 736 resetInProgress(6) 737 } 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "An object that indicates the operational status 742 of the group. 744 , 745 A status of notPresent(4) indicates that the group 746 is temporarily or permanently physically and/or 747 logically not a part of the repeater. It is an 748 implementation-specific matter as to whether the 749 agent effectively removes notPresent entries from 750 the table. 752 A status of operational(2) indicates that the 753 group is functioning, and a status of 754 malfunctioning(3) indicates that the group is 755 malfunctioning in some way." 756 ::= { rptrGroupEntry 4 } 758 rptrGroupLastOperStatusChange OBJECT-TYPE 759 SYNTAX TimeTicks 760 MAX-ACCESS read-only 761 STATUS deprecated 762 DESCRIPTION 763 "********* THIS OBJECT IS DEPRECATED ********** 765 An object that contains the value of sysUpTime at 766 the time when the last of the following occurred: 767 1) the agent cold- or warm-started; 768 2) the row for the group was created (such 769 as when the group was added to the system); or 770 3) the value of rptrGroupOperStatus for the 771 group changed. 773 A value of zero indicates that the group's 774 operational status has not changed since the agent 775 last restarted." 776 ::= { rptrGroupEntry 5 } 778 rptrGroupPortCapacity OBJECT-TYPE 779 SYNTAX Integer32 (1..2147483647) 780 MAX-ACCESS read-only 781 STATUS current 782 DESCRIPTION 783 "The rptrGroupPortCapacity is the number of ports 784 that can be contained within the group. Valid 785 range is 1-2147483647. Within each group, the 786 ports are uniquely numbered in the range from 1 to 787 rptrGroupPortCapacity. 789 Some ports may not be present in the system, in 791 , 792 which case the actual number of ports present 793 will be less than the value of rptrGroupPortCapacity. 794 The number of ports present in the group will never 795 be greater than the value of rptrGroupPortCapacity. 797 Note: In practice, this will generally be the 798 number of ports on a module, card, or board, and 799 the port numbers will correspond to numbers marked 800 on the physical embodiment." 801 REFERENCE 802 "IEEE 802.3 Mgt, 30.4.2.1.2, aGroupPortCapacity." 803 ::= { rptrGroupEntry 6 } 805 -- Basic information at the port level. 806 -- 807 -- Configuration and status objects for 808 -- each managed repeater port in the system, 809 -- independent of whether there is one or more 810 -- managed repeater-units in the system. 812 rptrPortTable OBJECT-TYPE 813 SYNTAX SEQUENCE OF RptrPortEntry 814 MAX-ACCESS not-accessible 815 STATUS current 816 DESCRIPTION 817 "Table of descriptive and status information about 818 the repeater ports in the system. The number of 819 entries is independent of the number of repeaters 820 in the managed system." 821 ::= { rptrPortInfo 1 } 823 rptrPortEntry OBJECT-TYPE 824 SYNTAX RptrPortEntry 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "An entry in the table, containing information 829 about a single port." 830 INDEX { rptrPortGroupIndex, rptrPortIndex } 831 ::= { rptrPortTable 1 } 833 RptrPortEntry ::= 834 SEQUENCE { 835 rptrPortGroupIndex 837 , 838 Integer32, 839 rptrPortIndex 840 Integer32, 841 rptrPortAdminStatus 842 INTEGER, 843 rptrPortAutoPartitionState 844 INTEGER, 845 rptrPortOperStatus 846 INTEGER, 847 rptrPortRptrId 848 Integer32 849 } 851 rptrPortGroupIndex OBJECT-TYPE 852 SYNTAX Integer32 (1..2147483647) 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "This object identifies the group containing the 857 port for which this entry contains information." 858 ::= { rptrPortEntry 1 } 860 rptrPortIndex OBJECT-TYPE 861 SYNTAX Integer32 (1..2147483647) 862 MAX-ACCESS read-only 863 STATUS current 864 DESCRIPTION 865 "This object identifies the port within the group 866 for which this entry contains information. This 867 identifies the port independently from the repeater 868 it may be attached to. The numbering scheme for 869 ports is implementation specific; however, this 870 value can never be greater than 871 rptrGroupPortCapacity for the associated group." 872 REFERENCE 873 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." 874 ::= { rptrPortEntry 2 } 876 rptrPortAdminStatus OBJECT-TYPE 877 SYNTAX INTEGER { 878 enabled(1), 879 disabled(2) 880 } 881 MAX-ACCESS read-write 882 STATUS current 884 , 885 DESCRIPTION 886 "Setting this object to disabled(2) disables the 887 port. A disabled port neither transmits nor 888 receives. Once disabled, a port must be 889 explicitly enabled to restore operation. A port 890 which is disabled when power is lost or when a 891 reset is exerted shall remain disabled when normal 892 operation resumes. 894 The admin status takes precedence over auto- 895 partition and functionally operates between the 896 auto-partition mechanism and the AUI/PMA. 898 Setting this object to enabled(1) enables the port 899 and exerts a BEGIN on the port's auto-partition 900 state machine. 902 (In effect, when a port is disabled, the value of 903 rptrPortAutoPartitionState for that port is frozen 904 until the port is next enabled. When the port 905 becomes enabled, the rptrPortAutoPartitionState 906 becomes notAutoPartitioned(1), regardless of its 907 pre-disabling state.)" 908 REFERENCE 909 "[IEEE 802.3 Mgt], 30.4.3.1.2, aPortAdminState 910 and 30.4.3.2.1, acPortAdminControl." 911 ::= { rptrPortEntry 3 } 913 rptrPortAutoPartitionState OBJECT-TYPE 914 SYNTAX INTEGER { 915 notAutoPartitioned(1), 916 autoPartitioned(2) 917 } 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "The autoPartitionState flag indicates whether the 922 port is currently partitioned by the repeater's 923 auto-partition protection. 925 The conditions that cause port partitioning are 926 specified in partition state machine in Sections 927 9 and 27 of [IEEE 802.3 Std]. They are not 928 differentiated here." 929 REFERENCE 931 , 932 "[IEEE 802.3 Mgt], 30.4.3.1.3, aAutoPartitionState." 933 ::= { rptrPortEntry 4 } 935 rptrPortOperStatus OBJECT-TYPE 936 SYNTAX INTEGER { 937 operational(1), 938 notOperational(2), 939 notPresent(3) 940 } 941 MAX-ACCESS read-only 942 STATUS current 943 DESCRIPTION 944 "This object indicates the port's operational 945 status. The notPresent(3) status indicates the 946 port is physically removed (note this may or may 947 not be possible depending on the type of port.) 948 The operational(1) status indicates that the port 949 is enabled (see rptrPortAdminStatus) and working, 950 even though it might be auto-partitioned (see 951 rptrPortAutoPartitionState). 953 If this object has the value operational(1) and 954 rptrPortAdminStatus is set to disabled(2), it is 955 expected that this object's value will soon change 956 to notOperational(2)." 957 ::= { rptrPortEntry 5 } 959 rptrPortRptrId OBJECT-TYPE 960 SYNTAX Integer32 (0..2147483647) 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "This object identifies the repeater to 965 which this port belongs. The repeater 966 identified by a particular value of this object 967 is the same as that identified by the same 968 value of rptrInfoId. A value of zero 969 indicates that this port currently is not 970 a member of any repeater." 971 ::= { rptrPortEntry 6 } 973 -- New version of basic information at the repeater level. 974 -- 975 -- Configuration, status, and control objects for 977 , 978 -- each managed repeater in the system. 980 rptrInfoTable OBJECT-TYPE 981 SYNTAX SEQUENCE OF RptrInfoEntry 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "A table of information about each 986 non-trivial repeater. The number of entries 987 depends on the physical configuration of the 988 managed system." 989 ::= { rptrAllRptrInfo 1 } 991 rptrInfoEntry OBJECT-TYPE 992 SYNTAX RptrInfoEntry 993 MAX-ACCESS not-accessible 994 STATUS current 995 DESCRIPTION 996 "An entry in the table, containing information 997 about a single non-trivial repeater." 998 INDEX { rptrInfoId } 999 ::= { rptrInfoTable 1 } 1001 RptrInfoEntry ::= 1002 SEQUENCE { 1003 rptrInfoId 1004 Integer32, 1005 rptrInfoRptrType 1006 INTEGER, 1007 rptrInfoOperStatus 1008 INTEGER, 1009 rptrInfoReset 1010 INTEGER, 1011 rptrInfoPartitionedPorts 1012 Gauge32, 1013 rptrInfoLastChange 1014 TimeStamp 1015 } 1017 rptrInfoId OBJECT-TYPE 1018 SYNTAX Integer32 (1..2147483647) 1019 MAX-ACCESS read-only 1020 STATUS current 1021 DESCRIPTION 1022 "This object identifies the repeater for which 1024 , 1025 this entry contains information." 1026 ::= { rptrInfoEntry 1 } 1028 rptrInfoRptrType OBJECT-TYPE 1029 SYNTAX INTEGER { 1030 other(1), -- undefined or unknown 1031 tenMb(2), 1032 onehundredMbClassI(3), 1033 onehundredMbClassII(4) 1034 } 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "The rptrInfoRptrType returns a value that identifies 1039 the CSMA/CD repeater type." 1040 REFERENCE 1041 "[IEEE 802.3 Mgt], 30.4.1.1.2, aRepeaterType." 1042 ::= { rptrInfoEntry 2 } 1044 rptrInfoOperStatus OBJECT-TYPE 1045 SYNTAX INTEGER { 1046 other(1), 1047 ok(2), 1048 failure(3) 1049 } 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION 1053 "The rptrInfoOperStatus object indicates the 1054 operational state of the repeater." 1055 REFERENCE 1056 "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState." 1057 ::= { rptrInfoEntry 3 } 1059 rptrInfoReset OBJECT-TYPE 1060 SYNTAX INTEGER { 1061 noReset(1), 1062 reset(2) 1063 } 1064 MAX-ACCESS read-write 1065 STATUS current 1066 DESCRIPTION 1067 "Setting this object to reset(2) causes a 1068 transition to the START state of Fig 9-2 in 1069 section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, 1071 , 1072 and to the START state of Fig 27-2 in section 27 1073 of that standard for a 100Mb/s repeater. 1075 Setting this object to noReset(1) has no effect. 1076 The agent will always return the value noReset(1) 1077 when this object is read. 1079 After receiving a request to set this variable to 1080 reset(2), the agent is allowed to delay the reset 1081 for a short period. For example, the implementor 1082 may choose to delay the reset long enough to allow 1083 the SNMP response to be transmitted. In any 1084 event, the SNMP response must be transmitted. 1086 This action does not reset the management counters 1087 defined in this document nor does it affect the 1088 portAdminStatus parameters. Included in this 1089 action is the execution of a disruptive Self-Test 1090 with the following characteristics: a) The nature 1091 of the tests is not specified. b) The test resets 1092 the repeater but without affecting management 1093 information about the repeater. c) The test does 1094 not inject packets onto any segment. d) Packets 1095 received during the test may or may not be 1096 transferred. e) The test does not interfere with 1097 management functions. 1099 After performing this self-test, the agent will 1100 update the repeater health information (including 1101 rptrInfoOperStatus), and send a rptrInfoResetEvent 1102 notification." 1103 REFERENCE 1104 "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." 1105 ::= { rptrInfoEntry 4 } 1107 rptrInfoPartitionedPorts OBJECT-TYPE 1108 SYNTAX Gauge32 1109 MAX-ACCESS read-only 1110 STATUS current 1111 DESCRIPTION 1112 "This object returns the total number of ports in 1113 the repeater whose current state meets all three 1114 of the following criteria: rptrPortOperStatus 1115 does not have the value notPresent(3), 1116 rptrPortAdminStatus is enabled(1), and 1118 , 1119 rptrPortAutoPartitionState is autoPartitioned(2)." 1120 ::= { rptrInfoEntry 5 } 1122 rptrInfoLastChange OBJECT-TYPE 1123 SYNTAX TimeStamp 1124 MAX-ACCESS read-only 1125 STATUS current 1126 DESCRIPTION 1127 "The value of sysUpTime when any of the following 1128 conditions occurred: 1129 1) agent cold- or warm-started; 1130 2) this instance of repeater was created 1131 (such as when a device or module was 1132 added to the system); 1133 3) a change in the value of rptrInfoOperStatus; 1134 4) ports were added or removed as members of 1135 the repeater; or 1136 5) any of the counters associated with this 1137 repeater had a discontinuity." 1138 ::= { rptrInfoEntry 6 } 1140 -- 1141 -- Old version of statistics at the repeater level. 1142 -- 1143 -- Performance monitoring statistics for the repeater 1144 -- 1145 -- In a system containing a single managed repeater-unit, 1146 -- the statistics object for the repeater-unit. 1148 -- The objects contained under the rptrMonitorRptrInfo subtree are 1149 -- intended for backwards compatibility with implementations of 1150 -- RFC 1516 [11]. In newer implementations (both single- and 1151 -- multiple-repeater implementations), the rptrMonitorTable will 1152 -- be implemented. It is the preferred source of this information, 1153 -- as it contains the values for all repeaters managed by the 1154 -- agent. In all cases, the objects in the rptrMonitorRptrInfo 1155 -- subtree are duplicates of the corresponding objects in the 1156 -- first entry of the rptrMonitorTable. 1158 rptrMonitorTransmitCollisions OBJECT-TYPE 1159 SYNTAX Counter32 1161 , 1162 MAX-ACCESS read-only 1163 STATUS deprecated 1164 DESCRIPTION 1165 "********* THIS OBJECT IS DEPRECATED ********** 1167 For a clause 9 (10Mb/s) repeater, this counter 1168 is incremented every time the repeater state 1169 machine enters the TRANSMIT COLLISION state 1170 from any state other than ONE PORT LEFT 1171 (Ref: Fig 9-2 [IEEE 802.3 Std]). 1173 For a clause 27 repeater, this counter is 1174 incremented every time the repeater core state 1175 diagram enters the Jam state as a result of 1176 Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). 1178 The approximate minimum time for rollover of this 1179 counter is 16 hours in a 10Mb/s repeater and 1.6 1180 hours in a 100Mb/s repeater." 1181 REFERENCE 1182 "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions." 1183 ::= { rptrMonitorRptrInfo 1 } 1185 -- Statistics at the group level. 1186 -- 1187 -- In a system containing a single managed repeater-unit, 1188 -- the statistics objects for each group. 1190 rptrMonitorGroupTable OBJECT-TYPE 1191 SYNTAX SEQUENCE OF RptrMonitorGroupEntry 1192 MAX-ACCESS not-accessible 1193 STATUS deprecated 1194 DESCRIPTION 1195 "********* THIS OBJECT IS DEPRECATED ********** 1197 Table of performance and error statistics for the 1198 groups within the repeater. The number of entries 1199 is the same as that in the rptrGroupTable." 1200 ::= { rptrMonitorGroupInfo 1 } 1202 rptrMonitorGroupEntry OBJECT-TYPE 1203 SYNTAX RptrMonitorGroupEntry 1204 MAX-ACCESS not-accessible 1205 STATUS deprecated 1207 , 1208 DESCRIPTION 1209 "********* THIS OBJECT IS DEPRECATED ********** 1211 An entry in the table, containing total 1212 performance and error statistics for a single 1213 group. Regular retrieval of the information in 1214 this table provides a means of tracking the 1215 performance and health of the networked devices 1216 attached to this group's ports. 1218 The counters in this table are redundant in the 1219 sense that they are the summations of information 1220 already available through other objects. However, 1221 these sums provide a considerable optimization of 1222 network management traffic over the otherwise 1223 necessary retrieval of the individual counters 1224 included in each sum. 1226 Note: Group-level counters are 1227 deprecated in this MIB. It is recommended 1228 that management applications instead use 1229 the repeater-level counters contained in 1230 the rptrMonTable." 1231 INDEX { rptrMonitorGroupIndex } 1232 ::= { rptrMonitorGroupTable 1 } 1234 RptrMonitorGroupEntry ::= 1235 SEQUENCE { 1236 rptrMonitorGroupIndex 1237 Integer32, 1238 rptrMonitorGroupTotalFrames 1239 Counter32, 1240 rptrMonitorGroupTotalOctets 1241 Counter32, 1242 rptrMonitorGroupTotalErrors 1243 Counter32 1244 } 1246 rptrMonitorGroupIndex OBJECT-TYPE 1247 SYNTAX Integer32 (1..2147483647) 1248 MAX-ACCESS read-only 1249 STATUS deprecated 1250 DESCRIPTION 1251 "********* THIS OBJECT IS DEPRECATED ********** 1253 , 1254 This object identifies the group within the 1255 repeater for which this entry contains 1256 information." 1257 ::= { rptrMonitorGroupEntry 1 } 1259 rptrMonitorGroupTotalFrames OBJECT-TYPE 1260 SYNTAX Counter32 1261 MAX-ACCESS read-only 1262 STATUS deprecated 1263 DESCRIPTION 1264 "********* THIS OBJECT IS DEPRECATED ********** 1266 The total number of frames of valid frame length 1267 that have been received on the ports in this group 1268 and for which the FCSError and CollisionEvent 1269 signals were not asserted. This counter is the 1270 summation of the values of the 1271 rptrMonitorPortReadableFrames counters for all of 1272 the ports in the group. 1274 This statistic provides one of the parameters 1275 necessary for obtaining the packet error rate. 1276 The approximate minimum time for rollover of this 1277 counter is 80 hours in a 10Mb/s repeater." 1278 ::= { rptrMonitorGroupEntry 2 } 1280 rptrMonitorGroupTotalOctets OBJECT-TYPE 1281 SYNTAX Counter32 1282 MAX-ACCESS read-only 1283 STATUS deprecated 1284 DESCRIPTION 1285 "********* THIS OBJECT IS DEPRECATED ********** 1287 The total number of octets contained in the valid 1288 frames that have been received on the ports in 1289 this group. This counter is the summation of the 1290 values of the rptrMonitorPortReadableOctets 1291 counters for all of the ports in the group. 1293 This statistic provides an indicator of the total 1294 data transferred. The approximate minimum time 1295 for rollover of this counter is 58 minutes in a 1296 10Mb/s repeater." 1297 ::= { rptrMonitorGroupEntry 3 } 1299 , 1301 rptrMonitorGroupTotalErrors OBJECT-TYPE 1302 SYNTAX Counter32 1303 MAX-ACCESS read-only 1304 STATUS deprecated 1305 DESCRIPTION 1306 "********* THIS OBJECT IS DEPRECATED ********** 1308 The total number of errors which have occurred on 1309 all of the ports in this group. This counter is 1310 the summation of the values of the 1311 rptrMonitorPortTotalErrors counters for all of the 1312 ports in the group." 1313 ::= { rptrMonitorGroupEntry 4 } 1315 -- Statistics at the port level. 1316 -- 1318 rptrMonitorPortTable OBJECT-TYPE 1319 SYNTAX SEQUENCE OF RptrMonitorPortEntry 1320 MAX-ACCESS not-accessible 1321 STATUS current 1322 DESCRIPTION 1323 "Table of performance and error statistics for the 1324 ports. The number of entries is the same as that 1325 in the rptrPortTable. 1327 The columnar object rptrMonitorPortLastChange 1328 is used to indicate possible discontinuities 1329 of counter type columnar objects in the table." 1330 ::= { rptrMonitorPortInfo 1 } 1332 rptrMonitorPortEntry OBJECT-TYPE 1333 SYNTAX RptrMonitorPortEntry 1334 MAX-ACCESS not-accessible 1335 STATUS current 1336 DESCRIPTION 1337 "An entry in the table, containing performance and 1338 error statistics for a single port." 1339 INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex } 1340 ::= { rptrMonitorPortTable 1 } 1342 RptrMonitorPortEntry ::= 1343 SEQUENCE { 1344 rptrMonitorPortGroupIndex 1346 , 1347 Integer32, 1348 rptrMonitorPortIndex 1349 Integer32, 1350 rptrMonitorPortReadableFrames 1351 Counter32, 1352 rptrMonitorPortReadableOctets 1353 Counter32, 1354 rptrMonitorPortFCSErrors 1355 Counter32, 1356 rptrMonitorPortAlignmentErrors 1357 Counter32, 1358 rptrMonitorPortFrameTooLongs 1359 Counter32, 1360 rptrMonitorPortShortEvents 1361 Counter32, 1362 rptrMonitorPortRunts 1363 Counter32, 1364 rptrMonitorPortCollisions 1365 Counter32, 1366 rptrMonitorPortLateEvents 1367 Counter32, 1368 rptrMonitorPortVeryLongEvents 1369 Counter32, 1370 rptrMonitorPortDataRateMismatches 1371 Counter32, 1372 rptrMonitorPortAutoPartitions 1373 Counter32, 1374 rptrMonitorPortTotalErrors 1375 Counter32, 1376 rptrMonitorPortLastChange 1377 TimeStamp 1378 } 1380 rptrMonitorPortGroupIndex OBJECT-TYPE 1381 SYNTAX Integer32 (1..2147483647) 1382 MAX-ACCESS read-only 1383 STATUS current 1384 DESCRIPTION 1385 "This object identifies the group containing the 1386 port for which this entry contains information." 1387 ::= { rptrMonitorPortEntry 1 } 1389 rptrMonitorPortIndex OBJECT-TYPE 1390 SYNTAX Integer32 (1..2147483647) 1391 MAX-ACCESS read-only 1393 , 1394 STATUS current 1395 DESCRIPTION 1396 "This object identifies the port within the group 1397 for which this entry contains information." 1398 REFERENCE 1399 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." 1400 ::= { rptrMonitorPortEntry 2 } 1402 rptrMonitorPortReadableFrames OBJECT-TYPE 1403 SYNTAX Counter32 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "This object is the number of frames of valid 1408 frame length that have been received on this port. 1409 This counter is incremented by one for each frame 1410 received on this port whose OctetCount is greater 1411 than or equal to minFrameSize and less than or 1412 equal to maxFrameSize (Ref: IEEE 802.3 Std, 1413 4.4.2.1) and for which the FCSError and 1414 CollisionEvent signals are not asserted. 1416 A discontinuity may occur in the value 1417 when the value of object 1418 rptrMonitorPortLastChange changes. 1420 This statistic provides one of the parameters 1421 necessary for obtaining the packet error rate. 1422 The approximate minimum time for rollover of this 1423 counter is 80 hours at 10Mb/s." 1424 REFERENCE 1425 "[IEEE 802.3 Mgt], 30.4.3.1.4, aReadableFrames." 1426 ::= { rptrMonitorPortEntry 3 } 1428 rptrMonitorPortReadableOctets OBJECT-TYPE 1429 SYNTAX Counter32 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "This object is the number of octets contained in 1434 valid frames that have been received on this port. 1435 This counter is incremented by OctetCount for each 1436 frame received on this port which has been 1437 determined to be a readable frame (i.e., including 1438 FCS octets but excluding framing bits and dribble 1440 , 1441 bits). 1443 A discontinuity may occur in the value 1444 when the value of object 1445 rptrMonitorPortLastChange changes. 1447 This statistic provides an indicator of the total 1448 data transferred. The approximate minimum time 1449 for rollover of this counter in a 10Mb/s repeater 1450 is 58 minutes. 1452 For ports receiving traffic at a maximum rate in 1453 a 100Mb/s repeater, this counter can roll over 1454 in less than 6 minutes. Since that amount of time 1455 could be less than a management station's poll cycle 1456 time, in order to avoid a loss of information a 1457 management station is advised to also poll the 1458 rptrMonitorPortUpper32Octets object, or to use the 1459 64-bit counter defined by 1460 rptrMonitorPortHCReadableOctets instead of the 1461 two 32-bit counters." 1462 REFERENCE 1463 "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets." 1464 ::= { rptrMonitorPortEntry 4 } 1466 rptrMonitorPortFCSErrors OBJECT-TYPE 1467 SYNTAX Counter32 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "This counter is incremented by one for each frame 1472 received on this port with the FCSError signal 1473 asserted and the FramingError and CollisionEvent 1474 signals deasserted and whose OctetCount is greater 1475 than or equal to minFrameSize and less than or 1476 equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 1477 Std). 1479 A discontinuity may occur in the value 1480 when the value of object 1481 rptrMonitorPortLastChange changes. 1483 The approximate minimum time for rollover of this 1484 counter is 80 hours at 10Mb/s." 1485 REFERENCE 1487 , 1488 "[IEEE 802.3 Mgt], 30.4.3.1.6, 1489 aFrameCheckSequenceErrors." 1490 ::= { rptrMonitorPortEntry 5 } 1492 rptrMonitorPortAlignmentErrors OBJECT-TYPE 1493 SYNTAX Counter32 1494 MAX-ACCESS read-only 1495 STATUS current 1496 DESCRIPTION 1497 "This counter is incremented by one for each frame 1498 received on this port with the FCSError and 1499 FramingError signals asserted and CollisionEvent 1500 signal deasserted and whose OctetCount is greater 1501 than or equal to minFrameSize and less than or 1502 equal to maxFrameSize (Ref: IEEE 802.3 Std, 1503 4.4.2.1). If rptrMonitorPortAlignmentErrors is 1504 incremented then the rptrMonitorPortFCSErrors 1505 Counter shall not be incremented for the same 1506 frame. 1508 A discontinuity may occur in the value 1509 when the value of object 1510 rptrMonitorPortLastChange changes. 1512 The approximate minimum time for rollover of this 1513 counter is 80 hours at 10Mb/s." 1514 REFERENCE 1515 "[IEEE 802.3 Mgt], 30.4.3.1.7, aAlignmentErrors." 1516 ::= { rptrMonitorPortEntry 6 } 1518 rptrMonitorPortFrameTooLongs OBJECT-TYPE 1519 SYNTAX Counter32 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "This counter is incremented by one for each frame 1524 received on this port whose OctetCount is greater 1525 than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). 1526 If rptrMonitorPortFrameTooLongs is incremented 1527 then neither the rptrMonitorPortAlignmentErrors 1528 nor the rptrMonitorPortFCSErrors counter shall be 1529 incremented for the frame. 1531 A discontinuity may occur in the value 1532 when the value of object 1534 , 1535 rptrMonitorPortLastChange changes. 1537 The approximate minimum time for rollover of this 1538 counter is 61 days in a 10Mb/s repeater." 1539 REFERENCE 1540 "[IEEE 802.3 Mgt], 30.4.3.1.8, aFramesTooLong." 1541 ::= { rptrMonitorPortEntry 7 } 1543 rptrMonitorPortShortEvents OBJECT-TYPE 1544 SYNTAX Counter32 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "This counter is incremented by one for each 1549 CarrierEvent on this port with ActivityDuration 1550 less than ShortEventMaxTime. ShortEventMaxTime is 1551 greater than 74 bit times and less than 82 bit 1552 times. ShortEventMaxTime has tolerances included 1553 to provide for circuit losses between a 1554 conformance test point at the AUI and the 1555 measurement point within the state machine. 1557 Notes: 1559 ShortEvents may indicate externally 1560 generated noise hits which will cause the repeater 1561 to transmit Runts to its other ports, or propagate 1562 a collision (which may be late) back to the 1563 transmitting DTE and damaged frames to the rest of 1564 the network. 1566 Implementors may wish to consider selecting the 1567 ShortEventMaxTime towards the lower end of the 1568 allowed tolerance range to accommodate bit losses 1569 suffered through physical channel devices not 1570 budgeted for within this standard. 1572 The significance of this attribute is different 1573 in 10 and 100 Mb/s collision domains. Clause 9 1574 repeaters perform fragment extension of short 1575 events which would be counted as runts on the 1576 interconnect ports of other repeaters. Clause 1577 27 repeaters do not perform fragment extension. 1579 A discontinuity may occur in the value 1581 , 1582 when the value of object 1583 rptrMonitorPortLastChange changes. 1585 The approximate minimum time for rollover of this 1586 counter is 16 hours in a 10Mb/s repeater." 1587 REFERENCE 1588 "[IEEE 802.3 Mgt], 30.4.3.1.9, aShortEvents." 1589 ::= { rptrMonitorPortEntry 8 } 1591 rptrMonitorPortRunts OBJECT-TYPE 1592 SYNTAX Counter32 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "This counter is incremented by one for each 1597 CarrierEvent on this port that meets one of the 1598 following two conditions. Only one test need be 1599 made. a) The ActivityDuration is greater than 1600 ShortEventMaxTime and less than ValidPacketMinTime 1601 and the CollisionEvent signal is deasserted. b) 1602 The OctetCount is less than 64, the 1603 ActivityDuration is greater than ShortEventMaxTime 1604 and the CollisionEvent signal is deasserted. 1605 ValidPacketMinTime is greater than or equal to 552 1606 bit times and less than 565 bit times. 1608 An event whose length is greater than 74 bit times 1609 but less than 82 bit times shall increment either 1610 the shortEvents counter or the runts counter but 1611 not both. A CarrierEvent greater than or equal to 1612 552 bit times but less than 565 bit times may or 1613 may not be counted as a runt. 1615 ValidPacketMinTime has tolerances included to 1616 provide for circuit losses between a conformance 1617 test point at the AUI and the measurement point 1618 within the state machine. 1620 Runts usually indicate collision fragments, a 1621 normal network event. In certain situations 1622 associated with large diameter networks a 1623 percentage of collision fragments may exceed 1624 ValidPacketMinTime. 1626 A discontinuity may occur in the value 1628 , 1629 when the value of object 1630 rptrMonitorPortLastChange changes. 1632 The approximate minimum time for rollover of this 1633 counter is 16 hours in a 10Mb/s repeater." 1634 REFERENCE 1635 "[IEEE 802.3 Mgt], 30.4.3.1.10, aRunts." 1636 ::= { rptrMonitorPortEntry 9 } 1638 rptrMonitorPortCollisions OBJECT-TYPE 1639 SYNTAX Counter32 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "For a clause 9 repeater, this counter is 1644 incremented by one for any CarrierEvent signal 1645 on any port for which the CollisionEvent signal 1646 on this port is asserted. For a clause 27 1647 repeater port the counter increments on entering 1648 the Collision Count Increment state of the 1649 partition state diagram (fig 27-8 of 1650 [IEEE 802.3 Std]). 1652 A discontinuity may occur in the value 1653 when the value of object 1654 rptrMonitorPortLastChange changes. 1656 The approximate minimum time for rollover of this 1657 counter is 16 hours in a 10Mb/s repeater." 1658 REFERENCE 1659 "[IEEE 802.3 Mgt], 30.4.3.1.11, aCollisions." 1660 ::= { rptrMonitorPortEntry 10 } 1662 rptrMonitorPortLateEvents OBJECT-TYPE 1663 SYNTAX Counter32 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "For a clause 9 repeater port, this counter is 1668 incremented by one for each CarrierEvent 1669 on this port in which the CollIn(X) 1670 variable transitions to the value SQE (Ref: 1671 9.6.6.2, IEEE 802.3 Std) while the 1672 ActivityDuration is greater than the 1673 LateEventThreshold. For a clause 27 repeater 1675 , 1676 port, this counter is incremented by one on 1677 entering the Collision Count Increment state 1678 of the partition state diagram (fig 27-8) 1679 while the ActivityDuration is greater than 1680 the LateEvent- Threshold. Such a CarrierEvent 1681 is counted twice, as both a collision and as a 1682 lateEvent. 1684 The LateEventThreshold is greater than 480 bit 1685 times and less than 565 bit times. 1686 LateEventThreshold has tolerances included to 1687 permit an implementation to build a single 1688 threshold to serve as both the LateEventThreshold 1689 and ValidPacketMinTime threshold. 1691 A discontinuity may occur in the value 1692 when the value of object 1693 rptrMonitorPortLastChange changes. 1695 The approximate minimum time for rollover of this 1696 counter is 81 hours in a 10Mb/s repeater." 1697 REFERENCE 1698 "[IEEE 802.3 Mgt], 30.4.3.1.12, aLateEvents." 1699 ::= { rptrMonitorPortEntry 11 } 1701 rptrMonitorPortVeryLongEvents OBJECT-TYPE 1702 SYNTAX Counter32 1703 MAX-ACCESS read-only 1704 STATUS current 1705 DESCRIPTION 1706 "For a clause 9 repeater port, this counter 1707 is incremented by one for each CarrierEvent 1708 whose ActivityDuration is greater than the 1709 MAU Jabber Lockup Protection timer TW3 1710 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). 1712 For a clause 27 repeater port, this counter 1713 is incremented by one on entry to the 1714 Rx Jabber state of the receiver timer state 1715 diagram (fig 27-7). Other counters may 1716 be incremented as appropriate. 1718 A discontinuity may occur in the value 1719 when the value of object 1720 rptrMonitorPortLastChange changes." 1722 , 1724 REFERENCE 1725 "[IEEE 802.3 Mgt], 30.4.3.1.13, aVeryLongEvents." 1726 ::= { rptrMonitorPortEntry 12 } 1728 rptrMonitorPortDataRateMismatches OBJECT-TYPE 1729 SYNTAX Counter32 1730 MAX-ACCESS read-only 1731 STATUS current 1732 DESCRIPTION 1733 "This counter is incremented by one for each 1734 frame received by this port that meets all 1735 of the conditions required by only one of the 1736 following two measurement methods: 1738 Measurement method A: 1) The CollisionEvent 1739 signal is not asserted (10Mb/s operation) or 1740 the Collision Count Increment state of the 1741 partition state diagram (fig 27-8 of 1742 [IEEE 802.3 Std]) has not been entered 1743 (100Mb/s operation). 2) The ActivityDuration 1744 is greater than ValidPacketMinTime. 3) The 1745 frequency (data rate) is detectably mismatched 1746 from the local transmit frequency. 1748 Measurement method B: 1) The CollisionEvent 1749 signal is not asserted (10Mb/s operation) 1750 or the Collision Count Increment state of the 1751 partition state diagram (fig 27-8 of 1752 [IEEE 802.3 Std]) has not been entered 1753 (100Mb/s operation). 2) The OctetCount is 1754 greater than 63. 3) The frequency (data 1755 rate) is detectably mismatched from the local 1756 transmit frequency. The exact degree of 1757 mismatch is vendor specific and is to be 1758 defined by the vendor for conformance testing. 1760 When this event occurs, other counters whose 1761 increment conditions were satisfied may or may not 1762 also be incremented, at the implementor's 1763 discretion. Whether or not the repeater was able 1764 to maintain data integrity is beyond the scope of 1765 this standard. 1767 A discontinuity may occur in the value 1768 when the value of object 1770 , 1771 rptrMonitorPortLastChange changes." 1772 REFERENCE 1773 "[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches." 1774 ::= { rptrMonitorPortEntry 13 } 1776 rptrMonitorPortAutoPartitions OBJECT-TYPE 1777 SYNTAX Counter32 1778 MAX-ACCESS read-only 1779 STATUS current 1780 DESCRIPTION 1781 "This counter is incremented by one for 1782 each time the repeater has automatically 1783 partitioned this port. 1785 The conditions that cause a clause 9 1786 repeater port to partition are specified in 1787 the partition state diagram in clause 9 of 1788 [IEEE 802.3 Std]. They are not differentiated 1789 here. A clause 27 repeater port partitions 1790 on entry to the Partition Wait state of the 1791 partition state diagram (fig 27-8 in 1792 [IEEE 802.3 Std]). 1794 A discontinuity may occur in the value 1795 when the value of object 1796 rptrMonitorPortLastChange changes." 1797 REFERENCE 1798 "[IEEE 802.3 Mgt], 30.4.3.1.15, aAutoPartitions." 1799 ::= { rptrMonitorPortEntry 14 } 1801 rptrMonitorPortTotalErrors OBJECT-TYPE 1802 SYNTAX Counter32 1803 MAX-ACCESS read-only 1804 STATUS current 1805 DESCRIPTION 1806 "The total number of errors which have occurred on 1807 this port. This counter is the summation of the 1808 values of other error counters (for the same 1809 port), namely: 1811 rptrMonitorPortFCSErrors, 1812 rptrMonitorPortAlignmentErrors, 1813 rptrMonitorPortFrameTooLongs, 1814 rptrMonitorPortShortEvents, 1815 rptrMonitorPortLateEvents, 1817 , 1818 rptrMonitorPortVeryLongEvents, 1819 rptrMonitorPortDataRateMismatches, and 1820 rptrMonitorPortSymbolErrors. 1822 This counter is redundant in the sense that it is 1823 the summation of information already available 1824 through other objects. However, it is included 1825 specifically because the regular retrieval of this 1826 object as a means of tracking the health of a port 1827 provides a considerable optimization of network 1828 management traffic over the otherwise necessary 1829 retrieval of the summed counters. 1831 Note that rptrMonitorPortRunts is not included 1832 in this total; this is because runts usually 1833 indicate collision fragments, a normal network 1834 event. 1836 A discontinuity may occur in the value 1837 when the value of object 1838 rptrMonitorPortLastChange changes." 1839 ::= { rptrMonitorPortEntry 15 } 1841 rptrMonitorPortLastChange OBJECT-TYPE 1842 SYNTAX TimeStamp 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "The value of sysUpTime when the last of 1847 the following occurred: 1848 1) the agent cold- or warm-started; 1849 2) the row for the port was created 1850 (such as when a device or module was added 1851 to the system); or 1852 3) any condition that would cause one of 1853 the counters for the row to experience 1854 a discontinuity." 1855 ::= { rptrMonitorPortEntry 16 } 1857 rptrMonitor100PortTable OBJECT-TYPE 1858 SYNTAX SEQUENCE OF RptrMonitor100PortEntry 1859 MAX-ACCESS not-accessible 1860 STATUS current 1861 DESCRIPTION 1862 "Table of additional performance and error 1864 , 1865 statistics for 100Mb/s ports, above and 1866 beyond those parameters that apply to both 1867 10 and 100Mbps ports. Entries exist only for 1868 ports attached to 100Mbps repeaters. 1870 The columnar object rptrMonitorPortLastChange 1871 is used to indicate possible discontinuities 1872 of counter type columnar objects in this table." 1873 ::= { rptrMonitorPortInfo 2 } 1875 rptrMonitor100PortEntry OBJECT-TYPE 1876 SYNTAX RptrMonitor100PortEntry 1877 MAX-ACCESS not-accessible 1878 STATUS current 1879 DESCRIPTION 1880 "An entry in the table, containing performance 1881 and error statistics for a single 100Mb/s port." 1882 INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex } 1883 ::= { rptrMonitor100PortTable 1 } 1885 RptrMonitor100PortEntry ::= 1886 SEQUENCE { 1887 rptrMonitorPortIsolates 1888 Counter32, 1889 rptrMonitorPortSymbolErrors 1890 Counter32, 1891 rptrMonitorPortUpper32Octets 1892 Counter32, 1893 rptrMonitorPortHCReadableOctets 1894 Counter64 1895 } 1897 rptrMonitorPortIsolates OBJECT-TYPE 1898 SYNTAX Counter32 1899 MAX-ACCESS read-only 1900 STATUS current 1901 DESCRIPTION 1902 "This counter is incremented by one each time that 1903 the repeater port automatically isolates as a 1904 consequence of false carrier events. The conditions 1905 which cause a port to automatically isolate are 1906 defined by the transition from the False Carrier 1907 state to the Link Unstable state of the carrier 1908 integrity state diagram (figure 27-9) 1909 [IEEE 802.3 Standard]. 1911 , 1912 Note: Isolates do not affect the value of 1913 the PortOperStatus object. 1915 A discontinuity may occur in the value 1916 when the value of object 1917 rptrMonitorPortLastChange changes." 1918 REFERENCE 1919 "[IEEE 802.3 Mgt], 30.4.3.1.16, aIsolates." 1920 ::= { rptrMonitor100PortEntry 1 } 1922 rptrMonitorPortSymbolErrors OBJECT-TYPE 1923 SYNTAX Counter32 1924 MAX-ACCESS read-only 1925 STATUS current 1926 DESCRIPTION 1927 "This counter is incremented by one each time when 1928 valid length packet was received at the port and 1929 there was at least one occurrence of an invalid 1930 data symbol. This can increment only once per valid 1931 carrier event. A collision presence at any port of 1932 the repeater containing port N, will not cause this 1933 attribute to increment. 1935 A discontinuity may occur in the value 1936 when the value of object 1937 rptrMonitorPortLastChange changes. 1939 The approximate minimum time for rollover of this 1940 counter is 7.4 hours at 100Mb/s." 1941 REFERENCE 1942 "[IEEE 802.3 Mgt], 30.4.3.1.17, 1943 aSymbolErrorDuringPacket." 1944 ::= { rptrMonitor100PortEntry 2 } 1946 rptrMonitorPortUpper32Octets OBJECT-TYPE 1947 SYNTAX Counter32 1948 MAX-ACCESS read-only 1949 STATUS current 1950 DESCRIPTION 1951 "This object is the number of octets contained in 1952 valid frames that have been received on this port, 1953 modulo 2**32. That is, it contains the upper 32 1954 bits of a 64-bit octets counter, of which the 1955 lower 32 bits are contained in the 1956 rptrMonitorPortReadableOctets object. 1958 , 1959 This two-counter mechanism is provided for those 1960 network management protocols that do not support 1961 64-bit counters (e.g. SNMP V1) and are used to 1962 manage a repeater type of 100Mb/s. 1964 Conformance clauses for this MIB are defined such 1965 that implementation of this object is not required 1966 in a system which does not support 100Mb/s. 1967 However, systems with mixed 10 and 100Mb/s ports 1968 may implement this object across all ports, 1969 including 10Mb/s. If this object is implemented, 1970 it must be according to the definition in the first 1971 paragraph of this description; that is, the value 1972 of this object MUST be a valid count. 1974 A discontinuity may occur in the value 1975 when the value of object 1976 rptrMonitorPortLastChange changes." 1977 ::= { rptrMonitor100PortEntry 3 } 1979 rptrMonitorPortHCReadableOctets OBJECT-TYPE 1980 SYNTAX Counter64 1981 MAX-ACCESS read-only 1982 STATUS current 1983 DESCRIPTION 1984 "This object is the number of octets contained in 1985 valid frames that have been received on this port. 1986 This counter is incremented by OctetCount for each 1987 frame received on this port which has been 1988 determined to be a readable frame (i.e., including 1989 FCS octets but excluding framing bits and dribble 1990 bits). 1992 This statistic provides an indicator of the total 1993 data transferred. 1995 This counter is a 64-bit version of rptrMonitor- 1996 PortReadableOctets. It should be used by network 1997 management protocols which suppport 64-bit counters 1998 (e.g. SNMPv2). 2000 Conformance clauses for this MIB are defined such 2001 that implementation of this object is not required 2002 in a system which does not support 100Mb/s. 2004 , 2005 However, systems with mixed 10 and 100Mb/s ports 2006 may implement this object across all ports, 2007 including 10Mb/s. If this object is implemented, 2008 it must be according to the definition in the first 2009 paragraph of this description; that is, the value 2010 of this object MUST be a valid count. 2012 A discontinuity may occur in the value 2013 when the value of object 2014 rptrMonitorPortLastChange changes." 2015 REFERENCE 2016 "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets." 2017 ::= { rptrMonitor100PortEntry 4 } 2019 -- New version of statistics at the repeater level. 2020 -- 2021 -- Statistics objects for each managed repeater 2022 -- in the system. 2024 rptrMonTable OBJECT-TYPE 2025 SYNTAX SEQUENCE OF RptrMonEntry 2026 MAX-ACCESS not-accessible 2027 STATUS current 2028 DESCRIPTION 2029 "A table of information about each 2030 non-trivial repeater. The number of entries 2031 in this table is the same as the number of 2032 entries in the rptrInfoTable. 2034 The columnar object rptrInfoLastChange is 2035 used to indicate possible discontinuities of 2036 counter type columnar objects in this table." 2037 ::= { rptrMonitorAllRptrInfo 1 } 2039 rptrMonEntry OBJECT-TYPE 2040 SYNTAX RptrMonEntry 2041 MAX-ACCESS not-accessible 2042 STATUS current 2043 DESCRIPTION 2044 "An entry in the table, containing information 2045 about a single non-trivial repeater." 2046 INDEX { rptrInfoId } 2047 ::= { rptrMonTable 1 } 2049 , 2051 RptrMonEntry ::= 2052 SEQUENCE { 2053 rptrMonTxCollisions 2054 Counter32, 2055 rptrMonTotalFrames 2056 Counter32, 2057 rptrMonTotalErrors 2058 Counter32, 2059 rptrMonTotalOctets 2060 Counter32 2061 } 2063 rptrMonTxCollisions OBJECT-TYPE 2064 SYNTAX Counter32 2065 MAX-ACCESS read-only 2066 STATUS current 2067 DESCRIPTION 2068 "For a clause 9 (10Mb/s) repeater, this counter 2069 is incremented every time the repeater state 2070 machine enters the TRANSMIT COLLISION state 2071 from any state other than ONE PORT LEFT 2072 (Ref: Fig 9-2 [IEEE 802.3 Std]). 2074 For a clause 27 repeater, this counter is 2075 incremented every time the repeater core state 2076 diagram enters the Jam state as a result of 2077 Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). 2079 The approximate minimum time for rollover of this 2080 counter is 16 hours in a 10Mb/s repeater and 1.6 2081 hours in a 100Mb/s repeater." 2082 REFERENCE 2083 "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions" 2084 ::= { rptrMonEntry 1 } 2086 rptrMonTotalFrames OBJECT-TYPE 2087 SYNTAX Counter32 2088 MAX-ACCESS read-only 2089 STATUS current 2090 DESCRIPTION 2091 "The number of frames of valid frame length 2092 that have been received on the ports in this repeater 2093 and for which the FCSError and CollisionEvent 2094 signals were not asserted. If an implementation 2095 can not obtain a count of frames as seen by 2097 , 2098 the repeater itself, this counter may be 2099 implemented as the summation of the values of the 2100 rptrMonitorPortReadableFrames counters for all of 2101 the ports in the repeater. 2103 This statistic provides one of the parameters 2104 necessary for obtaining the packet error rate. 2105 The approximate minimum time for rollover of this 2106 counter is 80 hours in a 10Mb/s repeater." 2107 ::= { rptrMonEntry 3 } 2109 rptrMonTotalErrors OBJECT-TYPE 2110 SYNTAX Counter32 2111 MAX-ACCESS read-only 2112 STATUS current 2113 DESCRIPTION 2114 "The total number of errors which have occurred on 2115 all of the ports in this repeater. The errors 2116 included in this count are the same as those listed 2117 for the rptrMonitorPortTotalErrors counter. If an 2118 implementation can not obtain a count of these 2119 errors as seen by the repeater itself, this counter 2120 may be implemented as the summation of the values of 2121 the rptrMonitorPortTotalErrors counters for all of 2122 the ports in the repeater." 2123 ::= { rptrMonEntry 4 } 2125 rptrMonTotalOctets OBJECT-TYPE 2126 SYNTAX Counter32 2127 MAX-ACCESS read-only 2128 STATUS current 2129 DESCRIPTION 2130 "The total number of octets contained in the valid 2131 frames that have been received on the ports in 2132 this group. If an implementation can not obtain 2133 a count of octets as seen by the repeater itself, 2134 this counter may be the summation of the 2135 values of the rptrMonitorPortReadableOctets 2136 counters for all of the ports in the group. 2138 This statistic provides an indicator of the total 2139 data transferred. The approximate minimum time 2140 for rollover of this counter in a 10Mb/s repeater 2141 is 58 minutes divided by the number of ports in 2142 the repeater. 2144 , 2145 For 100Mb/s repeaters processing traffic at a 2146 maximum rate, this counter can roll over in less 2147 than 6 minutes divided by the number of ports in 2148 the repeater. Since that amount of time could 2149 be less than a management station's poll cycle 2150 time, in order to avoid a loss of information a 2151 management station is advised to also poll the 2152 rptrMonUpper32TotalOctets object, or to use the 2153 64-bit counter defined by rptrMonHCTotalOctets 2154 instead of the two 32-bit counters." 2155 ::= { rptrMonEntry 5 } 2157 rptrMon100Table OBJECT-TYPE 2158 SYNTAX SEQUENCE OF RptrMon100Entry 2159 MAX-ACCESS not-accessible 2160 STATUS current 2161 DESCRIPTION 2162 "A table of additional information about each 2163 100Mb/s repeater, augmenting the entries in 2164 the rptrMonTable. Entries exist in this table 2165 only for 100Mb/s repeaters. 2167 The columnar object rptrInfoLastChange is 2168 used to indicate possible discontinuities of 2169 counter type columnar objects in this table." 2170 ::= { rptrMonitorAllRptrInfo 2 } 2172 rptrMon100Entry OBJECT-TYPE 2173 SYNTAX RptrMon100Entry 2174 MAX-ACCESS not-accessible 2175 STATUS current 2176 DESCRIPTION 2177 "An entry in the table, containing information 2178 about a single 100Mbps repeater." 2179 INDEX { rptrInfoId } 2180 ::= { rptrMon100Table 1 } 2182 RptrMon100Entry ::= 2183 SEQUENCE { 2184 rptrMonUpper32TotalOctets 2185 Counter32, 2186 rptrMonHCTotalOctets 2187 Counter64 2188 } 2190 , 2192 rptrMonUpper32TotalOctets OBJECT-TYPE 2193 SYNTAX Counter32 2194 MAX-ACCESS read-only 2195 STATUS current 2196 DESCRIPTION 2197 "The total number of octets contained in the valid 2198 frames that have been received on the ports in 2199 this repeater, modulo 2**32. That is, it contains 2200 the upper 32 bits of a 64-bit counter, of which 2201 the lower 32 bits are contained in the 2202 rptrMonTotalOctets object. If an implementation 2203 can not obtain a count of octets as seen 2204 by the repeater itself, the 64-bit value 2205 may be the summation of the values of the 2206 rptrMonitorPortReadableOctets counters combined 2207 with the corresponding rptrMonitorPortUpper32Octets 2208 counters for all of the ports in the repeater. 2210 This statistic provides an indicator of the total 2211 data transferred within the repeater. 2213 This two-counter mechanism is provided for those 2214 network management protocols that do not support 2215 64-bit counters (e.g. SNMP V1) and are used to 2216 manage a repeater type of 100Mb/s. 2218 Conformance clauses for this MIB are defined such 2219 that implementation of this object is not required 2220 in a system which does not support 100Mb/s. 2221 However, systems with mixed 10 and 100Mb/s ports 2222 may implement this object across all ports, 2223 including 10Mb/s. If this object is implemented, 2224 it must be according to the definition in the first 2225 paragraph of this description; that is, the value 2226 of this object MUST be a valid count." 2227 ::= { rptrMon100Entry 1 } 2229 rptrMonHCTotalOctets OBJECT-TYPE 2230 SYNTAX Counter64 2231 MAX-ACCESS read-only 2232 STATUS current 2233 DESCRIPTION 2234 "The total number of octets contained in the valid 2235 frames that have been received on the ports in 2236 this group. If a implementation can not obtain 2238 , 2239 a count of octets as seen by the repeater itself, 2240 this counter may be the summation of the 2241 values of the rptrMonitorPortReadableOctets 2242 counters for all of the ports in the group. 2244 This statistic provides an indicator of the total 2245 data transferred. 2247 This counter is a 64-bit (high-capacity) version 2248 of rptrMonUpper32TotalOctets and rptrMonTotalOctets. 2249 It should be used by network management protocols 2250 which support 64-bit counters (e.g. SNMPv2). 2252 Conformance clauses for this MIB are defined such 2253 that implementation of this object is not required 2254 in a system which does not support 100Mb/s. 2255 However, systems with mixed 10 and 100Mb/s ports 2256 may implement this object across all ports, 2257 including 10Mb/s. If this object is implemented, 2258 it must be according to the definition in the first 2259 paragraph of this description; that is, the value 2260 of this object MUST be a valid count." 2261 ::= { rptrMon100Entry 2 } 2263 -- 2264 -- The Repeater Address Search Table 2265 -- 2266 -- This table provides an active address tracking 2267 -- capability which can be also used to collect the 2268 -- necessary information for mapping the topology 2269 -- of a network. Note that an NMS is required to have 2270 -- read-write access to the table in order to access 2271 -- this function. Section 4, "Topology Mapping", 2272 -- contains a description of an algorithm which can 2273 -- make use of this table, in combination with the 2274 -- forwarding databases of managed bridges/switches 2275 -- in the network, to map network topology. 2276 -- 2278 rptrAddrSearchTable OBJECT-TYPE 2279 SYNTAX SEQUENCE OF RptrAddrSearchEntry 2280 MAX-ACCESS not-accessible 2281 STATUS current 2282 DESCRIPTION 2284 , 2285 "This table contains one entry per repeater in the 2286 system. It defines objects which allow a network 2287 management application to instruct an agent to watch 2288 for a given MAC address and report which port it 2289 was seen on. Only one address search can be in 2290 progress on each repeater at any one time. Before 2291 starting an address search, a management application 2292 should obtain 'ownership' of the entry in 2293 rptrAddrSearchTable for the repeater that is to 2294 perform the search. This is accomplished with the 2295 rptrAddrSearchLock and rptrAddrSearchStatus as 2296 follows: 2298 try_again: 2299 get(rptrAddrSearchLock, rptrAddrSearchStatus) 2300 while (rptrAddrSearchStatus != notInUse) 2301 { 2302 /* Loop waiting for objects to be available*/ 2303 short delay 2304 get(rptrAddrSearchLock, rptrAddrSearchStatus) 2305 } 2307 /* Try to claim map objects */ 2308 lock_value = rptrAddrSearchLock 2309 if ( set(rptrAddrSearchLock = lock_value, 2310 rptrAddrSearchStatus = inUse, 2311 rptrAddrSearchOwner = 'my-IP-address) 2312 == FAILURE) 2313 /* Another manager got the lock */ 2314 goto try_again 2316 /* I have the lock */ 2317 set (rptrAddrSearchAddress = ) 2319 wait for rptrAddrSearchState to change from none 2321 if (rptrAddrSearchState == single) 2322 get (rptrAddrSearchGroup, rptrAddrSearchPort) 2324 /* release the lock, making sure not to overwrite 2325 anyone else's lock */ 2326 set (rptrAddrSearchLock = lock_value+1, 2327 rptrAddrSearchStatus = notInUse, 2328 rptrAddrSearchOwner = '') 2330 , 2332 A management station first retrieves the values of 2333 the appropriate instances of the rptrAddrSearchLock 2334 and rptrAddrSearchStatus objects, periodically 2335 repeating the retrieval if necessary, until the value 2336 of rptrAddrSearchStatus is 'notInUse'. The 2337 management station then tries to set the same 2338 instance of the rptrAddrSearchLock object to the 2339 value it just retrieved, the same instance of the 2340 rptrAddrSearchStatus object to 'inUse', and the 2341 corresponding instance of rptrAddrSearchOwner to a 2342 value indicating itself. If the set operation 2343 succeeds, then the management station has obtained 2344 ownership of the rptrAddrSearchEntry, and the value 2345 of rptrAddrSearchLock is incremented by the agent (as 2346 per the semantics of TestAndIncr). Failure of the 2347 set operation indicates that some other manager has 2348 obtained ownership of the rptrAddrSearchEntry. 2350 Once ownership is obtained, the management station 2351 can proceed with the search operation. Note that the 2352 agent will reset rptrAddrSearchStatus to 'notInUse' 2353 if it has been in the 'inUse' state for an abnormally 2354 long period of time, to prevent a misbehaving manager 2355 from permanently locking the entry. It is suggested 2356 that this timeout period be between one and five 2357 minutes. 2359 When the management station has completed its search 2360 operation, it should free the entry by setting 2361 the instance of the rptrAddrSearchLock object to the 2362 previous value + 1, the instance of the 2363 rptrAddrSearchStatus to 'notInUse', and the instance 2364 of rptrAddrSearchOwner to a zero length string. This 2365 is done to prevent overwriting another station's 2366 lock." 2367 ::= { rptrAddrTrackRptrInfo 1 } 2369 rptrAddrSearchEntry OBJECT-TYPE 2370 SYNTAX RptrAddrSearchEntry 2371 MAX-ACCESS not-accessible 2372 STATUS current 2373 DESCRIPTION 2374 "An entry containing objects for invoking an address 2375 search on a repeater." 2376 INDEX { rptrInfoId } 2378 , 2379 ::= { rptrAddrSearchTable 1 } 2381 RptrAddrSearchEntry ::= 2382 SEQUENCE { 2383 rptrAddrSearchLock TestAndIncr, 2384 rptrAddrSearchStatus INTEGER, 2385 rptrAddrSearchAddress MacAddress, 2386 rptrAddrSearchState INTEGER, 2387 rptrAddrSearchGroup Integer32, 2388 rptrAddrSearchPort Integer32, 2389 rptrAddrSearchOwner OwnerString 2390 } 2392 rptrAddrSearchLock OBJECT-TYPE 2393 SYNTAX TestAndIncr 2394 MAX-ACCESS read-write 2395 STATUS current 2396 DESCRIPTION 2397 "This object is used by a management station as an 2398 advisory lock for this rptrAddrSearchEntry." 2399 ::= { rptrAddrSearchEntry 1 } 2401 rptrAddrSearchStatus OBJECT-TYPE 2402 SYNTAX INTEGER { 2403 notInUse(1), 2404 inUse(2) 2405 } 2406 MAX-ACCESS read-write 2407 STATUS current 2408 DESCRIPTION 2409 "This object is used to indicate that some management 2410 station is currently using this rptrAddrSearchEntry. 2411 Cooperating managers should set this object to 2412 'notInUse' when they are finished using this entry. 2413 The agent will automatically set the value of this 2414 object to 'notInUse' if it has been set to 'inUse' 2415 for an unusually long period of time." 2416 ::= { rptrAddrSearchEntry 2 } 2418 rptrAddrSearchAddress OBJECT-TYPE 2419 SYNTAX MacAddress 2420 MAX-ACCESS read-write 2421 STATUS current 2422 DESCRIPTION 2424 , 2425 "This object is used to search for a specified MAC 2426 address. When this object is set, an address search 2427 begins. This automatically sets the corresponding 2428 instance of the rptrAddrSearchState object to 'none' 2429 and the corresponding instances of the 2430 rptrAddrSearchGroup and rptrAddrSearchPort objects to 2431 0. 2433 When a valid frame is received by this repeater with 2434 a source MAC address which matches the current value 2435 of rptrAddrSearchAddress, the agent will update the 2436 corresponding instances of rptrAddrSearchState, 2437 rptrAddrSearchGroup and rptrAddrSearchPort to reflect 2438 the current status of the search, and the group and 2439 port on which the frame was seen." 2440 ::= { rptrAddrSearchEntry 3 } 2442 rptrAddrSearchState OBJECT-TYPE 2443 SYNTAX INTEGER { 2444 none(1), 2445 single(2), 2446 multiple(3) 2447 } 2448 MAX-ACCESS read-only 2449 STATUS current 2450 DESCRIPTION 2451 "The current state of the MAC address search on this 2452 repeater. This object is initialized to 'none' when 2453 the corresponding instance of rptrAddrSearchAddress 2454 is set. If the agent detects the address on exactly 2455 one port, it will set this object to 'single', and 2456 set the corresponding instances of 2457 rptrAddrSearchGroup and rptrAddrSearchPort to reflect 2458 the group and port on which the address was heard. 2459 If the agent detects the address on more than one 2460 port, it will set this object to 'multiple'." 2461 ::= { rptrAddrSearchEntry 4 } 2463 rptrAddrSearchGroup OBJECT-TYPE 2464 SYNTAX Integer32 (0..2147483647) 2465 MAX-ACCESS read-only 2466 STATUS current 2467 DESCRIPTION 2468 "The group from which an error-free frame whose 2469 source address is equal to the corresponding instance 2471 , 2472 of rptrAddrSearchAddress has been received. The 2473 value of this object is undefined when the 2474 corresponding instance of rptrAddrSearchState is 2475 equal to 'none' or 'multiple'." 2476 ::= { rptrAddrSearchEntry 5 } 2478 rptrAddrSearchPort OBJECT-TYPE 2479 SYNTAX Integer32 (0..2147483647) 2480 MAX-ACCESS read-only 2481 STATUS current 2482 DESCRIPTION 2483 "The port rom which an error-free frame whose 2484 source address is equal to the corresponding instance 2485 of rptrAddrSearchAddress has been received. The 2486 value of this object is undefined when the 2487 corresponding instance of rptrAddrSearchState is 2488 equal to 'none' or 'multiple'." 2489 ::= { rptrAddrSearchEntry 6 } 2491 rptrAddrSearchOwner OBJECT-TYPE 2492 SYNTAX OwnerString 2493 MAX-ACCESS read-write 2494 STATUS current 2495 DESCRIPTION 2496 "The entity which currently has 'ownership' of this 2497 rptrAddrSearchEntry." 2498 ::= { rptrAddrSearchEntry 7 } 2500 -- 2501 -- The Port Address Tracking Table 2502 -- 2503 -- This table provides a way for a network management 2504 -- application to passively gather information (using 2505 -- read-only privileges) about which network addresses 2506 -- are connected to which ports of a repeater. 2507 -- 2509 rptrAddrTrackTable OBJECT-TYPE 2510 SYNTAX SEQUENCE OF RptrAddrTrackEntry 2511 MAX-ACCESS not-accessible 2512 STATUS current 2513 DESCRIPTION 2514 "Table of address mapping information about the 2515 ports." 2517 , 2519 ::= { rptrAddrTrackPortInfo 1 } 2521 rptrAddrTrackEntry OBJECT-TYPE 2522 SYNTAX RptrAddrTrackEntry 2523 MAX-ACCESS not-accessible 2524 STATUS current 2525 DESCRIPTION 2526 "An entry in the table, containing address mapping 2527 information about a single port." 2528 INDEX { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex } 2529 ::= { rptrAddrTrackTable 1 } 2531 RptrAddrTrackEntry ::= 2532 SEQUENCE { 2533 rptrAddrTrackGroupIndex 2534 INTEGER, 2535 rptrAddrTrackPortIndex 2536 INTEGER, 2537 rptrAddrTrackLastSourceAddress -- DEPRECATED OBJECT 2538 MacAddress, 2539 rptrAddrTrackSourceAddrChanges 2540 Counter32, 2541 rptrAddrTrackNewLastSrcAddress 2542 OptMacAddr, 2543 rptrAddrTrackCapacity 2544 Integer32 2545 } 2547 rptrAddrTrackGroupIndex OBJECT-TYPE 2548 SYNTAX INTEGER (1..2147483647) 2549 MAX-ACCESS read-only 2550 STATUS current 2551 DESCRIPTION 2552 "This object identifies the group containing the 2553 port for which this entry contains information." 2554 ::= { rptrAddrTrackEntry 1 } 2556 rptrAddrTrackPortIndex OBJECT-TYPE 2557 SYNTAX INTEGER (1..2147483647) 2558 MAX-ACCESS read-only 2559 STATUS current 2560 DESCRIPTION 2561 "This object identifies the port within the group 2562 for which this entry contains information." 2563 REFERENCE 2565 , 2566 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." 2567 ::= { rptrAddrTrackEntry 2 } 2569 rptrAddrTrackLastSourceAddress OBJECT-TYPE 2570 SYNTAX MacAddress 2571 MAX-ACCESS read-only 2572 STATUS deprecated 2573 DESCRIPTION 2574 "********* THIS OBJECT IS DEPRECATED ********** 2576 This object is the SourceAddress of the last 2577 readable frame (i.e., counted by 2578 rptrMonitorPortReadableFrames) received by this 2579 port. 2581 This object has been deprecated because its value 2582 is undefined when no frames have been observed on 2583 this port. The replacement object is 2584 rptrAddrTrackNewLastSrcAddress." 2585 REFERENCE 2586 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2587 ::= { rptrAddrTrackEntry 3 } 2589 rptrAddrTrackSourceAddrChanges OBJECT-TYPE 2590 SYNTAX Counter32 2591 MAX-ACCESS read-only 2592 STATUS current 2593 DESCRIPTION 2594 "This counter is incremented by one for each time 2595 that the rptrAddrTrackLastSourceAddress attribute 2596 for this port has changed. 2598 This may indicate whether a link is connected to a 2599 single DTE or another multi-user segment. 2601 A discontinuity may occur in the value when the 2602 value of object rptrMonitorPortLastChange changes. 2604 The approximate minimum time for rollover of this 2605 counter is 81 hours in a 10Mb/s repeater." 2606 REFERENCE 2607 "[IEEE 802.3 Mgt], 30.4.3.1.19, aSourceAddressChanges." 2608 ::= { rptrAddrTrackEntry 4 } 2610 rptrAddrTrackNewLastSrcAddress OBJECT-TYPE 2612 , 2613 SYNTAX OptMacAddr 2614 MAX-ACCESS read-only 2615 STATUS current 2616 DESCRIPTION 2617 "This object is the SourceAddress of the last 2618 readable frame (i.e., counted by 2619 rptrMonitorPortReadableFrames) received by this 2620 port. If no frames have been received by this 2621 port since the agent began monitoring the port 2622 activity, the agent shall return a string of 2623 length zero." 2624 REFERENCE 2625 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2626 ::= { rptrAddrTrackEntry 5 } 2628 rptrAddrTrackCapacity OBJECT-TYPE 2629 SYNTAX Integer32 2630 MAX-ACCESS read-only 2631 STATUS current 2632 DESCRIPTION 2633 "The maximum number of addresses that can be 2634 detected on this port. This value indicates 2635 to the maximum number of entries in the 2636 rptrExtAddrTrackTable relative to this port. 2638 If this object has the value of 1, the agent 2639 implements only the LastSourceAddress mechanism 2640 described by RFC 1368 or RFC 1516." 2641 ::= { rptrAddrTrackEntry 6 } 2643 -- Table for multiple addresses per port 2645 rptrExtAddrTrackTable OBJECT-TYPE 2646 SYNTAX SEQUENCE OF RptrExtAddrTrackEntry 2647 MAX-ACCESS not-accessible 2648 STATUS current 2649 DESCRIPTION 2650 "A table to extend the address tracking table (i.e., 2651 rptrAddrTrackTable) with a list of source MAC 2652 addresses that were recently received on each port. 2653 The number of ports is the same as the number 2654 of entries in table rptrPortTable. The number of 2655 entries in this table depends on the agent/repeater 2656 implementation and the number of different 2658 , 2659 addresses received on each port. 2661 The first entry for each port contains 2662 the same MAC address that is given by the 2663 rptrAddrTrackNewLastSrcAddress for that port. 2665 Entries in this table for a particular port are 2666 retained when that port is switched from one 2667 repeater to another. 2669 The ordering of MAC addresses listed for a 2670 particular port is implementation dependent." 2671 ::= { rptrAddrTrackPortInfo 2 } 2673 rptrExtAddrTrackEntry OBJECT-TYPE 2674 SYNTAX RptrExtAddrTrackEntry 2675 MAX-ACCESS not-accessible 2676 STATUS current 2677 DESCRIPTION 2678 "A row in the table of extended address tracking 2679 information for ports. Entries can not be directly 2680 created or deleted via SNMP operations." 2681 INDEX { rptrAddrTrackGroupIndex, 2682 rptrAddrTrackPortIndex, 2683 rptrExtAddrTrackMacIndex } 2684 ::= { rptrExtAddrTrackTable 1 } 2686 RptrExtAddrTrackEntry ::= SEQUENCE { 2687 rptrExtAddrTrackMacIndex Integer32, 2688 rptrExtAddrTrackSourceAddress MacAddress 2689 } 2691 rptrExtAddrTrackMacIndex OBJECT-TYPE 2692 SYNTAX Integer32 (1..2147483647) 2693 MAX-ACCESS read-only 2694 STATUS current 2695 DESCRIPTION 2696 "The index of a source MAC address seen on 2697 the port. 2699 The ordering of MAC addresses listed for a 2700 particular port is implementation dependent. 2702 There is no implied relationship between a 2703 particular index and a particular MAC 2705 , 2706 address. The index for a particular MAC 2707 address may change without notice." 2708 ::= { rptrExtAddrTrackEntry 1 } 2710 rptrExtAddrTrackSourceAddress OBJECT-TYPE 2711 SYNTAX MacAddress 2712 MAX-ACCESS read-only 2713 STATUS current 2714 DESCRIPTION 2715 "The source MAC address from a readable frame 2716 (i.e., counted by rptrMonitorPortReadableFrames) 2717 recently received by the port." 2718 REFERENCE 2719 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2720 ::= { rptrExtAddrTrackEntry 2 } 2722 -- The Repeater Top "N" Port Group 2724 -- The Repeater Top N Port group is used to prepare reports that 2725 -- describe a list of ports ordered by one of the statistics in the 2726 -- Repeater Monitor Port Table. The statistic chosen by the 2727 -- management station is sampled over a management 2728 -- station-specified time interval, making the report rate based. 2729 -- The management station also specifies the number of ports that 2730 -- are reported. 2731 -- 2732 -- The rptrTopNPortControlTable is used to initiate the generation 2733 -- of a report. The management station may select the parameters 2734 -- of such a report, such as which repeater, which statistic, how 2735 -- many ports, and the start & stop times of the sampling. When 2736 -- the report is prepared, entries are created in the 2737 -- rptrTopNPortTable associated with the relevent 2738 -- rptrTopNControlEntry. These entries are static for 2739 -- each report after it has been prepared. 2741 -- Note that counter discontinuities may appear in some 2742 -- implementations if ports' assignment to repeaters changes 2743 -- during the collection of data for a Top "N" report. 2744 -- A management application could read the corresponding 2745 -- rptrMonitorPortLastChange timestamp in order to check 2746 -- whether a discontinuity occurred. 2748 rptrTopNPortControlTable OBJECT-TYPE 2750 , 2751 SYNTAX SEQUENCE OF RptrTopNPortControlEntry 2752 MAX-ACCESS not-accessible 2753 STATUS current 2754 DESCRIPTION 2755 "A table of control records for reports on the top `N' 2756 ports for the rate of a selected counter. The number 2757 of entries depends on the configuration of the agent. 2758 The maximum number of entries is implementation 2759 dependent." 2760 ::= { rptrTopNPortInfo 1 } 2762 rptrTopNPortControlEntry OBJECT-TYPE 2763 SYNTAX RptrTopNPortControlEntry 2764 MAX-ACCESS not-accessible 2765 STATUS current 2766 DESCRIPTION 2767 "A set of parameters that control the creation of a 2768 report of the top N ports according to several metrics." 2769 INDEX { rptrTopNPortControlIndex } 2770 ::= { rptrTopNPortControlTable 1 } 2772 RptrTopNPortControlEntry ::= SEQUENCE { 2773 rptrTopNPortControlIndex 2774 Integer32, 2775 rptrTopNPortRepeaterId 2776 Integer32, 2777 rptrTopNPortRateBase 2778 INTEGER, 2779 rptrTopNPortTimeRemaining 2780 Integer32, 2781 rptrTopNPortDuration 2782 Integer32, 2783 rptrTopNPortRequestedSize 2784 Integer32, 2785 rptrTopNPortGrantedSize 2786 Integer32, 2787 rptrTopNPortStartTime 2788 TimeStamp, 2789 rptrTopNPortOwner 2790 OwnerString, 2791 rptrTopNPortRowStatus 2792 RowStatus 2793 } 2795 rptrTopNPortControlIndex OBJECT-TYPE 2797 , 2798 SYNTAX Integer32 (1 .. 65535) 2799 MAX-ACCESS read-only 2800 STATUS current 2801 DESCRIPTION 2802 "An index that uniquely identifies an entry in the 2803 rptrTopNPortControl table. Each such entry defines 2804 one top N report prepared for a repeater or system." 2805 ::= { rptrTopNPortControlEntry 1 } 2807 rptrTopNPortRepeaterId OBJECT-TYPE 2808 SYNTAX Integer32 (0..2147483647) 2809 MAX-ACCESS read-create 2810 STATUS current 2811 DESCRIPTION 2812 "Identifies the repeater for which a top N report will 2813 be prepared (see rptrInfoId). If the value of this 2814 object is positive, only ports assigned to this repeater 2815 will be used to form the list in which to order the 2816 Top N table. If this value is zero, all ports will be 2817 eligible for inclusion on the list. 2819 The value of this object may not be modified if the 2820 associated rptrTopNPortRowStatus object is equal to 2821 active(1). 2823 If, for a particular row in this table, the repeater 2824 specified by the value of this object goes away (is 2825 removed from the rptrInfoTable) while the associated 2826 rptrTopNPortRowStatus object is equal to active(1), 2827 the row in this table is preserved by the agent but 2828 the value of rptrTopNPortRowStatus is changed to 2829 notInService(2), and the agent may time out the row 2830 if appropriate. If the specified repeater comes 2831 back (reappears in the rptrInfoTable) before the row 2832 has been timed out, the management station must set 2833 the value of the rptrTopNPortRowStatus object back 2834 to active(1) if desired (the agent doesn't do this 2835 automatically)." 2836 ::= { rptrTopNPortControlEntry 2 } 2838 rptrTopNPortRateBase OBJECT-TYPE 2839 SYNTAX INTEGER { 2840 readableFrames(1), 2841 readableOctets(2), 2842 fcsErrors(3), 2844 , 2845 alignmentErrors(4), 2846 frameTooLongs(5), 2847 shortEvents(6), 2848 runts(7), 2849 collisions(8), 2850 lateEvents(9), 2851 veryLongEvents(10), 2852 dataRateMismatches(11), 2853 autoPartitions(12), 2854 totalErrors(13), 2855 isolates(14), 2856 symbolErrors(15) 2857 } 2858 MAX-ACCESS read-create 2859 STATUS current 2860 DESCRIPTION 2861 "The monitored variable, which the rptrTopNPortRate 2862 variable is based upon. 2864 The value of this object may not be modified if 2865 the associated rptrTopNPortRowStatus object has 2866 a value of active(1)." 2867 ::= { rptrTopNPortControlEntry 3 } 2869 rptrTopNPortTimeRemaining OBJECT-TYPE 2870 SYNTAX Integer32 (0..2147483647) 2871 MAX-ACCESS read-create 2872 STATUS current 2873 DESCRIPTION 2874 "The number of seconds left in the report 2875 currently being collected. When this object 2876 is modified by the management station, a new 2877 collection is started, possibly aborting a 2878 currently running report. The new value is 2879 used as the requested duration of this report, 2880 which is loaded into the associated 2881 rptrTopNPortDuration object. 2883 When this object is set to a non-zero value, 2884 any associated rptrTopNPortEntries shall be 2885 made inaccessible by the agent. While the value 2886 of this object is non-zero, it decrements by one 2887 per second until it reaches zero. During this 2888 time, all associated rptrTopNPortEntries shall 2889 remain inaccessible. At the time that this object 2891 , 2892 decrements to zero, the report is made accessible 2893 in the rptrTopNPortTable. Thus, the rptrTopNPort 2894 table needs to be created only at the end of the 2895 collection interval. 2897 If the value of this object is set to zero 2898 while the associated report is running, the 2899 running report is aborted and no associated 2900 rptrTopNPortEntries are created." 2901 DEFVAL { 0 } 2902 ::= { rptrTopNPortControlEntry 4 } 2904 rptrTopNPortDuration OBJECT-TYPE 2905 SYNTAX Integer32 (0..2147483647) 2906 MAX-ACCESS read-only 2907 STATUS current 2908 DESCRIPTION 2909 "The number of seconds that this report has 2910 collected during the last sampling interval, 2911 or if this report is currently being collected, 2912 the number of seconds that this report is being 2913 collected during this sampling interval. 2915 When the associated rptrTopNPortTimeRemaining 2916 object is set, this object shall be set by the 2917 agent to the same value and shall not be modified 2918 until the next time the rptrTopNPortTimeRemaining 2919 is set. 2921 This value shall be zero if no reports have been 2922 requested for this rptrTopNPortControlEntry." 2923 ::= { rptrTopNPortControlEntry 5 } 2925 rptrTopNPortRequestedSize OBJECT-TYPE 2926 SYNTAX Integer32 2927 MAX-ACCESS read-create 2928 STATUS current 2929 DESCRIPTION 2930 "The maximum number of repeater ports requested 2931 for the Top N Table. 2933 When this object is created or modified, the 2934 agent should set rptrTopNPortGrantedSize as close 2935 to this object as is possible for the particular 2936 implementation and available resources." 2938 , 2940 DEFVAL { 10 } 2941 ::= { rptrTopNPortControlEntry 6 } 2943 rptrTopNPortGrantedSize OBJECT-TYPE 2944 SYNTAX Integer32 (0..65535) 2945 MAX-ACCESS read-only 2946 STATUS current 2947 DESCRIPTION 2948 "The maximum number of repeater ports in the 2949 top N table. 2951 When the associated rptrTopNPortRequestedSize object is 2952 created or modified, the agent should set this object as 2953 closely to the requested value as is possible for the 2954 particular implementation and available resources. The 2955 agent must not lower this value except as a result of a 2956 set to the associated rptrTopNPortRequestedSize object." 2957 ::= { rptrTopNPortControlEntry 7 } 2959 rptrTopNPortStartTime OBJECT-TYPE 2960 SYNTAX TimeStamp 2961 MAX-ACCESS read-only 2962 STATUS current 2963 DESCRIPTION 2964 "The value of sysUpTime when this top N report was 2965 last started. In other words, this is the time that 2966 the associated rptrTopNPortTimeRemaining object was 2967 modified to start the requested report. 2969 If the report has not yet been started, the value 2970 of this object is zero." 2971 ::= { rptrTopNPortControlEntry 8 } 2973 rptrTopNPortOwner OBJECT-TYPE 2974 SYNTAX OwnerString 2975 MAX-ACCESS read-create 2976 STATUS current 2977 DESCRIPTION 2978 "The entity that configured this entry and is 2979 using the resources assigned to it." 2980 ::= { rptrTopNPortControlEntry 9 } 2982 rptrTopNPortRowStatus OBJECT-TYPE 2983 SYNTAX RowStatus 2984 MAX-ACCESS read-create 2986 , 2987 STATUS current 2988 DESCRIPTION 2989 "The status of this row. 2991 If the value of this object is not equal to 2992 active(1), all associated entries in the 2993 rptrTopNPortTable shall be deleted by the 2994 agent." 2995 ::= { rptrTopNPortControlEntry 10 } 2997 -- Top "N" reports 2999 rptrTopNPortTable OBJECT-TYPE 3000 SYNTAX SEQUENCE OF RptrTopNPortEntry 3001 MAX-ACCESS not-accessible 3002 STATUS current 3003 DESCRIPTION 3004 "A table of reports for the top `N' ports based on 3005 setting of associated control table entries. The 3006 maximum number of entries depends on the number 3007 of entries in table rptrTopNPortControlTable and 3008 the value of object rptrTopNPortGrantedSize for 3009 each entry. 3011 For each entry in the rptrTopNPortControlTable, 3012 repeater ports with the highest value of 3013 rptrTopNPortRate shall be placed in this table 3014 in decreasing order of that rate until there is 3015 no more room or until there are no more ports." 3016 ::= { rptrTopNPortInfo 2 } 3018 rptrTopNPortEntry OBJECT-TYPE 3019 SYNTAX RptrTopNPortEntry 3020 MAX-ACCESS not-accessible 3021 STATUS current 3022 DESCRIPTION 3023 "A set of statistics for a repeater port that is 3024 part of a top N report." 3025 INDEX { rptrTopNPortControlIndex, 3026 rptrTopNPortIndex } 3027 ::= { rptrTopNPortTable 1 } 3029 RptrTopNPortEntry ::= SEQUENCE { 3030 rptrTopNPortIndex 3032 , 3033 Integer32, 3034 rptrTopNPortGroupIndex 3035 Integer32, 3036 rptrTopNPortPortIndex 3037 Integer32, 3038 rptrTopNPortRate 3039 Gauge32 3040 } 3042 rptrTopNPortIndex OBJECT-TYPE 3043 SYNTAX Integer32 (1..65535) 3044 MAX-ACCESS read-only 3045 STATUS current 3046 DESCRIPTION 3047 "An index that uniquely identifies an entry in 3048 the rptrTopNPort table among those in the same 3049 report. This index is between 1 and N, where N 3050 is the number of entries in this report. Increasing 3051 values of rptrTopNPortIndex shall be assigned to 3052 entries with decreasing values of rptrTopNPortRate 3053 until index N is assigned to the entry with the 3054 lowest value of rptrTopNPortRate or there are no 3055 more rptrTopNPortEntries. 3057 No ports are included in a report where their 3058 value of rptrTopNPortRate would be zero." 3059 ::= { rptrTopNPortEntry 1 } 3061 rptrTopNPortGroupIndex OBJECT-TYPE 3062 SYNTAX Integer32 (1..2147483647) 3063 MAX-ACCESS read-only 3064 STATUS current 3065 DESCRIPTION 3066 "This object identifes the group containing 3067 the port for this entry. (See also object 3068 type rptrGroupIndex.)" 3069 ::= { rptrTopNPortEntry 2 } 3071 rptrTopNPortPortIndex OBJECT-TYPE 3072 SYNTAX Integer32 (1..2147483647) 3073 MAX-ACCESS read-only 3074 STATUS current 3075 DESCRIPTION 3076 "The index of the repeater port. 3077 (See object type rptrPortIndex.)" 3079 , 3081 ::= { rptrTopNPortEntry 3 } 3083 rptrTopNPortRate OBJECT-TYPE 3084 SYNTAX Gauge32 3085 MAX-ACCESS read-only 3086 STATUS current 3087 DESCRIPTION 3088 "The amount of change in the selected variable 3089 during this sampling interval for the identified 3090 port. The selected variable is that port's 3091 instance of the object selected by 3092 rptrTopNPortRateBase." 3093 ::= { rptrTopNPortEntry 4 } 3095 -- Notifications for use by Repeaters 3097 rptrHealth NOTIFICATION-TYPE 3098 OBJECTS { rptrOperStatus } 3099 STATUS deprecated 3100 DESCRIPTION 3101 "********* THIS OBJECT IS DEPRECATED ********** 3103 In a system containing a single managed repeater, 3104 the rptrHealth notification conveys information 3105 related to the operational status of the repeater. 3106 It is sent either when the value of 3107 rptrOperStatus changes, or upon completion of a 3108 non-disruptive test. 3110 The rptrHealth notification must contain the 3111 rptrOperStatus object. The agent may optionally 3112 include the rptrHealthText object in the varBind 3113 list. See the rptrOperStatus and rptrHealthText 3114 objects for descriptions of the information that 3115 is sent. 3117 The agent must throttle the generation of 3118 consecutive rptrHealth traps so that there is at 3119 least a five-second gap between traps of this 3120 type. When traps are throttled, they are dropped, 3121 not queued for sending at a future time. (Note 3122 that 'generating' a trap means sending to all 3123 configured recipients.)" 3125 , 3127 REFERENCE 3128 "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth 3129 notification." 3130 ::= { snmpDot3RptrMgt 0 1 } 3132 rptrGroupChange NOTIFICATION-TYPE 3133 OBJECTS { rptrGroupIndex } 3134 STATUS deprecated 3135 DESCRIPTION 3136 "********* THIS OBJECT IS DEPRECATED ********** 3138 In a system containing a single managed repeater, 3139 this notification is sent when a change occurs in the 3140 group structure of the repeater. This occurs only 3141 when a group is logically or physically removed 3142 from or added to a repeater. The varBind list 3143 contains the identifier of the group that was 3144 removed or added. 3146 The agent must throttle the generation of 3147 consecutive rptrGroupChange traps for the same 3148 group so that there is at least a five-second gap 3149 between traps of this type. When traps are 3150 throttled, they are dropped, not queued for 3151 sending at a future time. (Note that 'generating' 3152 a trap means sending to all configured 3153 recipients.)" 3154 REFERENCE 3155 "[IEEE 802.3 Mgt], 30.4.1.3.3, nGroupMapChange 3156 notification." 3157 ::= { snmpDot3RptrMgt 0 2 } 3159 rptrResetEvent NOTIFICATION-TYPE 3160 OBJECTS { rptrOperStatus } 3161 STATUS deprecated 3162 DESCRIPTION 3163 "********* THIS OBJECT IS DEPRECATED ********** 3165 In a system containing a single managed repeater-unit, 3166 the rptrResetEvent notification conveys information 3167 related to the operational status of the repeater. 3168 This trap is sent on completion of a repeater 3169 reset action. A repeater reset action is defined 3170 as an a transition to the START state of Fig 9-2 3171 in section 9 [IEEE 802.3 Std], when triggered by a 3173 , 3174 management command (e.g., an SNMP Set on the 3175 rptrReset object). 3177 The agent must throttle the generation of 3178 consecutive rptrResetEvent traps so that there is 3179 at least a five-second gap between traps of this 3180 type. When traps are throttled, they are dropped, 3181 not queued for sending at a future time. (Note 3182 that 'generating' a trap means sending to all 3183 configured recipients.) 3185 The rptrResetEvent trap is not sent when the agent 3186 restarts and sends an SNMP coldStart or warmStart 3187 trap. However, it is recommended that a repeater 3188 agent send the rptrOperStatus object as an 3189 optional object with its coldStart and warmStart 3190 trap PDUs. 3192 The rptrOperStatus object must be included in the 3193 varbind list sent with this trap. The agent may 3194 optionally include the rptrHealthText object as 3195 well." 3196 REFERENCE 3197 "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset 3198 notification." 3199 ::= { snmpDot3RptrMgt 0 3 } 3201 -- Notifications for repeaters in a multiple-repeater implementation. 3202 -- An implementation may send either the single-repeater OR 3203 -- multiple-repeater version of these notifications (1 or 4; 2 or 5) 3204 -- but not both. 3206 rptrInfoHealth NOTIFICATION-TYPE 3207 OBJECTS { rptrInfoOperStatus } 3208 STATUS current 3209 DESCRIPTION 3210 "In a system containing multiple managed repeaters, 3211 the rptrInfoHealth notification conveys information 3212 related to the operational status of a repeater. 3213 It is sent either when the value of rptrInfoOperStatus 3214 changes, or upon completion of a non-disruptive test. 3216 The agent must throttle the generation of 3217 consecutive rptrInfoHealth notifications for 3219 , 3220 the same repeater so that there is at least 3221 a five-second gap between notifications of this type. 3222 When notifications are throttled, they are dropped, 3223 not queued for sending at a future time. (Note 3224 that 'generating' a notification means sending 3225 to all configured recipients.)" 3226 REFERENCE 3227 "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth 3228 notification." 3229 ::= { snmpDot3RptrMgt 0 4 } 3231 rptrInfoResetEvent NOTIFICATION-TYPE 3232 OBJECTS { rptrInfoOperStatus } 3233 STATUS current 3234 DESCRIPTION 3235 "In a system containing multiple managed 3236 repeaters, the rptrInfoResetEvent notification 3237 conveys information related to the operational 3238 status of a repeater. This notification is sent 3239 on completion of a repeater reset action. A 3240 repeater reset action is defined as a transition 3241 to the START state of Fig 9-2 in section 9 of 3242 [IEEE 802.3 Std], when triggered by a management 3243 command (e.g., an SNMP Set on the rptrInfoReset 3244 object). 3246 The agent must throttle the generation of 3247 consecutive rptrInfoResetEvent notifications for 3248 a single repeater so that there is at least 3249 a five-second gap between notifications of 3250 this type. When notifications are throttled, 3251 they are dropped, not queued for sending at 3252 a future time. (Note that 'generating' a 3253 notification means sending to all configured 3254 recipients.) 3256 The rptrInfoResetEvent is not sent when the 3257 agent restarts and sends an SNMP coldStart or 3258 warmStart trap. However, it is recommended that 3259 a repeater agent send the rptrInfoOperStatus 3260 object as an optional object with its coldStart 3261 and warmStart trap PDUs." 3262 REFERENCE 3263 "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset 3264 notification." 3266 , 3268 ::= { snmpDot3RptrMgt 0 5 } 3270 -- Conformance information 3272 snmpRptrModConf 3273 OBJECT IDENTIFIER ::= { snmpRptrMod 1 } 3274 snmpRptrModCompls 3275 OBJECT IDENTIFIER ::= { snmpRptrModConf 1 } 3276 snmpRptrModObjGrps 3277 OBJECT IDENTIFIER ::= { snmpRptrModConf 2 } 3278 snmpRptrModNotGrps 3279 OBJECT IDENTIFIER ::= { snmpRptrModConf 3 } 3281 -- Object groups 3283 snmpRptrGrpBasic1516 OBJECT-GROUP 3284 OBJECTS { rptrGroupCapacity, 3285 rptrOperStatus, 3286 rptrHealthText, 3287 rptrReset, 3288 rptrNonDisruptTest, 3289 rptrTotalPartitionedPorts, 3291 rptrGroupIndex, 3292 rptrGroupDescr, 3293 rptrGroupObjectID, 3294 rptrGroupOperStatus, 3295 rptrGroupLastOperStatusChange, 3296 rptrGroupPortCapacity, 3298 rptrPortGroupIndex, 3299 rptrPortIndex, 3300 rptrPortAdminStatus, 3301 rptrPortAutoPartitionState, 3302 rptrPortOperStatus } 3303 STATUS deprecated 3304 DESCRIPTION 3305 "********* THIS GROUP IS DEPRECATED ********** 3307 Basic group from RFCs 1368 and 1516. 3309 NOTE: this object group is DEPRECATED and replaced 3310 with snmpRptrGrpBasic." 3312 , 3314 ::= { snmpRptrModObjGrps 1 } 3316 snmpRptrGrpMonitor1516 OBJECT-GROUP 3317 OBJECTS { rptrMonitorTransmitCollisions, 3319 rptrMonitorGroupIndex, 3320 rptrMonitorGroupTotalFrames, 3321 rptrMonitorGroupTotalOctets, 3322 rptrMonitorGroupTotalErrors, 3324 rptrMonitorPortGroupIndex, 3325 rptrMonitorPortIndex, 3326 rptrMonitorPortReadableFrames, 3327 rptrMonitorPortReadableOctets, 3328 rptrMonitorPortFCSErrors, 3329 rptrMonitorPortAlignmentErrors, 3330 rptrMonitorPortFrameTooLongs, 3331 rptrMonitorPortShortEvents, 3332 rptrMonitorPortRunts, 3333 rptrMonitorPortCollisions, 3334 rptrMonitorPortLateEvents, 3335 rptrMonitorPortVeryLongEvents, 3336 rptrMonitorPortDataRateMismatches, 3337 rptrMonitorPortAutoPartitions, 3338 rptrMonitorPortTotalErrors } 3339 STATUS deprecated 3340 DESCRIPTION 3341 "********* THIS GROUP IS DEPRECATED ********** 3343 Monitor group from RFCs 1368 and 1516. 3345 NOTE: this object group is DEPRECATED and replaced 3346 with snmpRptrGrpMonitor." 3347 ::= { snmpRptrModObjGrps 2 } 3349 snmpRptrGrpAddrTrack1368 OBJECT-GROUP 3350 OBJECTS { rptrAddrTrackGroupIndex, 3351 rptrAddrTrackPortIndex, 3352 rptrAddrTrackLastSourceAddress, 3353 rptrAddrTrackSourceAddrChanges } 3354 STATUS obsolete 3355 DESCRIPTION 3356 "Address tracking group from RFC 1368. 3358 NOTE: this object group is OBSOLETE and replaced 3360 , 3361 with snmpRptrGrpAddrTrack1516." 3362 ::= { snmpRptrModObjGrps 3 } 3364 snmpRptrGrpAddrTrack1516 OBJECT-GROUP 3365 OBJECTS { rptrAddrTrackGroupIndex, 3366 rptrAddrTrackPortIndex, 3367 rptrAddrTrackLastSourceAddress, 3368 rptrAddrTrackSourceAddrChanges, 3369 rptrAddrTrackNewLastSrcAddress } 3370 STATUS deprecated 3371 DESCRIPTION 3372 "********* THIS GROUP IS DEPRECATED ********** 3374 Address tracking group from RFC 1516. 3376 NOTE: this object group is DEPRECATED and 3377 replaced with snmpRptrGrpAddrTrack." 3378 ::= { snmpRptrModObjGrps 4 } 3380 snmpRptrGrpBasic OBJECT-GROUP 3381 OBJECTS { rptrGroupIndex, 3382 rptrGroupObjectID, 3383 rptrGroupOperStatus, 3384 rptrGroupPortCapacity, 3386 rptrPortGroupIndex, 3387 rptrPortIndex, 3388 rptrPortAdminStatus, 3389 rptrPortAutoPartitionState, 3390 rptrPortOperStatus, 3391 rptrPortRptrId, 3393 rptrInfoId, 3394 rptrInfoRptrType, 3395 rptrInfoOperStatus, 3396 rptrInfoReset, 3397 rptrInfoPartitionedPorts, 3398 rptrInfoLastChange } 3399 STATUS current 3400 DESCRIPTION 3401 "Basic group for a system with one or more 3402 repeater-units in multi-segment (post-RFC 1516) 3403 version of the MIB module." 3404 ::= { snmpRptrModObjGrps 5 } 3406 , 3408 snmpRptrGrpMonitor OBJECT-GROUP 3409 OBJECTS { rptrMonitorPortGroupIndex, 3410 rptrMonitorPortIndex, 3411 rptrMonitorPortReadableFrames, 3412 rptrMonitorPortReadableOctets, 3413 rptrMonitorPortFCSErrors, 3414 rptrMonitorPortAlignmentErrors, 3415 rptrMonitorPortFrameTooLongs, 3416 rptrMonitorPortShortEvents, 3417 rptrMonitorPortRunts, 3418 rptrMonitorPortCollisions, 3419 rptrMonitorPortLateEvents, 3420 rptrMonitorPortVeryLongEvents, 3421 rptrMonitorPortDataRateMismatches, 3422 rptrMonitorPortAutoPartitions, 3423 rptrMonitorPortTotalErrors, 3424 rptrMonitorPortLastChange, 3426 rptrMonTxCollisions, 3427 rptrMonTotalFrames, 3428 rptrMonTotalErrors, 3429 rptrMonTotalOctets } 3430 STATUS current 3431 DESCRIPTION 3432 "Monitor group for a system with one or more 3433 repeater-units in multi-segment (post-RFC 1516) 3434 version of the MIB module." 3435 ::= { snmpRptrModObjGrps 6 } 3437 snmpRptrGrpMonitor100 OBJECT-GROUP 3438 OBJECTS { rptrMonitorPortIsolates, 3439 rptrMonitorPortSymbolErrors, 3440 rptrMonitorPortUpper32Octets, 3442 rptrMonUpper32TotalOctets } 3443 STATUS current 3444 DESCRIPTION 3445 "Monitor group for 100Mb/s ports and repeaters 3446 in a system with one or more repeater-units in 3447 multi-segment (post-RFC 1516) version of the MIB 3448 module. Systems which support Counter64 should 3449 also implement snmpRptrGrpMonitor100w64." 3450 ::= { snmpRptrModObjGrps 7 } 3452 snmpRptrGrpMonitor100w64 OBJECT-GROUP 3454 , 3455 OBJECTS { rptrMonitorPortHCReadableOctets, 3456 rptrMonHCTotalOctets } 3457 STATUS current 3458 DESCRIPTION 3459 "Monitor group for 100Mb/s ports and repeaters in a 3460 system with one or more repeater-units and support 3461 for Counter64." 3462 ::= { snmpRptrModObjGrps 8 } 3464 snmpRptrGrpAddrTrack OBJECT-GROUP 3465 OBJECTS { rptrAddrTrackGroupIndex, 3466 rptrAddrTrackPortIndex, 3467 rptrAddrTrackSourceAddrChanges, 3468 rptrAddrTrackNewLastSrcAddress, 3469 rptrAddrTrackCapacity } 3470 STATUS current 3471 DESCRIPTION 3472 "Passive address tracking group for post-RFC 1516 3473 version of the MIB module." 3474 ::= { snmpRptrModObjGrps 9 } 3476 snmpRptrGrpExtAddrTrack OBJECT-GROUP 3477 OBJECTS { rptrExtAddrTrackMacIndex, 3478 rptrExtAddrTrackSourceAddress } 3479 STATUS current 3480 DESCRIPTION 3481 "Extended passive address tracking group for 3482 a system with one or more repeater-units in 3483 post-RFC 1516 version of the MIB module." 3484 ::= { snmpRptrModObjGrps 10 } 3486 snmpRptrGrpRptrAddrSearch OBJECT-GROUP 3487 OBJECTS { rptrAddrSearchLock, 3488 rptrAddrSearchStatus, 3489 rptrAddrSearchAddress, 3490 rptrAddrSearchState, 3491 rptrAddrSearchGroup, 3492 rptrAddrSearchPort, 3493 rptrAddrSearchOwner } 3494 STATUS current 3495 DESCRIPTION 3496 "Active MAC address search group and topology 3497 mapping support for repeaters." 3498 ::= { snmpRptrModObjGrps 11 } 3500 , 3502 snmpRptrGrpTopNPort OBJECT-GROUP 3503 OBJECTS { rptrTopNPortControlIndex, 3504 rptrTopNPortRepeaterId, 3505 rptrTopNPortRateBase, 3506 rptrTopNPortTimeRemaining, 3507 rptrTopNPortDuration, 3508 rptrTopNPortRequestedSize, 3509 rptrTopNPortGrantedSize, 3510 rptrTopNPortStartTime, 3511 rptrTopNPortOwner, 3512 rptrTopNPortRowStatus, 3513 rptrTopNPortIndex, 3514 rptrTopNPortGroupIndex, 3515 rptrTopNPortPortIndex, 3516 rptrTopNPortRate } 3517 STATUS current 3518 DESCRIPTION 3519 "Top `N' group for repeater ports." 3520 ::= { snmpRptrModObjGrps 12 } 3522 -- Compliances 3524 snmpRptrModComplRFC1368 MODULE-COMPLIANCE 3525 STATUS obsolete 3526 DESCRIPTION 3527 "Compliance for RFC 1368. 3529 NOTE: this module compliance is OBSOLETE and 3530 replaced by snmpRptrModComplRFC1516." 3532 MODULE -- this module 3533 MANDATORY-GROUPS { snmpRptrGrpBasic1516 } 3535 GROUP snmpRptrGrpMonitor1516 3536 DESCRIPTION 3537 "Implementation of this optional group is 3538 recommended for systems which have the 3539 instrumentation to do performance monitoring." 3541 GROUP snmpRptrGrpAddrTrack1368 3542 DESCRIPTION 3543 "Implementation of this group is 3544 recommended for systems which have 3545 the necessary instrumentation." 3547 , 3549 ::= { snmpRptrModCompls 1 } 3551 snmpRptrModComplRFC1516 MODULE-COMPLIANCE 3552 STATUS deprecated 3553 DESCRIPTION 3554 "********* THIS COMPLIANCE IS DEPRECATED ********** 3556 Compliance for RFC 1516 and for backwards 3557 compatibility with single-repeater, 3558 10Mb/s-only implementations." 3560 MODULE -- this module 3561 MANDATORY-GROUPS { snmpRptrGrpBasic1516 } 3563 GROUP snmpRptrGrpMonitor1516 3564 DESCRIPTION 3565 "Implementation of this optional group is 3566 recommended for systems which have the 3567 instrumentation to do performance monitoring." 3569 GROUP snmpRptrGrpAddrTrack1516 3570 DESCRIPTION 3571 "Implementation of this group is 3572 recommended for systems which have 3573 the necessary instrumentation." 3575 ::= { snmpRptrModCompls 2 } 3577 snmpRptrModCompl MODULE-COMPLIANCE 3578 STATUS current 3579 DESCRIPTION 3580 "Compliance for the multi-segment version of the 3581 MIB module for a system with one or more 3582 repeater-units." 3584 MODULE -- this module 3585 MANDATORY-GROUPS { snmpRptrGrpBasic, 3586 snmpRptrGrpMonitor, 3587 snmpRptrGrpAddrTrack } 3589 GROUP snmpRptrGrpMonitor100 3590 DESCRIPTION 3591 "Implementation of this group is 3592 mandatory for managed systems which 3593 contain 100Mb/s repeaters." 3595 , 3597 GROUP snmpRptrGrpMonitor100w64 3598 DESCRIPTION 3599 "Implementation of this group is 3600 mandatory for managed systems which 3601 contain 100Mb/s repeaters and which 3602 can support Counter64." 3604 GROUP snmpRptrGrpExtAddrTrack 3605 DESCRIPTION 3606 "Implementation of this group is 3607 recommended for systems which have 3608 the necessary instrumentation to track 3609 MAC addresses of multiple DTEs attached 3610 to a single repeater port." 3612 GROUP snmpRptrGrpRptrAddrSearch 3613 DESCRIPTION 3614 "Implementation of this group is 3615 recommended for systems which allow 3616 read-write access and which have 3617 the necessary instrumentation to 3618 search all incoming data streams 3619 for a particular MAC address." 3621 GROUP snmpRptrGrpTopNPort 3622 DESCRIPTION 3623 "Implementation of this group is 3624 recommended for systems which have 3625 the necessary resources to support 3626 TopN statistics reporting." 3628 ::= { snmpRptrModCompls 3 } 3630 END 3632 , 3633 4. Topology Mapping 3635 The network mapping algorithm presented below takes 3636 information available from network devices such as repeaters, 3637 bridges, and switches, and creates a representation of the 3638 physical topology of the network. 3640 Networking devices connect to the network via one or more 3641 ports. Through these ports, the device is capable of hearing 3642 network packets sent by other devices. By looking the source 3643 address in the packet, and identifying which port the packet 3644 was heard on, the device can provide information to a Network 3645 Management System about the location of an address in the 3646 network, relative to that device. 3648 For devices such as bridges and switches, the association of 3649 address to port can be retrieved via the forwarding data base 3650 part of the Bridge MIB. For repeaters, the 3651 rptrAddrSearchTable may be used to perform the association. 3653 Given this information, it would be possible for the NMS to 3654 create a topology of the network which represents the physical 3655 relationships of the devices in the networks. The following 3656 is an example of how this might be done: 3658 Assume the network: 3660 ============================= 3661 | | | 3662 | | | 3663 d1 d4 d7 3664 / \ | 3665 / \ | 3666 d2 d3 d5 3667 | 3668 | 3669 d6 3671 The discovery process would first determine the existence of 3672 the network devices and nodes in the network. In the above 3673 example, the network devices discovered would be: 3675 d1,d2,d3,d4,d5,d6,d7 3677 , 3679 From this list of discovered devices, select (arbitrarily or 3680 via some heuristic) a device as the starting point. From that 3681 device, determine where all other devices are located in the 3682 network with respect to the selected device. 3684 For example, if d1 is the selected device, the network in 3685 relation to d1 would look like: 3687 d1 3688 / | \ 3689 / | \ 3690 d2 d3 d4,d5,d6,d7 3692 So d1 sees d2 on one port, d3 on another port, and d4, d5, and 3693 d6 on the third port. In other words, using the 3694 rptrAddrSearchTable (if d1 is a repeater) or the Forwarding 3695 Database (if it is a bridge or a switch), d1 has located d2 on 3696 one port, d1 has located d3 on another port, and finally, d1 3697 has located d4, d5, d6, and d7 on yet another port. 3699 After the first step of the algorithm is accomplished, the 3700 next and final step is a recursive one. Go to each of these 3701 temporary 'segments' (e.g., the segment connecting d1 and d2, 3702 or the segment connecting d1 and d3, or the segment connecting 3703 d1, d4, d5, d6, and d7) and determine which of these devices 3704 really belongs in that segment. 3706 As new segments are created due to this process, the recursive 3707 algorithm visits them, and performs the exact same process. 3709 In the example, the segments connecting d1 and d2, and 3710 connecting d1 and d3, require no further scrutiny, since there 3711 are only two nodes in those segments. However, the segment 3712 connecting d1, d4, d5, d6, and d7 may prove to be one or more 3713 segments, so we will investigate it. 3715 The purpose of this step is to determine which devices are 3716 really connected to this segment, and which are actually 3717 connected downstream. This is done by giving each of the 3718 child devices in the segment (d4, d5, d6, and d7) a chance to 3719 eliminate each of the others from the segment. 3721 A device eliminates another device by showing that it hears 3722 the parent device (in this case, d1) on one port, and the 3723 other device on another port (different from the port on which 3725 , 3726 it heard the parent). If this is true, then it must mean that 3727 that device is _between_ the parent device and the device 3728 which is being eliminated. 3730 In the example, we can see that device d4 can eliminate both 3731 d5 and d6, , but nobody can eliminate d4 and d7, because 3732 everybody hears them on the same port that they hear the 3733 parent device (d1). So the resulting topology looks like: 3735 d1 3736 / | \ 3737 / | \ 3738 d2 d3 d4,d7 3739 | 3740 | 3741 d5,d6 3743 Next the algorithm visits the next segment, which is the one 3744 connecting d4, d5, and d6. Using the process stated above, d5 3745 can eliminate d6, since it hears d4 on a different port from 3746 where it hears d6. Finally, the topology looks like: 3748 d1 3749 / | \ 3750 / | \ 3751 d2 d3 d4,d7 3752 | 3753 | 3754 d5 3755 | 3756 | 3757 d6 3759 This is actually the topology shown at the beginning of the 3760 description. 3762 With this information about how the network devices are 3763 connected, it is a relatively simple extension to then place 3764 nodes such as workstations and PCs in the network. This can 3765 be done by placing the node into a segment, then allowing the 3766 network devices to show that the node is really not part of 3767 that segment. 3769 This elimination can be done because the devices know what 3770 port connects them to the segment on which the node is 3772 , 3773 temporarily placed. If they actually hear the node on a 3774 different port than that which connects the device to the 3775 segment, then the node must be downstream, and so it is moved 3776 onto the downstream segment. Then that segment is evaluated, 3777 and so forth. Eventually, no device can show that the node is 3778 connected downstream, and so it must be attached to that 3779 segment. 3781 For example, assume the network: 3783 ============================= 3784 | | | 3785 | | | 3786 d1 d4 d7 3787 / \ | 3788 / \ | 3789 d2 d3 d5 3790 | | 3791 | | 3792 e1 d6 3794 In this network, we are trying to place e1 where it belongs. 3795 We begin by placing it arbitrarily into a segment: 3797 ================================== 3798 | | | | 3799 | | | | 3800 e1 d1 d4 d7 3801 / \ | 3802 / \ | 3803 d2 d3 d5 3804 | 3805 | 3806 d6 3808 In the above case, we would give d1, d4, and d7 a chance to 3809 show that e1 is not really on that segment. d4 and d7 hear e1 3810 on the same port which connects them to that segment, so they 3811 cannot eliminate e1 from the segment. However, d1 will hear 3812 e1 on a different port, so we move e1 down onto the segment 3813 which is connected by that port. This yields the following: 3815 , 3816 ============================= 3817 | | | 3818 | | | 3819 d1 d4 d7 3820 / \ | 3821 / \ | 3822 d2 d3,e1 d5 3823 | 3824 | 3825 d6 3827 Now we give everyone in that segment (besides that parent 3828 device, d1) a chance to eliminate e1. Only d3 can try, and it 3829 succeeds, so we place e1 on segment which is connected by the 3830 port on which d3 heard e1. There is no segment there (yet), 3831 so we create one, and end up with the following: 3833 ============================= 3834 | | | 3835 | | | 3836 d1 d4 d7 3837 / \ | 3838 / \ | 3839 d2 d3 d5 3840 | | 3841 | | 3842 e1 d6 3844 which is the correct position. 3846 , 3847 5. Acknowledgements 3849 This document was produced by the IETF Hub MIB Working Group, 3850 whose efforts were greatly advanced by the contributions of 3851 the following people: 3853 Chuck Black 3854 John Flick 3855 Jeff Johnson 3856 Leon Leong 3857 Mike Lui 3858 Dave Perkins 3859 Geoff Thompson 3860 Maurice Turcotte 3861 Paul Woodruff 3863 , 3865 6. References 3867 [1] IEEE 802.3/ISO 8802-3 Information processing systems - 3868 Local area networks - Part 3: Carrier sense multiple 3869 access with collision detection (CSMA/CD) access method 3870 and physical layer specifications, 1993. 3872 [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium 3873 Attachment Units and Repeater for 100 Mb/s Operation, 3874 Type 100BASE-T," Sections 21 through 29, Supplement to 3875 IEEE Std 802.3, October 26, 1995. 3877 [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, 3878 Supplement to IEEE Std 802.3, October 26, 1995. 3880 [4] de Graaf, K., D. Romascanu, D. McMaster, K. McCloghrie, 3881 and S. Roberts, "Definitions of Managed Objects for IEEE 3882 802.3 Medium Attachment Units (MAUs)", Internet Draft, 3883 August 1996. 3885 [5] McCloghrie, K., and M. Rose, Editors, "Management 3886 Information Base for Network Management of TCP/IP-based 3887 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 3888 Performance Systems International, March 1991. 3890 [6] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, 3891 and S. Waldbusser, "Structure of Management Information 3892 for version 2 of the Simple Network Management Protocol 3893 (SNMPv2)", RFC 1902, January 1996. 3895 [7] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, 3896 and S. Waldbusser, "Textual Conventions for version 2 of 3897 the Simple Network Management Protocol (SNMPv2)", RFC 3898 1903, January 1996. 3900 [8] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, 3901 and S. Waldbusser, "Conformance Statements for version 2 3902 of the Simple Network Management Protocol (SNMPv2)", RFC 3903 1904, January 1996. 3905 [9] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, 3906 and S. Waldbusser, "Protocol Operations for version 2 of 3907 the Simple Network Management Protocol (SNMPv2)", RFC 3908 1905, January 1996. 3910 , 3912 [10] Case, J., M. Fedor, M. Schoffstall, and J. Davin, "Simple 3913 Network Management Protocol", RFC 1157, SNMP Research, 3914 Performance Systems International, MIT Laboratory for 3915 Computer Science, May 1990. 3917 [11] McMaster, D., and K. McCloghrie, "Definitions of Managed 3918 Objects for IEEE 802.3 Repeater Devices", RFC 1516, 3919 September 1993. 3921 [12] McAnally, G., D. Gilbert, and J. Flick, "Conditional 3922 Grant of Rights to Specific Hewlett-Packard Patents In 3923 Conjunction With the Internet Engineering Task Force's 3924 Internet-Standard Network Management Framework", Internet 3925 Draft, May 1996. 3927 [13] Hewlett-Packard Company, US Patents 5,293,635 and 3928 5,421,024. 3930 [14] McCloghrie, K., and F. Kastenholz, "Evolution of the 3931 Interfaces Group of MIB-II", RFC 1573, January 1994. 3933 , 3935 7. Security Considerations 3937 Security issues are not discussed in this memo. 3939 8. Authors' Addresses 3941 Kathryn de Graaf 3942 3Com Corporation 3943 118 Turnpike Rd. 3944 Southborough, MA 01772 USA 3945 Tel: (508)229-1627 3946 Fax: (508)490-5882 3947 E-mail: kdegraaf@isd.3com.com 3949 Dan Romascanu 3950 Madge Networks (Israel) Ltd. 3951 Atidim Technology Park, Bldg. 3 3952 Tel Aviv 61131, Israel 3953 Tel: 972-3-6458414, 6458458 3954 Fax: 972-3-6487146 3955 E-mail: dromasca@madge.com 3957 Donna McMaster 3958 Coloma Communications 3959 Tel: (916) 642-2402 3960 E-Mail: donna@coloma.com 3962 Keith McCloghrie 3963 Cisco Systems Inc. 3964 170 West Tasman Drive 3965 San Jose, CA 95134 3966 Tel: (408) 526-5260 3967 E-Mail: kzm@cisco.com 3969 , 3971 Table of Contents 3973 1 The SNMP Network Management Framework ................. 2 3974 1.1 Object Definitions .................................. 3 3975 2 Overview .............................................. 4 3976 2.1 Relationship to RFC 1516 ............................ 4 3977 2.2 Repeater Management ................................. 4 3978 2.3 Structure of the MIB ................................ 5 3979 2.3.1 Basic Definitions ................................. 5 3980 2.3.2 Monitor Definitions ............................... 5 3981 2.3.3 Address Tracking Definitions ...................... 5 3982 2.3.4 Top N Definitions ................................. 6 3983 2.4 Relationship to Other MIBs .......................... 6 3984 2.4.1 Relationship to MIB-II ............................ 6 3985 2.4.1.1 Relationship to the 'system' group .............. 6 3986 2.4.1.2 Relationship to the 'interfaces' group .......... 6 3987 3 Definitions ........................................... 8 3988 4 Topology Mapping ...................................... 81 3989 5 Acknowledgements ...................................... 86 3990 6 References ............................................ 87 3991 7 Security Considerations ............................... 89 3992 8 Authors' Addresses .................................... 89