idnits 2.17.1 draft-ietf-hubmib-repeater-dev-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) 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. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an 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. ** 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 84 instances of too long lines in the document, the longest one being 6 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [5], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1612 has weird spacing: '... of the parti...' == Line 2231 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 (27 November 1995) is 10377 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 3065 looks like a reference -- Missing reference section? '2' on line 3070 looks like a reference -- Missing reference section? '3' on line 3075 looks like a reference -- Missing reference section? '5' on line 3082 looks like a reference -- Missing reference section? '4' on line 3078 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft 802.3 Repeater MIB 27 November 1995 3 Definitions of Managed Objects 4 for IEEE 802.3 Repeater Devices 6 8 27 November 1995 10 Dan Romascanu 11 LANNET Data Communications, Ltd. 12 dan@lannet.com 14 Kathryn de Graaf 15 3Com Corporation 16 kdegraaf@chipcom.com 18 Status of this Memo 20 This document is an Internet-Draft. Internet-Drafts are 21 working documents of the Internet Engineering Task Force 22 (IETF), its areas, and its working groups. Note that other 23 groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet- 29 Drafts as reference material or to cite them other than as a 30 "work in progress". 32 To learn the current status of any Internet-Draft, please 33 check the "1id-abstracts.txt" listing contained in the 34 Internet- Drafts Shadow Directories on ds.internic.net (US 35 East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West 36 Coast), or munnari.oz.au (Pacific Rim). 38 Abstract 40 This memo defines an experimental portion of the Management 41 Information Base (MIB) for use with network management 42 protocols in the Internet community. In particular, it 43 defines objects for managing IEEE 802.3 10 and 100 Mb/second 44 baseband repeaters based on IEEE Std 802.3 Section 30, "10 & 45 100 Mb/s Management," October 26, 1995. 47 This memo does not specify a standard for the Internet 48 community. 50 1. The SNMPv2 Network Management Framework 52 The SNMPv2 Network Management Framework consists of four major 53 components. They are: 55 o RFC 1442 which defines the SMI, the mechanisms used for 56 describing and naming objects for the purpose of 57 management. 59 o STD 17, RFC 1213 defines MIB-II, the core set of managed 60 objects for the Internet suite of protocols. 62 o RFC 1445 which defines the administrative and other 63 architectural aspects of the framework. 65 o RFC 1448 which defines the protocol used for network 66 access to managed objects. 68 The Framework permits new objects to be defined for the 69 purpose of experimentation and evaluation. 71 1.1. Object Definitions 73 Managed objects are accessed via a virtual information store, 74 termed the Management Information Base or MIB. Objects in the 75 MIB are defined using the subset of Abstract Syntax Notation 76 One (ASN.1) defined in the SMI. In particular, each object 77 type is named by an OBJECT IDENTIFIER, an administratively 78 assigned name. The object type together with an object 79 instance serves to uniquely identify a specific instantiation 80 of the object. For human convenience, we often use a textual 81 string, termed the descriptor, to refer to the object type. 83 2. Overview 85 Instances of the object types defined in this memo represent 86 attributes of an IEEE 802.3 (Ethernet-like) repeater, as 87 defined by Section 9, "Repeater Unit for 10 Mb/s Baseband 88 Networks" in the IEEE 802.3/ISO 8802-3 CSMA/CD standard [1], 89 and Section 27, "Repeater for 100 Mb/s Baseband Networks" in 90 the IEEE Standard 802.3u-1995 [2]. 92 These Repeater MIB objects may be used to manage non-standard 93 repeater-like devices, but defining objects to describe 94 implementation-specific properties of non-standard repeater- 95 like devices is outside the scope of this memo. 97 The definitions presented here are based on Section 30.4, 98 "Layer Management for 10 and 100 Mb/s Baseband Repeaters" and 99 Annex 30A, "GDMO Specificataions for 802.3 managed objects" of 100 [3]. 102 Implementors of these MIB objects should note that [3] 103 explicitly describes when, where, and how various repeater 104 attributes are measured. The IEEE document also describes the 105 effects of repeater actions that may be invoked by 106 manipulating instances of the MIB objects defined here. 108 The counters in this document are defined to be the same as 109 those counters in [3], with the intention that the same 110 instrumentation can be used to implement both the IEEE and 111 IETF management standards. 113 2.1. Structure of the MIB 115 Objects in this MIB are arranged into MIB groups. Each MIB 116 group is organized as a set of related objects. 118 2.1.1. The Basic Group Definitions 120 This group contains the objects which are applicable to all 121 repeaters. It contains status, parameter and control objects 122 for each repeater within the managed system, for the port 123 groups within the system, and for the individual ports 124 themselves. 126 2.1.2. The Monitor Group Definitions 128 This group contains monitoring statistics for each repeater 129 within the system and for individual ports. 131 2.1.3. The Address Tracking Group Definitions 133 This group contains objects for tracking the MAC addresses of 134 the DTEs attached to the ports within the system. 136 2.1.4. The Top N Group Definitions 138 This group contains objects for tracking the ports with the 139 most activity within the system or within particular 140 repeaters. 142 2.2. Relationship to Other MIBs 144 2.2.1. Relationship to RFC 1516 146 This MIB is intended as a superset of that defined by RFC 147 1516, which will go to historic status. This MIB includes all 148 of the objects contained in that MIB, plus some additional 149 ones, mainly for support for multiple repeaters and for 150 100BASE-T management. Certain objects have been deprecated; 151 in particular, those scalar objects used for managing a single 152 repeater are now of minimal use since they are duplicated in 153 the rptrInfoTable and rptrMonitorTable definitions. 155 2.2.2. Relationship to MIB-II It is assumed that a repeater 156 implementing this MIB will also implement (at least) the 157 'system' group defined in MIB-II [5]. 159 2.2.2.1. Relationship to the 'system' group 161 In MIB-II, the 'system' group is defined as being mandatory 162 for all systems such that each managed entity contains one 163 instance of each object in the 'system' group. Thus, those 164 objects apply to the entity even if the entity's sole 165 functionality is management of repeaters. 167 2.2.2.2. Relationship to the 'interfaces' group 169 In MIB-II, the 'interfaces' group is defined as being 170 mandatory for all systems and contains information on an 171 entity's interfaces, where each interface is thought of as 172 being attached to a 'subnetwork'. (Note that this term is not 173 to be confused with 'subnet' which refers to an addressing 174 partitioning scheme used in the Internet suite of protocols.) 176 This Repeater MIB uses the notion of ports on a repeater. The 177 concept of a MIB-II interface has NO specific relationship to 178 a repeater's port. Therefore, the 'interfaces' group applies 179 only to the one (or more) network interfaces on which the 180 entity managing the repeater sends and receives management 181 protocol operations, and does not apply to the repeater's 182 ports. 184 This is consistent with the physical-layer nature of a 185 repeater. A repeater is a bitwise store-and-forward device. 186 It recognizes activity and bits, but does not process incoming 187 data based on any packet-related information (such as checksum 188 or addresses). A repeater has no MAC address, no MAC 189 implementation, and does not pass packets up to higher-level 190 protocol entities for processing. 192 (When a network management entity is observing a repeater, it 193 may appear as though the repeater is passing packets to a 194 higher-level protocol entity. However, this is only a means 195 of implementing management, and this passing of management 196 information is not part of the repeater functionality.) 197 3. Definitions 199 SNMP-REPEATER-MIB DEFINITIONS ::= BEGIN 201 IMPORTS 202 experimental, Counter32, Integer32, Gauge32, OBJECT-TYPE, 203 MODULE-IDENTITY, NOTIFICATION-TYPE 204 FROM SNMPv2-SMI 205 TimeStamp, DisplayString, MacAddress, TEXTUAL-CONVENTION, 206 RowStatus 207 FROM SNMPv2-TC 208 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP, 209 FROM SNMPv2-CONF 210 OwnerString 211 FROM RMON-MIB 212 mib-2 213 FROM RFC1213-MIB; 215 snmpRptrMod MODULE-IDENTITY 216 LAST-UPDATED "9511270000Z" 217 ORGANIZATION "IETF HUB MIB Working Group" 218 CONTACT-INFO 219 "WG E-mail: hubmib@baynetworks.com 221 Chair: Dan Romascanu 222 Postal: LANNET Data Communications, Ltd. 223 Atidim Technology Park, Bldg. 3 224 Tel Aviv 61131, Israel 225 Tel: 972-3-6458414, 6458458 226 Fax: 972-3-6487146 227 E-mail: dan@lannet.com 229 Editor: Kathryn de Graaf 230 Postal: 3Com Corporation 231 118 Turnpike Rd. 232 Southborough, MA 01772 233 USA 234 Tel: (508)229-1627 235 Fax: (508)490-5882 236 E-mail: kdegraaf@chipcom.com" 237 DESCRIPTION 238 "Management information for 802.3 repeaters. 240 The following references are used throughout 241 this MIB module: 243 [IEEE 802.3 Std] 244 refers to IEEE 802.3/ISO 8802-3 Information 245 processing systems - Local area networks - 246 Part 3: Carrier sense multiple access with 247 collision detection (CSMA/CD) access method 248 and physical layer specifications (1993). 250 [IEEE 802.3 Mgt] 251 refers to IEEE 802.3u-1995, '10 Mb/s & 252 100 Mb/s Management, Section 30,' 253 Supplement to ANSI/IEEE 802.3. 255 The following terms are used throughout this 256 MIB module: 258 System - 260 Chassis - 262 Repeater-unit - 264 Trivial repeater-unit - an isolated port that can 265 gather statistics. 267 Group - 269 System interconnect segment - 271 Stack - 273 Unit - 275 Module - 276 " 277 REVISION "9309010000Z" 278 DESCRIPTION 279 "Published as RFC 1516" 280 REVISION "9210010000Z" 281 DESCRIPTION 282 "Published as RFC 1368" 283 ::= { snmpDot3RptrMgt x } 285 snmpDot3RptrMgt OBJECT IDENTIFIER ::= { experimental x } 287 OptMacAddr ::= TEXTUAL-CONVENTION 288 DISPLAY-HINT "1x:" 289 STATUS current 290 DESCRIPTION 291 "Either a 6 octet address in the `canonical' 292 order defined by IEEE 802.1a, i.e., as if it 293 were transmitted least significant bit first 294 if a value is available or a zero length string." 295 REFERENCE 296 "See MacAddress in SNMPv2-TC. The only difference 297 is that a zero length string is allowed as a value 298 for OptMacAddr and not for MacAddress." 299 SYNTAX OCTET STRING (SIZE (0 | 6)) 301 -- Basic information at the repeater, group, and port level. 303 rptrBasicPackage 304 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 1 } 305 rptrRptrInfo 306 OBJECT IDENTIFIER ::= { rptrBasicPackage 1 } 307 rptrGroupInfo 308 OBJECT IDENTIFIER ::= { rptrBasicPackage 2 } 309 rptrPortInfo 310 OBJECT IDENTIFIER ::= { rptrBasicPackage 3 } 311 rptrAllRptrInfo 312 OBJECT IDENTIFIER ::= { rptrBasicPackage 4 } 314 -- Monitoring information at the repeater, group, and port level. 315 rptrMonitorPackage 316 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 2 } 317 rptrMonitorRptrInfo 318 OBJECT IDENTIFIER ::= { rptrMonitorPackage 1 } 319 rptrMonitorGroupInfo 320 OBJECT IDENTIFIER ::= { rptrMonitorPackage 2 } 321 rptrMonitorPortInfo 322 OBJECT IDENTIFIER ::= { rptrMonitorPackage 3 } 323 rptrMonitorAllRptrInfo 324 OBJECT IDENTIFIER ::= { rptrMonitorPackage 4 } 326 -- Address tracking information at the repeater, group, 327 -- and port level. 328 rptrAddrTrackPackage 329 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 3 } 330 rptrAddrTrackRptrInfo 331 -- this subtree is currently unused 332 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 1 } 333 rptrAddrTrackGroupInfo 334 -- this subtree is currently unused 335 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 2 } 336 rptrAddrTrackPortInfo 337 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 3 } 339 -- TopN information. 340 rptrTopNPackage 341 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 4 } 342 rptrTopNRptrInfo 343 -- this subtree is currently unused 344 OBJECT IDENTIFIER ::= { rptrTopNPackage 1 } 345 rptrTopNGroupInfo 346 -- this subtree is currently unused 347 OBJECT IDENTIFIER ::= { rptrTopNPackage 2 } 348 rptrTopNPortInfo 349 OBJECT IDENTIFIER ::= { rptrTopNPackage 3 } 351 -- Old version of basic information at the repeater level. 352 -- 353 -- In a system containing a single managed repeater, 354 -- configuration, status, and control objects for the overall 355 -- repeater. 356 -- 357 -- The objects contained under the rptrRptrInfo subtree are 358 -- intended for backwards compatibility with implementations of 359 -- RFC 1516. In newer implementations (both single- and 360 -- multiple-repeater implementations) the rptrInfoTable should 361 -- be implemented. It is the preferred source of this information, 362 -- as it contains the values for all repeaters managed by the 363 -- agent. In all cases, the objects in the rptrRptrInfo subtree 364 -- are duplicates of the corresponding objects in the first entry 365 -- of the rptrInfoTable. 367 rptrGroupCapacity OBJECT-TYPE 368 SYNTAX Integer32 (1..2147483647) 369 MAX-ACCESS read-only 370 STATUS deprecated 371 DESCRIPTION 372 "The rptrGroupCapacity is the number of groups 373 that can be contained within the repeater. Within 374 each managed repeater, the groups are uniquely 375 numbered in the range from 1 to rptrGroupCapacity. 377 Some groups may not be present in the repeater, in 378 which case the actual number of groups present 379 will be less than rptrGroupCapacity. The number 380 of groups present will never be greater than 381 rptrGroupCapacity. 383 Note: In practice, this will generally be the 384 number of field-replaceable units (i.e., modules, 385 cards, or boards) that can fit in the physical 386 repeater enclosure, and the group numbers will 387 correspond to numbers marked on the physical 388 enclosure." 389 REFERENCE 390 "[IEEE 802.3 Mgt], 30.4.1.1.3, 391 aRepeaterGroupCapacity." 392 ::= { rptrRptrInfo 1 } 394 rptrOperStatus OBJECT-TYPE 395 SYNTAX INTEGER { 396 other(1), -- undefined or unknown 397 ok(2), -- no known failures 398 rptrFailure(3), -- repeater-related failure 399 groupFailure(4), -- group-related failure 400 portFailure(5), -- port-related failure 401 generalFailure(6) -- failure, unspecified type 402 } 403 MAX-ACCESS read-only 404 STATUS deprecated 405 DESCRIPTION 406 "The rptrOperStatus object indicates the 407 operational state of the repeater. The 408 rptrHealthText object may be consulted for more 409 specific information about the state of the 410 repeater's health. 412 In the case of multiple kinds of failures (e.g., 413 repeater failure and port failure), the value of 414 this attribute shall reflect the highest priority 415 failure in the following order, listed highest 416 priority first: 418 rptrFailure(3) 419 groupFailure(4) 420 portFailure(5) 421 generalFailure(6)." 422 REFERENCE 423 "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState." 424 ::= { rptrRptrInfo 2 } 426 rptrHealthText OBJECT-TYPE 427 SYNTAX DisplayString (SIZE (0..255)) 428 MAX-ACCESS read-only 429 STATUS deprecated 430 DESCRIPTION 431 "The health text object is a text string that 432 provides information relevant to the operational 433 state of the repeater. Agents may use this string 434 to provide detailed information on current 435 failures, including how they were detected, and/or 436 instructions for problem resolution. The contents 437 are agent-specific." 438 REFERENCE 439 "[IEEE 802.3 Mgt], 30.4.1.1.6, aRepeaterHealthText." 440 ::= { rptrRptrInfo 3 } 442 rptrReset OBJECT-TYPE 443 SYNTAX INTEGER { 444 noReset(1), 445 reset(2) 446 } 447 MAX-ACCESS read-write 448 STATUS deprecated 449 DESCRIPTION 450 "Setting this object to reset(2) causes a 451 transition to the START state of Fig 9-2 in 452 section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, 453 and the START state of Fig 27-2 in section 27 454 of that standard for a 100Mb/s repeater. 456 Setting this object to noReset(1) has no effect. 457 The agent will always return the value noReset(1) 458 when this object is read. 460 After receiving a request to set this variable to 461 reset(2), the agent is allowed to delay the reset 462 for a short period. For example, the implementor 463 may choose to delay the reset long enough to allow 464 the SNMP response to be transmitted. In any 465 event, the SNMP response must be transmitted. 467 This action does not reset the management counters 468 defined in this document nor does it affect the 469 portAdminStatus parameters. Included in this 470 action is the execution of a disruptive Self-Test 471 with the following characteristics: a) The nature 472 of the tests is not specified. b) The test resets 473 the repeater but without affecting management 474 information about the repeater. c) The test does 475 not inject packets onto any segment. d) Packets 476 received during the test may or may not be 477 transferred. e) The test does not interfere with 478 management functions. 480 After performing this self-test, the agent will 481 update the repeater health information (including 482 rptrOperStatus and rptrHealthText), and send a 483 rptrHealth trap." 484 REFERENCE 485 "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." 486 ::= { rptrRptrInfo 4 } 488 rptrNonDisruptTest OBJECT-TYPE 489 SYNTAX INTEGER { 490 noSelfTest(1), 491 selfTest(2) 492 } 493 MAX-ACCESS read-write 494 STATUS deprecated 495 DESCRIPTION 496 "Setting this object to selfTest(2) causes the 497 repeater to perform a agent-specific, non- 498 disruptive self-test that has the following 499 characteristics: a) The nature of the tests is 500 not specified. b) The test does not change the 501 state of the repeater or management information 502 about the repeater. c) The test does not inject 503 packets onto any segment. d) The test does not 504 prevent the relay of any packets. e) The test 505 does not interfere with management functions. 507 After performing this test, the agent will update 508 the repeater health information (including 509 rptrOperStatus and rptrHealthText) and send a 510 rptrHealth trap. 512 Note that this definition allows returning an 513 'okay' result after doing a trivial test. 515 Setting this object to noSelfTest(1) has no 516 effect. The agent will always return the value 517 noSelfTest(1) when this object is read." 518 REFERENCE 519 "[IEEE 802.3 Mgt], 30.4.1.2.2, 520 acExecuteNonDisruptiveSelfTest." 521 ::= { rptrRptrInfo 5 } 523 rptrTotalPartitionedPorts OBJECT-TYPE 524 SYNTAX Gauge32 525 MAX-ACCESS read-only 526 STATUS deprecated 527 DESCRIPTION 528 "This object returns the total number of ports in 529 the repeater whose current state meets all three 530 of the following criteria: rptrPortOperStatus 531 does not have the value notPresent(3), 532 rptrPortAdminStatus is enabled(1), and 533 rptrPortAutoPartitionState is autoPartitioned(2)." 534 ::= { rptrRptrInfo 6 } 536 -- Basic information at the group level. 537 -- 538 -- Configuration and status objects for each 539 -- managed group in the system, independent 540 -- of whether there is one or more managed 541 -- repeater-units in the system. 543 rptrGroupTable OBJECT-TYPE 544 SYNTAX SEQUENCE OF RptrGroupEntry 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 "Table of descriptive and status information about 549 the groups of ports." 551 ::= { rptrGroupInfo 1 } 553 rptrGroupEntry OBJECT-TYPE 554 SYNTAX RptrGroupEntry 555 MAX-ACCESS not-accessible 556 STATUS current 557 DESCRIPTION 558 "An entry in the table, containing information 559 about a single group of ports." 560 INDEX { rptrGroupIndex } 561 ::= { rptrGroupTable 1 } 563 RptrGroupEntry ::= 564 SEQUENCE { 565 rptrGroupIndex 566 Integer32, 567 rptrGroupDescr 568 DisplayString, 569 rptrGroupObjectID 570 OBJECT IDENTIFIER, 571 rptrGroupOperStatus 572 INTEGER, 573 rptrGroupLastOperStatusChange 574 TimeTicks, 575 rptrGroupPortCapacity 576 Integer32 577 } 579 rptrGroupIndex OBJECT-TYPE 580 SYNTAX Integer32 (1..2147483647) 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "This object identifies the group within the 585 system for which this entry contains 586 information." 587 REFERENCE 588 "[IEEE 802.3 Mgt], 30.4.2.1.1, aGroupID." 589 ::= { rptrGroupEntry 1 } 591 rptrGroupDescr OBJECT-TYPE 592 SYNTAX DisplayString (SIZE (0..255)) 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "A textual description of the group. This value 597 should include the full name and version 598 identification of the group's hardware type and 599 indicate how the group is differentiated from 600 other types of groups in the repeater. Plug-in 601 Module, Rev A' or 'Barney Rubble 10BASE-T 4-port 602 SIMM socket Version 2.1' are examples of valid 603 group descriptions. 605 It is mandatory that this only contain printable 606 ASCII characters." 607 ::= { rptrGroupEntry 2 } 609 rptrGroupObjectID OBJECT-TYPE 610 SYNTAX OBJECT IDENTIFIER 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "The vendor's authoritative identification of the 615 group. This value may be allocated within the SMI 616 enterprises subtree (1.3.6.1.4.1) and provides a 617 straight-forward and unambiguous means for 618 determining what kind of group is being managed. 620 For example, this object could take the value 621 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, 622 Inc.' was assigned the subtree 1.3.6.1.4.1.4242, 623 and had assigned the identifier 624 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 625 6-Port FOIRL Plug-in Module.'" 626 ::= { rptrGroupEntry 3 } 628 rptrGroupOperStatus OBJECT-TYPE 629 SYNTAX INTEGER { 630 other(1), 631 operational(2), 632 malfunctioning(3), 633 notPresent(4), 634 underTest(5), 635 resetInProgress(6) 636 } 637 MAX-ACCESS read-only 638 STATUS current 639 DESCRIPTION 640 "An object that indicates the operational status 641 of the group. 643 A status of notPresent(4) indicates that the group 644 is temporarily or permanently physically and/or 645 logically not a part of the repeater. It is an 646 implementation-specific matter as to whether the 647 agent effectively removes notPresent entries from 648 the table. 650 A status of operational(2) indicates that the 651 group is functioning, and a status of 652 malfunctioning(3) indicates that the group is 653 malfunctioning in some way." 654 ::= { rptrGroupEntry 4 } 656 rptrGroupLastOperStatusChange OBJECT-TYPE 657 SYNTAX TimeTicks 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 "An object that contains the value of sysUpTime at 662 the time when the last of the following occurred: 663 1) the agent cold- or warm-started; 664 2) the row for the group was created (such 665 as when the group was added to the system); or 666 3) the value of rptrGroupOperStatus for the 667 group changed. 669 A value of zero indicates that the group's 670 operational status has not changed since the agent 671 last restarted." 672 ::= { rptrGroupEntry 5 } 674 rptrGroupPortCapacity OBJECT-TYPE 675 SYNTAX Integer32 (1..2147483647) 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The rptrGroupPortCapacity is the number of ports 680 that can be contained within the group. Valid 681 range is 1-2147483647. Within each group, the 682 ports are uniquely numbered in the range from 1 to 683 rptrGroupPortCapacity. 685 Some ports may not be present in the system, in 686 which case the actual number of ports present 687 will be less than the value of rptrGroupPortCapacity. 688 The number of ports present in the group will never 689 be greater than the value of rptrGroupPortCapacity. 691 Note: In practice, this will generally be the 692 number of ports on a module, card, or board, and 693 the port numbers will correspond to numbers marked 694 on the physical embodiment." 695 REFERENCE 696 "IEEE 802.3 Mgt, 30.4.2.1.2, aGroupPortCapacity." 697 ::= { rptrGroupEntry 6 } 699 -- Basic information at the port level. 700 -- 701 -- Configuration and status objects for 702 -- each managed repeater port in the system, 703 -- independent of whether there is one or more 704 -- managed repeater-units in the system. 706 rptrPortTable OBJECT-TYPE 707 SYNTAX SEQUENCE OF RptrPortEntry 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "Table of descriptive and status information about 712 the repeater ports in the system. The number of 713 entries is independent of the number of repeaters 714 in the managed system." 715 ::= { rptrPortInfo 1 } 717 rptrPortEntry OBJECT-TYPE 718 SYNTAX RptrPortEntry 719 MAX-ACCESS not-accessible 720 STATUS current 721 DESCRIPTION 722 "An entry in the table, containing information 723 about a single port." 724 INDEX { rptrPortGroupIndex, rptrPortIndex } 725 ::= { rptrPortTable 1 } 727 RptrPortEntry ::= 728 SEQUENCE { 729 rptrPortGroupIndex 730 Integer32, 731 rptrPortIndex 732 Integer32, 733 rptrPortAdminStatus 734 INTEGER, 735 rptrPortAutoPartitionState 736 INTEGER, 737 rptrPortOperStatus 738 INTEGER, 739 rptrPortRptrId 740 Integer32 741 } 743 rptrPortGroupIndex OBJECT-TYPE 744 SYNTAX Integer32 (1..2147483647) 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "This object identifies the group containing the 749 port for which this entry contains information." 750 ::= { rptrPortEntry 1 } 752 rptrPortIndex OBJECT-TYPE 753 SYNTAX Integer32 (1..2147483647) 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "This object identifies the port within the group 758 for which this entry contains information. This 759 identifies the port independently from the repeater 760 it may be attached to. The numbering scheme for 761 ports is implementation specific; however, this 762 value can never be greater than 763 rptrGroupPortCapacity for the associated group." 764 REFERENCE 765 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." 766 ::= { rptrPortEntry 2 } 768 rptrPortAdminStatus OBJECT-TYPE 769 SYNTAX INTEGER { 770 enabled(1), 771 disabled(2) 772 } 773 MAX-ACCESS read-write 774 STATUS current 775 DESCRIPTION 776 "Setting this object to disabled(2) disables the 777 port. A disabled port neither transmits nor 778 receives. Once disabled, a port must be 779 explicitly enabled to restore operation. A port 780 which is disabled when power is lost or when a 781 reset is exerted shall remain disabled when normal 782 operation resumes. 784 The admin status takes precedence over auto- 785 partition and functionally operates between the 786 auto-partition mechanism and the AUI/PMA. 788 Setting this object to enabled(1) enables the port 789 and exerts a BEGIN on the port's auto-partition 790 state machine. 792 (In effect, when a port is disabled, the value of 793 rptrPortAutoPartitionState for that port is frozen 794 until the port is next enabled. When the port 795 becomes enabled, the rptrPortAutoPartitionState 796 becomes notAutoPartitioned(1), regardless of its 797 pre-disabling state.)" 798 REFERENCE 799 "[IEEE 802.3 Mgt], 30.4.3.1.2, aPortAdminState 800 and 30.4.3.2.1, acPortAdminControl." 801 ::= { rptrPortEntry 3 } 803 rptrPortAutoPartitionState OBJECT-TYPE 804 SYNTAX INTEGER { 805 notAutoPartitioned(1), 806 autoPartitioned(2) 807 } 808 MAX-ACCESS read-only 809 STATUS current 810 DESCRIPTION 811 "The autoPartitionState flag indicates whether the 812 port is currently partitioned by the repeater's 813 auto-partition protection. 815 The conditions that cause port partitioning are 816 specified in partition state machine in Sections 817 9 and 27 of [IEEE 802.3 Std]. They are not 818 differentiated here." 819 REFERENCE 820 "[IEEE 802.3 Mgt], 30.4.3.1.3, aAutoPartitionState." 821 ::= { rptrPortEntry 4 } 823 rptrPortOperStatus OBJECT-TYPE 824 SYNTAX INTEGER { 825 operational(1), 826 notOperational(2), 827 notPresent(3) 828 } 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "This object indicates the port's operational 833 status. The notPresent(3) status indicates the 834 port is physically removed (note this may or may 835 not be possible depending on the type of port.) 836 The operational(1) status indicates that the port 837 is enabled (see rptrPortAdminStatus) and working, 838 even though it might be auto-partitioned (see 839 rptrPortAutoPartitionState). 841 If this object has the value operational(1) and 842 rptrPortAdminStatus is set to disabled(2), it is 843 expected that this object's value will soon change 844 to notOperational(2)." 845 ::= { rptrPortEntry 5 } 847 rptrPortRptrId OBJECT-TYPE 848 SYNTAX Integer32 (0..2147483647) 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "This object identifies the repeater to 853 which this port belongs. The repeater 854 identified by a particular value of this object 855 is the same as that identified by the same 856 value of rptrInfoId. A value of zero 857 indicates that this port currently is not 858 a member of any repeater." 859 ::= { rptrPortEntry 6 } 861 -- New version of basic information at the repeater level. 862 -- 863 -- Configuration, status, and control objects for 864 -- each managed repeater in the system. 866 rptrInfoTable OBJECT-TYPE 867 SYNTAX SEQUENCE OF RptrInfoEntry 868 MAX-ACCESS not-accessible 869 STATUS current 870 DESCRIPTION 871 "A table of information about each possible 872 non-trivial repeater. The number of entries 873 depends on the physical configuration of the 874 managed system." 875 ::= { rptrAllRptrInfo 1 } 877 rptrInfoEntry OBJECT-TYPE 878 SYNTAX RptrInfoEntry 879 MAX-ACCESS not-accessible 880 STATUS current 881 DESCRIPTION 882 "An entry in the table, containing information 883 about a single non-trivial repeater." 884 INDEX { rptrInfoId } 885 ::= { rptrInfoTable 1 } 887 RptrInfoEntry ::= 888 SEQUENCE { 889 rptrInfoId 890 Integer32, 891 rptrInfoRptrType 892 INTEGER, 893 rptrInfoOperStatus 894 INTEGER, 895 rptrInfoHealthText 896 DisplayString, 897 rptrInfoReset 898 INTEGER, 899 rptrInfoNonDisruptTest 900 INTEGER, 901 rptrInfoPorts 902 Gauge32, 903 rptrInfoPartitionedPorts 904 Gauge32, 905 rptrInfoLastChange 906 TimeStamp 907 } 909 rptrInfoId OBJECT-TYPE 910 SYNTAX Integer32 (1..2147483647) 911 MAX-ACCESS read-only 912 STATUS current 913 DESCRIPTION 914 "This object identifies the repeater for which 915 this entry contains information." 916 ::= { rptrInfoEntry 1 } 918 rptrInfoRptrType OBJECT-TYPE 919 SYNTAX INTEGER { 920 other(1), -- undefined or unknown 921 10MbBaseband(2), 922 100MbBasebandClassI(3), 923 100MbBasebandClassII(4) 924 } 925 MAX-ACCESS read-only 926 STATUS mandatory 927 DESCRIPTION 928 "The rptrInfoRptrType returns a value that identifies 929 the CSMA/CD repeater type." 930 REFERENCE 931 "[IEEE 802.3 Mgt], 30.4.1.1.2, aRepeaterType." 932 ::= { rptrInfoEntry 2 } 934 rptrInfoOperStatus OBJECT-TYPE 935 SYNTAX INTEGER { 936 other(1), -- undefined or unknown 937 ok(2), -- no known failures 938 rptrFailure(3), -- repeater-related failure 939 groupFailure(4), -- group-related failure 940 portFailure(5), -- port-related failure 941 generalFailure(6) -- failure, unspecified type 942 } 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "The rptrInfoOperStatus object indicates the 947 operational state of the repeater. The 948 rptrInfoHealthText object may be consulted 949 for more specific information about the state 950 of the repeater's health. 952 In the case of multiple kinds of failures (e.g., 953 repeater failure and port failure), the value of 954 this attribute shall reflect the highest priority 955 failure in the following order, listed highest 956 priority first: 958 rptrFailure(3) 959 groupFailure(4) 960 portFailure(5) 961 generalFailure(6)." 962 REFERENCE 963 "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState." 964 ::= { rptrInfoEntry 3 } 966 rptrInfoHealthText OBJECT-TYPE 967 SYNTAX DisplayString (SIZE (0..255)) 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "The health text object is a text string that 972 provides information relevant to the operational 973 state of the repeater. Agents may use this string 974 to provide detailed information on current 975 failures, including how they were detected, and/or 976 instructions for problem resolution. The contents 977 are agent-specific." 978 REFERENCE 979 "[IEEE 802.3 Mgt], 30.4.1.1.6, aRepeaterHealthText." 980 ::= { rptrInfoEntry 4 } 982 rptrInfoReset OBJECT-TYPE 983 SYNTAX INTEGER { 984 noReset(1), 985 reset(2) 986 } 987 MAX-ACCESS read-write 988 STATUS current 989 DESCRIPTION 990 "Setting this object to reset(2) causes a 991 transition to the START state of Fig 9-2 in 992 section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, 993 and to the START state of Fig 27-2 in section 27 994 of that standard for a 100Mb/s repeater. 996 Setting this object to noReset(1) has no effect. 997 The agent will always return the value noReset(1) 998 when this object is read. 1000 After receiving a request to set this variable to 1001 reset(2), the agent is allowed to delay the reset 1002 for a short period. For example, the implementor 1003 may choose to delay the reset long enough to allow 1004 the SNMP response to be transmitted. In any 1005 event, the SNMP response must be transmitted. 1007 This action does not reset the management counters 1008 defined in this document nor does it affect the 1009 portAdminStatus parameters. Included in this 1010 action is the execution of a disruptive Self-Test 1011 with the following characteristics: a) The nature 1012 of the tests is not specified. b) The test resets 1013 the repeater but without affecting management 1014 information about the repeater. c) The test does 1015 not inject packets onto any segment. d) Packets 1016 received during the test may or may not be 1017 transferred. e) The test does not interfere with 1018 management functions. 1020 After performing this self-test, the agent will 1021 update the repeater health information (including 1022 rptrInfoOperStatus and rptrInfoHealthText), and 1023 send a rptrInfoHealth trap." 1024 REFERENCE 1025 "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." 1026 ::= { rptrInfoEntry 5 } 1028 rptrInfoNonDisruptTest OBJECT-TYPE 1029 SYNTAX INTEGER { 1030 noSelfTest(1), 1031 selfTest(2) 1032 } 1033 MAX-ACCESS read-write 1034 STATUS current 1035 DESCRIPTION 1036 "Setting this object to selfTest(2) causes the 1037 repeater to perform a agent-specific, non- 1038 disruptive self-test that has the following 1039 characteristics: a) The nature of the tests is 1040 not specified. b) The test does not change the 1041 state of the repeater or management information 1042 about the repeater. c) The test does not inject 1043 packets onto any segment. d) The test does not 1044 prevent the relay of any packets. e) The test 1045 does not interfere with management functions. 1047 After performing this test, the agent will update 1048 the repeater health information (including 1049 rptrInfoOperStatus and rptrInfoHealthText) 1050 and send a rptrInfoHealth trap. 1052 Note that this definition allows returning an 1053 'okay' result after doing a trivial test. 1055 Setting this object to noSelfTest(1) has no 1056 effect. The agent will always return the value 1057 noSelfTest(1) when this object is read." 1058 REFERENCE 1059 "[IEEE 802.3 Mgt], 30.4.1.2.2, 1060 acExecuteNonDisruptiveSelfTest." 1061 ::= { rptrInfoEntry 6 } 1063 rptrInfoPorts OBJECT-TYPE 1064 SYNTAX Gauge32 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "The number of ports that are configured to 1069 be a member of the repeater-unit." 1070 ::= { rptrInfoEntry 7 } 1072 rptrInfoPartitionedPorts OBJECT-TYPE 1073 SYNTAX Gauge32 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "This object returns the total number of ports in 1078 the repeater whose current state meets all three 1079 of the following criteria: rptrPortOperStatus 1080 does not have the value notPresent(3), 1081 rptrPortAdminStatus is enabled(1), and 1082 rptrPortAutoPartitionState is autoPartitioned(2)." 1083 ::= { rptrInfoEntry 8 } 1085 rptrInfoLastChange OBJECT-TYPE 1086 SYNTAX TimeStamp 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "The value of sysUpTime when any of the following 1091 conditions occurred: 1092 1) agent cold- or warm-started; 1093 2) this instance of repeater was created 1094 (such as when a device or module was 1095 added to the system); 1096 3) a change in the value of rptrInfoOperStatus; 1097 4) ports were added or removed as members of 1098 the repeater; or 1099 5) any of the counters associated with this 1100 repeater had a discontinuity." 1101 ::= { rptrInfoEntry 9 } 1103 -- 1104 -- Old version of statistics at the repeater level. 1105 -- 1106 -- Performance monitoring statistics for the repeater 1107 -- 1108 -- In a system containing a single managed repeater-unit, 1109 -- the statistics object for the repeater-unit. 1111 -- The objects contained under the rptrMonitorRptrInfo subtree are 1112 -- intended for backwards compatibility with implementations of 1113 -- RFC 1516. In newer implementations (both single- and 1114 -- multiple-repeater implementations), the rptrMonitorTable will 1115 -- be implemented. It is the preferred source of this information, 1116 -- as it contains the values for all repeaters managed by the 1117 -- agent. In all cases, the objects in the rptrMonitorRptrInfo 1118 -- subtree are duplicates of the corresponding objects in the 1119 -- first entry of the rptrMonitorTable. 1121 rptrMonitorTransmitCollisions OBJECT-TYPE 1122 SYNTAX Counter32 1123 MAX-ACCESS read-only 1124 STATUS deprecated 1125 DESCRIPTION 1126 "For a clause 9 (10Mb/s) repeater, this counter 1127 is incremented every time the repeater state 1128 machine enters the TRANSMIT COLLISION state 1129 from any state other than ONE PORT LEFT 1130 (Ref: Fig 9-2 [IEEE 802.3 Std]). 1132 For a clause 27 repeater, this counter is 1133 incremented every time the repeater core state 1134 diagram enters the Jam state as a result of 1135 Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). 1137 The approximate minimum time for rollover of this 1138 counter is 16 hours in a 10Mb/s repeater and 1.6 1139 hours in a 100Mb/s repeater." 1140 REFERENCE 1141 "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions." 1142 ::= { rptrMonitorRptrInfo 1 } 1144 -- Statistics at the group level. 1145 -- 1146 -- In a system containing a single managed repeater-unit, 1147 -- the statistics objects for each group. 1149 rptrMonitorGroupTable OBJECT-TYPE 1150 SYNTAX SEQUENCE OF RptrMonitorGroupEntry 1151 MAX-ACCESS not-accessible 1152 STATUS deprecated 1153 DESCRIPTION 1154 "Table of performance and error statistics for the 1155 groups within the repeater. The number of entries 1156 is the same as that in the rptrGroupTable." 1157 ::= { rptrMonitorGroupInfo 1 } 1159 rptrMonitorGroupEntry OBJECT-TYPE 1160 SYNTAX RptrMonitorGroupEntry 1161 MAX-ACCESS not-accessible 1162 STATUS deprecated 1163 DESCRIPTION 1164 "An entry in the table, containing total 1165 performance and error statistics for a single 1166 group. Regular retrieval of the information in 1167 this table provides a means of tracking the 1168 performance and health of the networked devices 1169 attached to this group's ports. 1171 The counters in this table are redundant in the 1172 sense that they are the summations of information 1173 already available through other objects. However, 1174 these sums provide a considerable optimization of 1175 network management traffic over the otherwise 1176 necessary retrieval of the individual counters 1177 included in each sum. 1179 Note: Group-level counters are 1180 deprecated in this MIB. It is recommended 1181 that management applications instead use 1182 the repeater-level counters contained in 1183 the rptrMonTable." 1184 INDEX { rptrMonitorGroupIndex } 1185 ::= { rptrMonitorGroupTable 1 } 1187 RptrMonitorGroupEntry ::= 1188 SEQUENCE { 1189 rptrMonitorGroupIndex 1190 Integer32, 1191 rptrMonitorGroupTotalFrames 1192 Counter32, 1193 rptrMonitorGroupTotalOctets 1194 Counter32, 1195 rptrMonitorGroupTotalErrors 1196 Counter32 1197 } 1199 rptrMonitorGroupIndex OBJECT-TYPE 1200 SYNTAX Integer32 (1..2147483647) 1201 MAX-ACCESS read-only 1202 STATUS deprecated 1203 DESCRIPTION 1204 "This object identifies the group within the 1205 repeater for which this entry contains 1206 information." 1207 ::= { rptrMonitorGroupEntry 1 } 1209 rptrMonitorGroupTotalFrames OBJECT-TYPE 1210 SYNTAX Counter32 1211 MAX-ACCESS read-only 1212 STATUS deprecated 1213 DESCRIPTION 1214 "The total number of frames of valid frame length 1215 that have been received on the ports in this group 1216 and for which the FCSError and CollisionEvent 1217 signals were not asserted. This counter is the 1218 summation of the values of the 1219 rptrMonitorPortReadableFrames counters for all of 1220 the ports in the group. 1222 This statistic provides one of the parameters 1223 necessary for obtaining the packet error rate. 1224 The approximate minimum time for rollover of this 1225 counter is 80 hours in a 10Mb/s repeater." 1226 ::= { rptrMonitorGroupEntry 2 } 1228 rptrMonitorGroupTotalOctets OBJECT-TYPE 1229 SYNTAX Counter32 1230 MAX-ACCESS read-only 1231 STATUS deprecated 1232 DESCRIPTION 1233 "The total number of octets contained in the valid 1234 frames that have been received on the ports in 1235 this group. This counter is the summation of the 1236 values of the rptrMonitorPortReadableOctets 1237 counters for all of the ports in the group. 1239 This statistic provides an indicator of the total 1240 data transferred. The approximate minimum time 1241 for rollover of this counter is 58 minutes in a 1242 10Mb/s repeater." 1243 ::= { rptrMonitorGroupEntry 3 } 1245 rptrMonitorGroupTotalErrors OBJECT-TYPE 1246 SYNTAX Counter32 1247 MAX-ACCESS read-only 1248 STATUS deprecated 1249 DESCRIPTION 1250 "The total number of errors which have occurred on 1251 all of the ports in this group. This counter is 1252 the summation of the values of the 1253 rptrMonitorPortTotalErrors counters for all of the 1254 ports in the group." 1255 ::= { rptrMonitorGroupEntry 4 } 1257 -- Statistics at the port level. 1258 -- 1260 rptrMonitorPortTable OBJECT-TYPE 1261 SYNTAX SEQUENCE OF RptrMonitorPortEntry 1262 MAX-ACCESS not-accessible 1263 STATUS current 1264 DESCRIPTION 1265 "Table of performance and error statistics for the 1266 ports. The number of entries is the same as that 1267 in the rptrPortTable. 1269 The columnar object rptrMonitorPortLastChange 1270 is used to indicate possible discontinuities 1271 of counter type columnar objects in the table." 1272 ::= { rptrMonitorPortInfo 1 } 1274 rptrMonitorPortEntry OBJECT-TYPE 1275 SYNTAX RptrMonitorPortEntry 1276 MAX-ACCESS not-accessible 1277 STATUS current 1278 DESCRIPTION 1279 "An entry in the table, containing performance and 1280 error statistics for a single port." 1281 INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex } 1282 ::= { rptrMonitorPortTable 1 } 1284 RptrMonitorPortEntry ::= 1285 SEQUENCE { 1286 rptrMonitorPortGroupIndex 1287 Integer32, 1288 rptrMonitorPortIndex 1289 Integer32, 1290 rptrMonitorPortReadableFrames 1291 Counter32, 1292 rptrMonitorPortReadableOctets 1293 Counter32, 1294 rptrMonitorPortFCSErrors 1295 Counter32, 1296 rptrMonitorPortAlignmentErrors 1297 Counter32, 1298 rptrMonitorPortFrameTooLongs 1299 Counter32, 1300 rptrMonitorPortShortEvents 1301 Counter32, 1302 rptrMonitorPortRunts 1303 Counter32, 1304 rptrMonitorPortCollisions 1305 Counter32, 1306 rptrMonitorPortLateEvents 1307 Counter32, 1308 rptrMonitorPortVeryLongEvents 1309 Counter32, 1310 rptrMonitorPortDataRateMismatches 1311 Counter32, 1312 rptrMonitorPortAutoPartitions 1313 Counter32, 1314 rptrMonitorPortTotalErrors 1315 Counter32, 1316 rptrMonitorPortIsolates 1317 Counter32, 1318 rptrMonitorPortSymbolErrors 1319 Counter32, 1320 rptrMonitorPortUpper32Octets 1321 Counter32, 1322 rptrMonitorPortLCReadableOctets 1323 Counter64, 1324 rptrMonitorPortLastChange 1325 TimeStamp 1326 } 1328 rptrMonitorPortGroupIndex OBJECT-TYPE 1329 SYNTAX Integer32 (1..2147483647) 1330 MAX-ACCESS read-only 1331 STATUS current 1332 DESCRIPTION 1333 "This object identifies the group containing the 1334 port for which this entry contains information." 1335 ::= { rptrMonitorPortEntry 1 } 1337 rptrMonitorPortIndex OBJECT-TYPE 1338 SYNTAX Integer32 (1..2147483647) 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "This object identifies the port within the group 1343 for which this entry contains information." 1344 REFERENCE 1345 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." 1346 ::= { rptrMonitorPortEntry 2 } 1348 rptrMonitorPortReadableFrames OBJECT-TYPE 1349 SYNTAX Counter32 1350 MAX-ACCESS read-only 1351 STATUS current 1352 DESCRIPTION 1353 "This object is the number of frames of valid 1354 frame length that have been received on this port. 1355 This counter is incremented by one for each frame 1356 received on this port whose OctetCount is greater 1357 than or equal to minFrameSize and less than or 1358 equal to maxFrameSize (Ref: IEEE 802.3 Std, 1359 4.4.2.1) and for which the FCSError and 1360 CollisionEvent signals are not asserted. 1362 A discontinuity may occur in the value 1363 when the value of object 1364 rptrMonitorPortLastChange changes. 1366 This statistic provides one of the parameters 1367 necessary for obtaining the packet error rate. 1368 The approximate minimum time for rollover of this 1369 counter is 80 hours at 10Mb/s." 1370 REFERENCE 1371 "[IEEE 802.3 Mgt], 30.4.3.1.4, aReadableFrames." 1372 ::= { rptrMonitorPortEntry 3 } 1374 rptrMonitorPortReadableOctets OBJECT-TYPE 1375 SYNTAX Counter32 1376 MAX-ACCESS read-only 1377 STATUS current 1378 DESCRIPTION 1379 "This object is the number of octets contained in 1380 valid frames that have been received on this port. 1381 This counter is incremented by OctetCount for each 1382 frame received on this port which has been 1383 determined to be a readable frame (i.e., including 1384 FCS octets but excluding framing bits and dribble 1385 bits). 1387 A discontinuity may occur in the value 1388 when the value of object 1389 rptrMonitorPortLastChange changes. 1391 This statistic provides an indicator of the total 1392 data transferred. The approximate minimum time 1393 for rollover of this counter in a 10Mb/s repeater 1394 is 58 minutes. 1396 For ports receiving traffic at a maximum rate in 1397 a 100Mb/s repeater, this counter can roll over 1398 in less than 6 minutes. Since that amount of time 1399 could be less than a management station's poll cycle 1400 time, in order to avoid a loss of information a 1401 management station is advised to also poll the 1402 rptrMonitorPortUpper32Octets object, or to use the 1403 64-bit counter defined by 1404 rptrMonitorPortLCReadableOctets instead of the 1405 two 32-bit counters." 1406 REFERENCE 1407 "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets." 1408 ::= { rptrMonitorPortEntry 4 } 1410 rptrMonitorPortFCSErrors OBJECT-TYPE 1411 SYNTAX Counter32 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "This counter is incremented by one for each frame 1416 received on this port with the FCSError signal 1417 asserted and the FramingError and CollisionEvent 1418 signals deasserted and whose OctetCount is greater 1419 than or equal to minFrameSize and less than or 1420 equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 1421 Std). 1423 A discontinuity may occur in the value 1424 when the value of object 1425 rptrMonitorPortLastChange changes. 1427 The approximate minimum time for rollover of this 1428 counter is 80 hours at 10Mb/s." 1429 REFERENCE 1430 "[IEEE 802.3 Mgt], 30.4.3.1.6, 1431 aFrameCheckSequenceErrors." 1432 ::= { rptrMonitorPortEntry 5 } 1434 rptrMonitorPortAlignmentErrors OBJECT-TYPE 1435 SYNTAX Counter32 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "This counter is incremented by one for each frame 1440 received on this port with the FCSError and 1441 FramingError signals asserted and CollisionEvent 1442 signal deasserted and whose OctetCount is greater 1443 than or equal to minFrameSize and less than or 1444 equal to maxFrameSize (Ref: IEEE 802.3 Std, 1445 4.4.2.1). If rptrMonitorPortAlignmentErrors is 1446 incremented then the rptrMonitorPortFCSErrors 1447 Counter shall not be incremented for the same 1448 frame. 1450 A discontinuity may occur in the value 1451 when the value of object 1452 rptrMonitorPortLastChange changes. 1454 The approximate minimum time for rollover of this 1455 counter is 80 hours at 10Mb/s." 1456 REFERENCE 1457 "[IEEE 802.3 Mgt], 30.4.3.1.7, aAlignmentErrors." 1458 ::= { rptrMonitorPortEntry 6 } 1460 rptrMonitorPortFrameTooLongs OBJECT-TYPE 1461 SYNTAX Counter32 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "This counter is incremented by one for each frame 1466 received on this port whose OctetCount is greater 1467 than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). 1468 If rptrMonitorPortFrameTooLongs is incremented 1469 then neither the rptrMonitorPortAlignmentErrors 1470 nor the rptrMonitorPortFCSErrors counter shall be 1471 incremented for the frame. 1473 A discontinuity may occur in the value 1474 when the value of object 1475 rptrMonitorPortLastChange changes. 1477 The approximate minimum time for rollover of this 1478 counter is 61 days in a 10Mb/s repeater." 1479 REFERENCE 1480 "[IEEE 802.3 Mgt], 30.4.3.1.8, aFramesTooLong." 1481 ::= { rptrMonitorPortEntry 7 } 1483 rptrMonitorPortShortEvents OBJECT-TYPE 1484 SYNTAX Counter32 1485 MAX-ACCESS read-only 1486 STATUS current 1487 DESCRIPTION 1488 "This counter is incremented by one for each 1489 CarrierEvent on this port with ActivityDuration 1490 less than ShortEventMaxTime. ShortEventMaxTime is 1491 greater than 74 bit times and less than 82 bit 1492 times. ShortEventMaxTime has tolerances included 1493 to provide for circuit losses between a 1494 conformance test point at the AUI and the 1495 measurement point within the state machine. 1497 Notes: 1499 ShortEvents may indicate externally 1500 generated noise hits which will cause the repeater 1501 to transmit Runts to its other ports, or propagate 1502 a collision (which may be late) back to the 1503 transmitting DTE and damaged frames to the rest of 1504 the network. 1506 Implementors may wish to consider selecting the 1507 ShortEventMaxTime towards the lower end of the 1508 allowed tolerance range to accommodate bit losses 1509 suffered through physical channel devices not 1510 budgeted for within this standard. 1512 The significance of this attribute is different 1513 in 10 and 100 Mb/s collision domains. Clause 9 1514 repeaters perform fragment extension of short 1515 events which would be counted as runts on the 1516 interconnect ports of other repeaters. Clause 1517 27 repeaters do not perform fragment extension. 1519 A discontinuity may occur in the value 1520 when the value of object 1521 rptrMonitorPortLastChange changes. 1523 The approximate minimum time for rollover of this 1524 counter is 16 hours in a 10Mb/s repeater." 1525 REFERENCE 1526 "[IEEE 802.3 Mgt], 30.4.3.1.9, aShortEvents." 1527 ::= { rptrMonitorPortEntry 8 } 1529 rptrMonitorPortRunts OBJECT-TYPE 1530 SYNTAX Counter32 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "This counter is incremented by one for each 1535 CarrierEvent on this port that meets one of the 1536 following two conditions. Only one test need be 1537 made. a) The ActivityDuration is greater than 1538 ShortEventMaxTime and less than ValidPacketMinTime 1539 and the CollisionEvent signal is deasserted. b) 1540 The OctetCount is less than 64, the 1541 ActivityDuration is greater than ShortEventMaxTime 1542 and the CollisionEvent signal is deasserted. 1543 ValidPacketMinTime is greater than or equal to 552 1544 bit times and less than 565 bit times. 1546 An event whose length is greater than 74 bit times 1547 but less than 82 bit times shall increment either 1548 the shortEvents counter or the runts counter but 1549 not both. A CarrierEvent greater than or equal to 1550 552 bit times but less than 565 bit times may or 1551 may not be counted as a runt. 1553 ValidPacketMinTime has tolerances included to 1554 provide for circuit losses between a conformance 1555 test point at the AUI and the measurement point 1556 within the state machine. 1558 Runts usually indicate collision fragments, a 1559 normal network event. In certain situations 1560 associated with large diameter networks a 1561 percentage of collision fragments may exceed 1562 ValidPacketMinTime. 1564 A discontinuity may occur in the value 1565 when the value of object 1566 rptrMonitorPortLastChange changes. 1568 The approximate minimum time for rollover of this 1569 counter is 16 hours in a 10Mb/s repeater." 1570 REFERENCE 1571 "[IEEE 802.3 Mgt], 30.4.3.1.10, aRunts." 1572 ::= { rptrMonitorPortEntry 9 } 1574 rptrMonitorPortCollisions OBJECT-TYPE 1575 SYNTAX Counter32 1576 MAX-ACCESS read-only 1577 STATUS current 1578 DESCRIPTION 1579 "For a clause 9 repeater, this counter is 1580 incremented by one for any CarrierEvent signal 1581 on any port for which the CollisionEvent signal 1582 on this port is asserted. For a clause 27 1583 repeater port the counter increments on entering 1584 the Collision Count Increment state of the 1585 partition state diagram (fig 27-8 of 1586 [IEEE 802.3 Std]). 1588 A discontinuity may occur in the value 1589 when the value of object 1590 rptrMonitorPortLastChange changes. 1592 The approximate minimum time for rollover of this 1593 counter is 16 hours in a 10Mb/s repeater." 1594 REFERENCE 1595 "[IEEE 802.3 Mgt], 30.4.3.1.11, aCollisions." 1596 ::= { rptrMonitorPortEntry 10 } 1598 rptrMonitorPortLateEvents OBJECT-TYPE 1599 SYNTAX Counter32 1600 MAX-ACCESS read-only 1601 STATUS current 1602 DESCRIPTION 1603 "For a clause 9 repeater port, this counter is 1604 incremented by one for each CarrierEvent 1605 on this port in which the CollIn(X) 1606 variable transitions to the value SQE (Ref: 1607 9.6.6.2, IEEE 802.3 Std) while the 1608 ActivityDuration is greater than the 1609 LateEventThreshold. For a clause 27 repeater 1610 port, this counter is incremented by one on 1611 entering the Collision Count Increment state 1612 of the partition state diagram (fig 27-8) 1613 while the ActivityDuration is greater than 1614 the LateEvent- Threshold. Such a CarrierEvent 1615 is counted twice, as both a collision and as a 1616 lateEvent. 1618 The LateEventThreshold is greater than 480 bit 1619 times and less than 565 bit times. 1620 LateEventThreshold has tolerances included to 1621 permit an implementation to build a single 1622 threshold to serve as both the LateEventThreshold 1623 and ValidPacketMinTime threshold. 1625 A discontinuity may occur in the value 1626 when the value of object 1627 rptrMonitorPortLastChange changes. 1629 The approximate minimum time for rollover of this 1630 counter is 81 hours in a 10Mb/s repeater." 1631 REFERENCE 1632 "[IEEE 802.3 Mgt], 30.4.3.1.12, aLateEvents." 1633 ::= { rptrMonitorPortEntry 11 } 1635 rptrMonitorPortVeryLongEvents OBJECT-TYPE 1636 SYNTAX Counter32 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "For a clause 9 repeater port, this counter 1641 is incremented by one for each CarrierEvent 1642 whose ActivityDuration is greater than the 1643 MAU Jabber Lockup Protection timer TW3 1644 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). 1646 For a clause 27 repeater port, this counter 1647 is incremented by one on entry to the 1648 Rx Jabber state of the receiver timer state 1649 diagram (fig 27-7). Other counters may 1650 be incremented as appropriate. 1652 A discontinuity may occur in the value 1653 when the value of object 1654 rptrMonitorPortLastChange changes." 1655 REFERENCE 1656 "[IEEE 802.3 Mgt], 30.4.3.1.13, aVeryLongEvents." 1657 ::= { rptrMonitorPortEntry 12 } 1659 rptrMonitorPortDataRateMismatches OBJECT-TYPE 1660 SYNTAX Counter32 1661 MAX-ACCESS read-only 1662 STATUS current 1663 DESCRIPTION 1664 "This counter is incremented by one for each 1665 frame received by this port that meets all 1666 of the conditions required by only one of the 1667 following two measurement methods: 1669 Measurement method A: 1) The CollisionEvent 1670 signal is not asserted (10Mb/s operation) or 1671 the Collision Count Increment state of the 1672 partition state diagram (fig 27-8 of 1673 [IEEE 802.3 Std]) has not been entered 1674 (100Mb/s operation). 2) The ActivityDuration 1675 is greater than ValidPacketMinTime. 3) The 1676 frequency (data rate) is detectably mismatched 1677 from the local transmit frequency. 1679 Measurement method B: 1) The CollisionEvent 1680 signal is not asserted (10Mb/s operation) 1681 or the Collision Count Increment state of the 1682 partition state diagram (fig 27-8 of 1683 [IEEE 802.3 Std]) has not been entered 1684 (100Mb/s operation). 2) The OctetCount is 1685 greater than 63. 3) The frequency (data 1686 rate) is detectably mismatched from the local 1687 transmit frequency. The exact degree of 1688 mismatch is vendor specific and is to be 1689 defined by the vendor for conformance testing. 1691 When this event occurs, other counters whose 1692 increment conditions were satisfied may or may not 1693 also be incremented, at the implementor's 1694 discretion. Whether or not the repeater was able 1695 to maintain data integrity is beyond the scope of 1696 this standard. 1698 A discontinuity may occur in the value 1699 when the value of object 1700 rptrMonitorPortLastChange changes." 1701 REFERENCE 1702 "[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches." 1703 ::= { rptrMonitorPortEntry 13 } 1705 rptrMonitorPortAutoPartitions OBJECT-TYPE 1706 SYNTAX Counter32 1707 MAX-ACCESS read-only 1708 STATUS current 1709 DESCRIPTION 1710 "This counter is incremented by one for 1711 each time the repeater has automatically 1712 partitioned this port. 1714 The conditions that cause a clause 9 1715 repeater port to partition are specified in 1716 the partition state diagram in clause 9 of 1717 [IEEE 802.3 Std]. They are not differentiated 1718 here. A clause 27 repeater port partitions 1719 on entry to the Partition Wait state of the 1720 partition state diagram (fig 27-8 in 1721 [IEEE 802.3 Std]). 1723 A discontinuity may occur in the value 1724 when the value of object 1725 rptrMonitorPortLastChange changes." 1726 REFERENCE 1727 "[IEEE 802.3 Mgt], 30.4.3.1.15, aAutoPartitions." 1728 ::= { rptrMonitorPortEntry 14 } 1730 rptrMonitorPortTotalErrors OBJECT-TYPE 1731 SYNTAX Counter32 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "The total number of errors which have occurred on 1736 this port. This counter is the summation of the 1737 values of other error counters (for the same 1738 port), namely: 1740 rptrMonitorPortFCSErrors, 1741 rptrMonitorPortAlignmentErrors, 1742 rptrMonitorPortFrameTooLongs, 1743 rptrMonitorPortShortEvents, 1744 rptrMonitorPortLateEvents, 1745 rptrMonitorPortVeryLongEvents, and 1746 rptrMonitorPortDataRateMismatches. 1748 This counter is redundant in the sense that it is 1749 the summation of information already available 1750 through other objects. However, it is included 1751 specifically because the regular retrieval of this 1752 object as a means of tracking the health of a port 1753 provides a considerable optimization of network 1754 management traffic over the otherwise necessary 1755 retrieval of the summed counters. 1757 Note that rptrMonitorPortRunts is not included 1758 in this total; this is because runts usually 1759 indicate collision fragments, a normal network 1760 event. 1762 [Editor's note: This sum does not include the 1763 value of the rptrMonitorPortSymbolErrors object. 1764 Perhaps we should deprecate it and define a new 1765 PortTotalErrors object which does. However, we 1766 may need to address the rollover issue in that 1767 case.] 1769 This object is a delta value, providing the 1770 count of total errors on the port between 1771 the current time and the time which is the 1772 value of object rptrMonitorPortLastChange. 1774 A discontinuity may occur in the value 1775 when the value of object 1776 rptrMonitorPortLastChange changes." 1777 ::= { rptrMonitorPortEntry 15 } 1779 rptrMonitorPortIsolates OBJECT-TYPE 1780 SYNTAX Counter32 1781 MAX-ACCESS read-only 1782 STATUS mandatory 1783 DESCRIPTION 1784 "This counter is incremented by one each time that 1785 the repeater port automatically isolates as a 1786 consequence of false carrier events. The conditions 1787 which cause a port to automatically isolate are 1788 defined by the transition from the False Carrier 1789 state to the Link Unstable state of the carrier 1790 integrity state diagram (figure 27-9) 1791 [IEEE 802.3 Standard]. 1793 Note: Isolates do not affect the value of 1794 the PortOperStatus object. 1796 A discontinuity may occur in the value 1797 when the value of object 1798 rptrMonitorPortLastChange changes." 1799 REFERENCE 1800 "[IEEE 802.3 Mgt], 30.4.3.1.16, aIsolates." 1801 ::= { rptrMonitorPortEntry 16 } 1803 rptrMonitorPortSymbolErrors OBJECT-TYPE 1804 SYNTAX Counter32 1805 MAX-ACCESS read-only 1806 STATUS mandatory 1807 DESCRIPTION 1808 "This counter is incremented by one each time when 1809 valid length packet was received at the port and 1810 there was at least one occurrence of an invalid 1811 data symbol. This can increment only once per valid 1812 carrier event. A collision presence at any port of 1813 the repeater containing port N, will not cause this 1814 attribute to increment. 1816 A discontinuity may occur in the value 1817 when the value of object 1818 rptrMonitorPortLastChange changes. 1820 The approximate minimum time for rollover of this 1821 counter is 7.4 hours at 100Mb/s." 1822 REFERENCE 1823 "[IEEE 802.3 Mgt], 30.4.3.1.17, 1824 aSymbolErrorDuringPacket." 1825 ::= { rptrMonitorPortEntry 17 } 1827 rptrMonitorPortUpper32Octets OBJECT-TYPE 1828 SYNTAX Counter32 1829 MAX-ACCESS read-only 1830 STATUS mandatory 1831 DESCRIPTION 1832 "This object is the number of octets contained in 1833 valid frames that have been received on this port, 1834 modulo 2**32. That is, it contains the upper 32 1835 bits of a 64-bit octets counter, of which the 1836 lower 32 bits are contained in the 1837 rptrMonitorPortReadableOctets object. 1839 This two-counter mechanism is provided for those 1840 network management protocols that do not support 1841 64-bit counters (e.g. SNMP V1) and are used to 1842 manage a repeater type of 100Mb/s. 1844 A discontinuity may occur in the value 1845 when the value of object 1846 rptrMonitorPortLastChange changes." 1847 ::= { rptrMonitorPortEntry 18 } 1849 rptrMonitorPortLCReadableOctets OBJECT-TYPE 1850 SYNTAX Counter64 1851 MAX-ACCESS read-only 1852 STATUS mandatory 1853 DESCRIPTION 1854 "This object is the number of octets contained in 1855 valid frames that have been received on this port. 1856 This counter is incremented by OctetCount for each 1857 frame received on this port which has been 1858 determined to be a readable frame (i.e., including 1859 FCS octets but excluding framing bits and dribble 1860 bits). 1862 This statistic provides an indicator of the total 1863 data transferred. 1865 This counter is a 64-bit version of rptrMonitor- 1866 PortReadableOctets. It should be used by network 1867 management protocols which suppport 64-bit counters 1868 (e.g. SNMPv2). 1870 A discontinuity may occur in the value 1871 when the value of object 1872 rptrMonitorPortLastChange changes." 1873 REFERENCE 1874 "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets." 1875 ::= { rptrMonitorPortEntry 19 } 1877 rptrMonitorPortLastChange OBJECT-TYPE 1878 SYNTAX TimeStamp 1879 MAX-ACCESS read-only 1880 STATUS current 1881 DESCRIPTION 1882 "The value of sysUpTime when the last of 1883 the following occurred: 1884 1) the agent cold- or warm-started; 1885 2) the row for the port was created 1886 (such as when a device or module was added 1887 to the system); or 1888 3) any condition that would cause one of 1889 the counters for the row to experience 1890 a discontinuity." 1891 ::= { rptrMonitorPortEntry 20 } 1893 -- New version of statistics at the repeater level. 1894 -- 1895 -- Statistics objects for each managed repeater 1896 -- in the system. 1898 rptrMonTable OBJECT-TYPE 1899 SYNTAX SEQUENCE OF rptrMonEntry 1900 MAX-ACCESS not-accessible 1901 STATUS current 1902 DESCRIPTION 1903 "A table of information about each possible 1904 non-trivial repeater. The number of entries 1905 in this table is the same as the number of 1906 entries in the rptrInfoTable. 1908 The columnar object rptrInfoLastChange is 1909 used to indicate possible discontinuities of 1910 counter type columnar objects in this table." 1911 ::= { rptrMonitorAllRptrInfo 1 } 1913 rptrMonEntry OBJECT-TYPE 1914 SYNTAX rptrMonEntry 1915 MAX-ACCESS not-accessible 1916 STATUS current 1917 DESCRIPTION 1918 "An entry in the table, containing information 1919 about a single non-trivial repeater." 1920 AUGMENTS { rptrInfoEntry } 1921 ::= { rptrMonTable 1 } 1923 rptrMonEntry ::= 1924 SEQUENCE { 1925 rptrMonTxCollisions 1926 Counter32, 1927 rptrMonTotalFrames 1928 Counter32, 1929 rptrMonTotalErrors 1930 Counter32, 1931 rptrMonUpper32TotalOctets 1932 Counter32, 1933 rptrMonLower32TotalOctets 1934 Counter32, 1935 rptrMonLCTotalOctets 1936 Counter64 1937 } 1939 rptrMonTxCollisions OBJECT-TYPE 1940 SYNTAX Counter32 1941 MAX-ACCESS read-only 1942 STATUS current 1943 DESCRIPTION 1944 "For a clause 9 (10Mb/s) repeater, this counter 1945 is incremented every time the repeater state 1946 machine enters the TRANSMIT COLLISION state 1947 from any state other than ONE PORT LEFT 1948 (Ref: Fig 9-2 [IEEE 802.3 Std]). 1950 For a clause 27 repeater, this counter is 1951 incremented every time the repeater core state 1952 diagram enters the Jam state as a result of 1953 Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). 1955 This object is a delta value, providing 1956 the count of transmit collisions between 1957 the current time and the time which is the 1958 value of object rptrInfoLastChange. 1960 The approximate minimum time for rollover of this 1961 counter is 16 hours in a 10Mb/s repeater and 1.6 1962 hours in a 100Mb/s repeater." 1963 REFERENCE 1964 "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions" 1965 ::= { rptrMonEntry 1 } 1967 rptrMonTotalFrames OBJECT-TYPE 1968 SYNTAX Counter32 1969 MAX-ACCESS read-only 1970 STATUS current 1971 DESCRIPTION 1972 "The number of frames of valid frame length 1973 that have been received on the ports in this repeater 1974 and for which the FCSError and CollisionEvent 1975 signals were not asserted. If an implementation 1976 can not obtain a count of frames as seen by 1977 the repeater itself, this counter may be 1978 implemented as the summation of the values of the 1979 rptrMonitorPortReadableFrames counters for all of 1980 the ports in the repeater. 1982 This object is a delta value, providing 1983 the count of total frames between the 1984 current time and the time which is the 1985 value of object rptrInfoLastChange. 1987 This statistic provides one of the parameters 1988 necessary for obtaining the packet error rate. 1989 The approximate minimum time for rollover of this 1990 counter is 80 hours in a 10Mb/s repeater." 1991 ::= { rptrMonEntry 3 } 1993 rptrMonTotalErrors OBJECT-TYPE 1994 SYNTAX Counter32 1995 MAX-ACCESS read-only 1996 STATUS current 1997 DESCRIPTION 1998 "The total number of errors which have occurred on 1999 all of the ports in this repeater. The errors 2000 included in this count are the same as those listed 2001 for the rptrMonitorPortTotalErrors counter. If an 2002 implementation can not obtain a count of these 2003 errors as seen by the repeater itself, this counter 2004 may be implemented as the summation of the values of 2005 the rptrMonitorPortTotalErrors counters for all of 2006 the ports in the repeater. 2008 This object is a delta value, providing 2009 the count of total errors between the 2010 current time and the time which is the 2011 value of object rptrInfoLastChange." 2012 ::= { rptrMonEntry 4 } 2014 rptrMonUpper32TotalOctets OBJECT-TYPE 2015 SYNTAX Counter32 2016 MAX-ACCESS read-only 2017 STATUS mandatory 2018 DESCRIPTION 2019 "The total number of octets contained in the valid 2020 frames that have been received on the ports in 2021 this repeater, modulo 2**32. That is, it contains 2022 the upper 32 bits of a 64-bit counter, of which 2023 the lower 32 bits are contained in the 2024 rptrMonLower32TotalOctets object. If an 2025 implementation can not obtain a count of octets 2026 as seen by the repeater itself, the 64-bit 2027 value may be the summation of the values of the 2028 rptrMonitorPortReadableOctets counters combined 2029 with the corresponding rptrMonitorPortUpper32Octets 2030 counters for all of the ports in the repeater. 2032 This object is a delta value, providing the 2033 count of octets received between the current 2034 time and the time which is the value of object 2035 rptrInfoLastChange. 2037 This statistic provides an indicator of the total 2038 data transferred within the repeater. 2040 This two-counter mechanism is provided for those 2041 network management protocols that do not support 2042 64-bit counters (e.g. SNMP V1) and are used to 2043 manage a repeater type of 100Mb/s." 2044 ::= { rptrMonEntry 5 } 2046 rptrMonLower32TotalOctets OBJECT-TYPE 2047 SYNTAX Counter32 2048 MAX-ACCESS read-only 2049 STATUS mandatory 2050 DESCRIPTION 2051 "The total number of octets contained in the valid 2052 frames that have been received on the ports in 2053 this group. If an implementation can not obtain 2054 a count of octets as seen by the repeater itself, 2055 this counter may be the summation of the 2056 values of the rptrMonitorPortReadableOctets 2057 counters for all of the ports in the group. 2059 This object is a delta value, providing 2060 the count of octets between the current 2061 time and the time which is the value of 2062 object rptrInfoLastChange. 2064 This statistic provides an indicator of the total 2065 data transferred. The approximate minimum time 2066 for rollover of this counter in a 10Mb/s repeater 2067 is 58 minutes divided by the number of ports in 2068 the repeater. 2070 For 100Mb/s repeaters processing traffic at a 2071 maximum rate, this counter can roll over in less 2072 than 6 minutes divided by the number of ports in 2073 the repeater. Since that amount of time could 2074 be less than a management station's poll cycle 2075 time, in order to avoid a loss of information a 2076 management station is advised to also poll the 2077 rptrMonUpper32TotalOctets object, or to use the 2078 64-bit counter defined by rptrMonLCTotalOctets 2079 instead of the two 32-bit counters." 2080 ::= { rptrMonEntry 6 } 2082 rptrMonLCTotalOctets OBJECT-TYPE 2083 SYNTAX Counter64 2084 MAX-ACCESS read-only 2085 STATUS mandatory 2086 DESCRIPTION 2087 "The total number of octets contained in the valid 2088 frames that have been received on the ports in 2089 this group. If a implementation can not obtain 2090 a count of octets as seen by the repeater itself, 2091 this counter may be the summation of the 2092 values of the rptrMonitorPortReadableOctets 2093 counters for all of the ports in the group. 2095 This object is a delta value, providing 2096 the count of octets between the current 2097 time and the time which is the value of 2098 object rptrInfoLastChange. 2100 This statistic provides an indicator of the total 2101 data transferred. 2103 This counter is a 64-bit version of rptrMon- 2104 Upper32TotalOctets and rptrMonLower32TotalOctets. 2105 It should be used by network management protocols 2106 which support 64-bit counters (e.g. SNMPv2). " 2107 ::= { rptrMonEntry 7 } 2109 -- 2110 -- The Port Address Tracking Table 2111 -- 2113 rptrAddrTrackTable OBJECT-TYPE 2114 SYNTAX SEQUENCE OF RptrAddrTrackEntry 2115 MAX-ACCESS not-accessible 2116 STATUS current 2117 DESCRIPTION 2118 "Table of address mapping information about the 2119 ports." 2120 ::= { rptrAddrTrackPortInfo 1 } 2122 rptrAddrTrackEntry OBJECT-TYPE 2123 SYNTAX RptrAddrTrackEntry 2124 MAX-ACCESS not-accessible 2125 STATUS current 2126 DESCRIPTION 2127 "An entry in the table, containing address mapping 2128 information about a single port." 2129 INDEX { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex } 2130 ::= { rptrAddrTrackTable 1 } 2132 RptrAddrTrackEntry ::= 2133 SEQUENCE { 2134 rptrAddrTrackGroupIndex 2135 INTEGER, 2136 rptrAddrTrackPortIndex 2137 INTEGER, 2138 rptrAddrTrackLastSourceAddress -- DEPRECATED OBJECT 2139 MacAddress, 2140 rptrAddrTrackSourceAddrChanges 2141 Counter32, 2142 rptrAddrTrackNewLastSrcAddress 2143 OptMcAddr, 2144 rptrAddrTrackCapacity 2145 Integer32 2146 } 2148 rptrAddrTrackGroupIndex OBJECT-TYPE 2149 SYNTAX INTEGER (1..2147483647) 2150 MAX-ACCESS read-only 2151 STATUS current 2152 DESCRIPTION 2153 "This object identifies the group containing the 2154 port for which this entry contains information." 2155 ::= { rptrAddrTrackEntry 1 } 2157 rptrAddrTrackPortIndex OBJECT-TYPE 2158 SYNTAX INTEGER (1..2147483647) 2159 MAX-ACCESS read-only 2160 STATUS current 2161 DESCRIPTION 2162 "This object identifies the port within the group 2163 for which this entry contains information." 2165 REFERENCE 2166 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." 2167 ::= { rptrAddrTrackEntry 2 } 2169 rptrAddrTrackLastSourceAddress OBJECT-TYPE 2170 SYNTAX MacAddress 2171 MAX-ACCESS read-only 2172 STATUS deprecated 2173 DESCRIPTION 2174 "This object is the SourceAddress of the last 2175 readable frame (i.e., counted by 2176 rptrMonitorPortReadableFrames) received by this 2177 port. 2179 This object has been deprecated because its value 2180 is undefined when no frames have been observed on 2181 this port. The replacement object is 2182 rptrAddrTrackNewLastSrcAddress." 2183 REFERENCE 2184 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2185 ::= { rptrAddrTrackEntry 3 } 2187 rptrAddrTrackSourceAddrChanges OBJECT-TYPE 2188 SYNTAX Counter32 2189 MAX-ACCESS read-only 2190 STATUS current 2191 DESCRIPTION 2192 "This counter is incremented by one for each time 2193 that the rptrAddrTrackLastSourceAddress attribute 2194 for this port has changed. 2196 This may indicate whether a link is connected to a 2197 single DTE or another multi-user segment. 2199 A discontinuity may occur in the value when the 2200 value of object rptrMonitorPortLastChange changes. 2202 The approximate minimum time for rollover of this 2203 counter is 81 hours in a 10Mb/s repeater." 2204 REFERENCE 2205 "[IEEE 802.3 Mgt], 30.4.3.1.19, aSourceAddressChanges." 2206 ::= { rptrAddrTrackEntry 4 } 2208 rptrAddrTrackNewLastSrcAddress OBJECT-TYPE 2209 SYNTAX OptMacAddr 2210 MAX-ACCESS read-only 2211 STATUS current 2212 DESCRIPTION 2213 "This object is the SourceAddress of the last 2214 readable frame (i.e., counted by 2215 rptrMonitorPortReadableFrames) received by this 2216 port. If no frames have been received by this 2217 port since the agent began monitoring the port 2218 activity, the agent shall return a string of 2219 length zero." 2220 REFERENCE 2221 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2222 ::= { rptrAddrTrackEntry 5 } 2224 rptrAddrTrackCapacity OBJECT-TYPE 2225 SYNTAX Integer32 2226 MAX-ACCESS read-only 2227 STATUS current 2228 DESCRIPTION 2229 "The maximum number of addresses that can be 2230 detected on this port. This value indicates 2231 to the maximum number of entries in the 2232 rptrExtAddrTrackTable relative to this port. 2234 If this object has the value of 1, the agent 2235 implements only the LastSourceAddress mechanism 2236 described by RFC 1368 or RFC 1516." 2237 ::= { rptrAddrTrackEntry 6 } 2239 -- Table for multiple addresses per port 2241 rptrExtAddrTrackTable OBJECT-TYPE 2242 SYNTAX SEQUENCE OF RptrExtAddrTrackEntry 2243 MAX-ACCESS not-accessible 2244 STATUS current 2245 DESCRIPTION 2246 "A table to extend the address tracking table (i.e., 2247 rptrAddrTrackTable) with a list of source MAC 2248 addresses that were recently received on each port. 2249 The number of ports is the same as the number 2250 of entries in table rptrPortTable. The number of 2251 entries in this table depends on the agent/repeater 2252 implementation and the number of different 2253 addresses received on each port. 2255 The first entry for each port contains 2256 the same MAC address that is given by the 2257 rptrAddrTrackNewLastSrcAddress for that port. 2259 Entries in this table for a particular port are 2260 retained when that port is switched from one 2261 repeater to another. 2263 The ordering of MAC addresses listed for a 2264 particular port is implementation dependent." 2265 ::= { rptrAddrTrackPortInfo 2 } 2267 rptrExtAddrTrackEntry OBJECT-TYPE 2268 SYNTAX RptrExtAddrTrackEntry 2269 MAX-ACCESS not-accessible 2270 STATUS current 2271 DESCRIPTION 2272 "A row in the table of extended address tracking 2273 information for ports. Entries can not be directly 2274 created or deleted via SNMP operations." 2275 INDEX { rptrAddrTrackGroupIndex, 2276 rptrAddrTrackPortIndex, 2277 rptrExtAddrTrackMacIndex } 2278 ::= { rptrExtAddrTrackTable 1 } 2280 RptrExtAddrTrackEntry ::= SEQUENCE { 2281 rptrExtAddrTrackMacIndex Integer32, 2282 rptrExtAddrTrackSourceAddress MacAddress 2283 } 2285 rptrExtAddrTrackMacIndex OBJECT-TYPE 2286 SYNTAX Integer32 (1..2147483647) 2287 MAX-ACCESS not-accessible 2288 STATUS current 2289 DESCRIPTION 2290 "The index of a source MAC address seen on 2291 the port." 2292 ::= { rptrExtAddrTrackEntry 1 } 2294 rptrExtAddrTrackSourceAddress OBJECT-TYPE 2295 SYNTAX MacAddress 2296 MAX-ACCESS read-only 2297 STATUS current 2298 DESCRIPTION 2299 "The source MAC address from a readable frame 2300 (i.e., counted by rptrMonitorPortReadableFrames) 2301 recently received by the port." 2302 REFERENCE 2303 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2304 ::= { rptrExtAddrTrackEntry 2 } 2306 rptrAddrTrackReset OBJECT-TYPE 2307 SYNTAX INTEGER { 2308 noReset(1), 2309 reset(2) 2310 } 2311 MAX-ACCESS read-write 2312 STATUS current 2313 DESCRIPTION 2314 "Setting this object to reset(2) causes 2315 the agent to empty the contents of the 2316 rptrExtAddrTrackTable. The contents of 2317 the rptrAddrTrackTable are not affected. 2319 Setting this object to noReset(1) has no effect. 2320 The agent will always return the value noReset(1) 2321 when this object is read." 2322 ::= { rptrAddrTrackPortInfo 3 } 2324 -- The Repeater Top "N" Port Group 2326 -- The Repeater Top N Port group is used to prepare reports that 2327 -- describe a list of ports ordered by one of the statistics in the 2328 -- Repeater Monitor Port Table. The statistic chosen by the 2329 -- management station is sampled over a management 2330 -- station-specified time interval, making the report rate based. 2331 -- The management station also specifies the number of ports that 2332 -- are reported. 2333 -- 2334 -- The rptrTopNPortControlTable is used to initiate the generation 2335 -- of a report. The management station may select the parameters 2336 -- of such a report, such as which repeater, which statistic, how 2337 -- many ports, and the start & stop times of the sampling. When 2338 -- the report is prepared, entries are created in the 2339 -- rptrTopNPortTable associated with the relevent 2340 -- rptrTopNControlEntry. These entries are static for each report 2341 -- after it has been prepared. 2343 rptrTopNPortControlTable OBJECT-TYPE 2344 SYNTAX SEQUENCE OF RptrTopNPortControlEntry 2345 MAX-ACCESS not-accessible 2346 STATUS current 2347 DESCRIPTION 2348 "A table of control records for reports on the top `N' 2349 ports for the rate of a selected counter. The number 2350 of entries depends on the configuration of the agent. 2351 The maximum number of entries is implementation 2352 dependent." 2353 ::= { rptrTopNPortInfo 1 } 2355 rptrTopNPortControlEntry OBJECT-TYPE 2356 SYNTAX RptrTopNPortControlEntry 2357 MAX-ACCESS not-accessible 2358 STATUS current 2359 DESCRIPTION 2360 "A set of parameters that control the creation of a 2361 report of the top N ports according to several metrics." 2362 INDEX { rptrTopNPortControlIndex } 2363 ::= { rptrTopNPortControlTable 1 } 2365 RptrTopNPortControlEntry ::= SEQUENCE { 2366 rptrTopNPortControlIndex 2367 Integer32, 2368 rptrTopNPortRepeaterId 2369 Integer32, 2370 rptrTopNPortRateBase 2371 INTEGER, 2372 rptrTopNPortTimeRemaining 2373 Integer32, 2374 rptrTopNPortDuration 2375 Integer32, 2376 rptrTopNPortRequestedSize 2377 Integer32, 2378 rptrTopNPortGrantedSize 2379 Integer32, 2380 rptrTopNPortStartTime 2381 TimeStamp, 2382 rptrTopNPortOwner 2383 OwnerString, 2384 rptrTopNPortRowStatus 2385 RowStatus 2386 } 2388 rptrTopNPortControlIndex OBJECT-TYPE 2389 SYNTAX Integer32 (1 .. 65535) 2390 MAX-ACCESS read-only 2391 STATUS current 2392 DESCRIPTION 2393 "An index that uniquely identifies an entry in the 2394 rptrTopNPortControl table. Each such entry defines 2395 one top N report prepared for a repeater or system." 2396 ::= { rptrTopNPortControlEntry 1 } 2398 rptrTopNPortRepeaterId OBJECT-TYPE 2399 SYNTAX INTEGER (0..2147483647) 2400 MAX-ACCESS read-create 2401 STATUS current 2402 DESCRIPTION 2403 "Identifies the repeater for which a top N report will 2404 be prepared (see rptrInfoId). If the value of this 2405 object is positive, only ports assigned to this repeater 2406 will be used to form the list in which to order the 2407 Top N table. If this value is zero, all ports will be 2408 eligible for inclusion on the list. 2410 The value of this object may not be modified if the 2411 associated rptrTopNPortRowStatus object is equal to 2412 active(1)." 2413 ::= { rptrTopNPortControlEntry 2 } 2415 rptrTopNPortRateBase OBJECT-TYPE 2416 SYNTAX INTEGER { 2417 rptrMonitorPortReadableFrames(1), 2418 rptrMonitorPortReadableOctets(2), 2419 rptrMonitorPortFCSErrors(3), 2420 rptrMonitorPortAlignmentErrors(4), 2421 rptrMonitorPortFrameTooLongs(5), 2422 rptrMonitorPortShortEvents(6), 2423 rptrMonitorPortRunts(7), 2424 rptrMonitorPortCollisions(8), 2425 rptrMonitorPortLateEvents(9), 2426 rptrMonitorPortVeryLongEvents(10), 2427 rptrMonitorPortDataRateMismatches(11), 2428 rptrMonitorPortAutoPartitions(12), 2429 rptrMonitorPortTotalErrors(13), 2430 rptrMonitorPortIsolates(14), 2431 rptrMonitorPortSymbolErrors(15) 2432 } 2433 MAX-ACCESS read-create 2434 STATUS current 2435 DESCRIPTION 2436 "The monitored variable, which the rptrTopNPortRate 2437 variable is based upon. 2439 The value of this object may not be modified if 2440 the associated rptrTopNPortRowStatus object has 2441 a value of active(1)." 2442 ::= { rptrTopNPortControlEntry 3 } 2444 rptrTopNPortTimeRemaining OBJECT-TYPE 2445 SYNTAX Integer32 (0..2147483647) 2446 MAX-ACCESS read-create 2447 STATUS current 2448 DESCRIPTION 2449 "The number of seconds left in the report 2450 currently being collected. When this object 2451 is modified by the management station, a new 2452 collection is started, possibly aborting a 2453 currently running report. The new value is 2454 used as the requested duration of this report, 2455 which is loaded into the associated 2456 rptrTopNPortDuration object. 2458 When this object is set to a non-zero value, 2459 any associated rptrTopNPortEntries shall be 2460 made inaccessible by the agent. While the value 2461 of this object is non-zero, it decrements by one 2462 per second until it reaches zero. During this 2463 time, all associated rptrTopNPortEntries shall 2464 remain inaccessible. At the time that this object 2465 decrements to zero, the report is made accessible 2466 in the rptrTopNPortTable. Thus, the rptrTopNPort 2467 table needs to be created only at the end of the 2468 collection interval." 2469 DEFVAL { 0 } 2470 ::= { rptrTopNPortControlEntry 4 } 2472 rptrTopNPortDuration OBJECT-TYPE 2473 SYNTAX Integer32 (0..2147483647) 2474 MAX-ACCESS read-only 2475 STATUS current 2476 DESCRIPTION 2477 "The number of seconds that this report has 2478 collected during the last sampling interval, 2479 or if this report is currently being collected, 2480 the number of seconds that this report is being 2481 collected during this sampling interval. 2483 When the associated rptrTopNPortTimeRemaining 2484 object is set, this object shall be set by the 2485 agent to the same value and shall not be modified 2486 until the next time the rptrTopNPortTimeRemaining 2487 is set. 2489 This value shall be zero if no reports have been 2490 requested for this rptrTopNPortControlEntry." 2491 ::= { rptrTopNPortControlEntry 5 } 2493 rptrTopNPortRequestSize OBJECT-TYPE 2494 SYNTAX Integer32 2495 MAX-ACCESS read-create 2496 STATUS current 2497 DESCRIPTION 2498 "The maximum number of repeater ports requested 2499 for the Top N Table. 2501 When this object is created or modified, the 2502 agent should set rptrTopNPortGrantedSize as close 2503 to this object as is possible for the particular 2504 implementation and available resources." 2505 DEFVAL { 10 } 2506 ::= { rptrTopNPortControlEntry 6 } 2508 rptrTopNPortGrantedSize OBJECT-TYPE 2509 SYNTAX Integer32 (0..65535) 2510 MAX-ACCESS read-only 2511 STATUS current 2512 DESCRIPTION 2513 "The maximum number of repeater ports in the 2514 top N table. 2516 When the associated rptrTopNPortRequestedSize object is 2517 created or modified, the agent should set this object as 2518 closely to the requested value as is possible for the 2519 particular implementation and available resources. The 2520 agent must not lower this value except as a result of a 2521 set to the associated rptrTopNPortRequestedSize object." 2522 ::= { rptrTopNPortControlEntry 7 } 2524 rptrTopNPortStartTime OBJECT-TYPE 2525 SYNTAX TimeStamp 2526 MAX-ACCESS read-only 2527 STATUS current 2528 DESCRIPTION 2529 "The value of sysUpTime when this top N report was 2530 last started. In other words, this is the time that 2531 the associated rptrTopNPortTimeRemaining object was 2532 modified to start the requested report." 2533 ::= { rptrTopNPortControlEntry 8 } 2535 rptrTopNPortOwner OBJECT-TYPE 2536 SYNTAX OwnerString 2537 MAX-ACCESS read-create 2538 STATUS current 2539 DESCRIPTION 2540 "The entity that configured this entry and is 2541 using the resources assigned to it." 2542 ::= { rptrPortTopControlEntry 9 } 2544 rptrTopNPortRowStatus OBJECT-TYPE 2545 SYNTAX RowStatus 2546 MAX-ACCESS read-create 2547 STATUS current 2548 DESCRIPTION 2549 "The status of this row." 2550 ::= { rptrTopNPortControlEntry 10 } 2552 -- Top "N" reports 2554 rptrTopNPortTable OBJECT-TYPE 2555 SYNTAX SEQUENCE OF RptrTopNPortEntry 2556 MAX-ACCESS not-accesible 2557 STATUS current 2558 DESCRIPTION 2559 "A table of reports for the top `N' ports based on 2560 setting of associated control table entries. The 2561 maximum number of entries depends on the number 2562 of entries in table rptrTopNPortControlTable and 2563 the value of object rptrTopNPortGrantedSize for 2564 each entry. 2566 For each entry in the rptrTopNPortControlTable, 2567 repeater ports with the highest value of 2568 rptrTopNPortRate shall be placed in this table 2569 in decreasing order of that rate until there is 2570 no more room or until there are no more ports." 2571 ::= { rptrTopNPortInfo 2 } 2573 rptrTopNPortEntry OBJECT-TYPE 2574 SYNTAX RptrTopNPortEntry 2575 MAX-ACCESS not-accesible 2576 STATUS current 2577 DESCRIPTION 2578 "A set of statistics for a repeater port that is 2579 part of a top N report." 2580 INDEX { rptrTopNPortControlIndex, 2581 rptrTopNPortIndex } 2582 ::= { rptrTopNPortTable 1 } 2584 RptrTopNPortEntry ::= SEQUENCE { 2585 rptrTopNPortIndex 2586 Integer32, 2587 rptrTopNPortGroupIndex 2588 Integer32, 2589 rptrTopNPortPortIndex 2590 Integer32, 2591 rptrTopNPortRate 2592 Gauge32 2593 } 2595 rptrTopNPortIndex OBJECT-TYPE 2596 SYNTAX Integer32 (1..65535) 2597 MAX-ACCESS read-only 2598 STATUS current 2599 DESCRIPTION 2600 "An index that uniquely identifies an entry in 2601 the rptrTopNPort table among those in the same 2602 report. This index is between 1 and N, where N 2603 is the number of entries in this report. Increasing 2604 values of rptrTopNPortIndex shall be assigned to 2605 entries with decreasing values of rptrTopNPortRate 2606 until index N is assigned to the entry with the 2607 lowest value of rptrTopNPortRate or there are no 2608 more rptrTopNPortEntries. 2610 No ports are included in a report where their 2611 value of rptrTopNPortRate would be zero." 2612 ::= { rptrTopNPortEntry 1 } 2614 rptrTopNPortGroupIndex OBJECT-TYPE 2615 SYNTAX Integer32 (1..2147483647) 2616 MAX-ACCESS read-only 2617 STATUS current 2618 DESCRIPTION 2619 "This object identifes the group containing 2620 the port for this entry. (See also object 2621 type rptrGroupIndex.)" 2622 ::= { rptrTopNPortEntry 2 } 2624 rptrTopNPortPortIndex OBJECT-TYPE 2625 SYNTAX Integer32 (1..2147483647) 2626 MAX-ACCESS read-only 2627 STATUS current 2628 DESCRIPTION 2629 "The index of the repeater port. 2630 (See object type rptrPortIndex.)" 2631 ::= { rptrTopNPortEntry 3 } 2633 rptrTopNPortRate OBJECT-TYPE 2634 SYNTAX Gauge32 2635 MAX-ACCESS read-only 2636 STATUS current 2637 DESCRIPTION 2638 "The amount of change in the selected variable 2639 during this sampling interval for the identified 2640 port. The selected variable is that port's 2641 instance of the object selected by 2642 rptrTopNPortRateBase." 2643 ::= { rptrTopNPortEntry 4 } 2645 -- Notifications for use by Repeaters 2647 rptrHealth NOTIFICATION-TYPE 2648 OBJECTS { rptrOperStatus } 2649 STATUS deprecated 2650 DESCRIPTION 2651 "In a system containing a single managed repeater, 2652 the rptrHealth notification conveys information 2653 related to the operational status of the repeater. 2654 It is sent either when the value of 2655 rptrOperStatus changes, or upon completion of a 2656 non-disruptive test. 2658 The rptrHealth notification must contain the 2659 rptrOperStatus object. The agent may optionally 2660 include the rptrHealthText object in the varBind 2661 list. See the rptrOperStatus and rptrHealthText 2662 objects for descriptions of the information that 2663 is sent. 2665 The agent must throttle the generation of 2666 consecutive rptrHealth traps so that there is at 2667 least a five-second gap between traps of this 2668 type. When traps are throttled, they are dropped, 2669 not queued for sending at a future time. (Note 2670 that 'generating' a trap means sending to all 2671 configured recipients.)" 2672 REFERENCE 2673 "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth 2674 notification." 2675 ::= { snmpDot3RptrMgt 0 1 } 2677 rptrGroupChange NOTIFICATION-TYPE 2678 OBJECTS { rptrGroupIndex } 2679 STATUS deprecated 2680 DESCRIPTION 2681 "In a system containing a single managed repeater, 2682 this notification is sent when a change occurs in the 2683 group structure of the repeater. This occurs only 2684 when a group is logically or physically removed 2685 from or added to a repeater. The varBind list 2686 contains the identifier of the group that was 2687 removed or added. 2689 The agent must throttle the generation of 2690 consecutive rptrGroupChange traps for the same 2691 group so that there is at least a five-second gap 2692 between traps of this type. When traps are 2693 throttled, they are dropped, not queued for 2694 sending at a future time. (Note that 'generating' 2695 a trap means sending to all configured 2696 recipients.)" 2697 REFERENCE 2698 "[IEEE 802.3 Mgt], 30.4.1.3.3, nGroupMapChange 2699 notification." 2700 ::= { snmpDot3RptrMgt 0 2 } 2702 rptrResetEvent NOTIFICATION-TYPE 2703 OBJECTS { rptrOperStatus } 2704 STATUS deprecated 2705 DESCRIPTION 2706 "In a system containing a single managed repeater-unit, 2707 the rptrResetEvent notification conveys information 2708 related to the operational status of the repeater. 2709 This trap is sent on completion of a repeater 2710 reset action. A repeater reset action is defined 2711 as an a transition to the START state of Fig 9-2 2712 in section 9 [IEEE 802.3 Std], when triggered by a 2713 management command (e.g., an SNMP Set on the 2714 rptrReset object). 2716 The agent must throttle the generation of 2717 consecutive rptrResetEvent traps so that there is 2718 at least a five-second gap between traps of this 2719 type. When traps are throttled, they are dropped, 2720 not queued for sending at a future time. (Note 2721 that 'generating' a trap means sending to all 2722 configured recipients.) 2724 The rptrResetEvent trap is not sent when the agent 2725 restarts and sends an SNMP coldStart or warmStart 2726 trap. However, it is recommended that a repeater 2727 agent send the rptrOperStatus object as an 2728 optional object with its coldStart and warmStart 2729 trap PDUs. 2731 The rptrOperStatus object must be included in the 2732 varbind list sent with this trap. The agent may 2733 optionally include the rptrHealthText object as 2734 well." 2735 REFERENCE 2736 "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset 2737 notification." 2738 ::= { snmpDot3RptrMgt 0 3 } 2740 -- Conformance information 2742 snmpRptrModConf 2743 OBJECT IDENTIFIER ::= { snmpRptrMod 1 } 2744 snmpRptrModCompls 2745 OBJECT IDENTIFIER ::= { snmpRptrModConf 1 } 2746 snmpRptrModObjGrps 2747 OBJECT IDENTIFIER ::= { snmpRptrModConf 2 } 2749 snmpRptrModNotGrps 2750 OBJECT IDENTIFIER ::= { snmpRptrModConf 3 } 2752 -- Object groups 2754 snmpRptrGrpBasic OBJECT-GROUP 2755 OBJECTS { rptrGroupCapacity, 2756 rptrOperStatus, 2757 rptrHealthText, 2758 rptrReset, 2759 rptrNonDisruptTest, 2760 rptrTotalPartitionedPorts, 2762 rptrGroupIndex, 2763 rptrGroupDescr, 2764 rptrGroupObjectID, 2765 rptrGroupOperStatus, 2766 rptrGroupLastOperStatusChange, 2767 rptrGroupPortCapacity, 2769 rptrPortGroupIndex, 2770 rptrPortIndex, 2771 rptrPortAdminStatus, 2772 rptrPortAutoPartitionState, 2773 rptrPortOperStatus } 2774 STATUS obsolete 2775 DESCRIPTION 2776 "Basic group from RFC 1368. 2778 NOTE: this object group is OBSOLETE and replaced 2779 with snmpRptrGrpBasicRS1." 2780 ::= { snmpRptrModObjGrps 1 } 2782 snmpRptrGrpMonitor OBJECT-GROUP 2783 OBJECTS { rptrMonitorTransmitCollisions, 2785 rptrMonitorGroupIndex, 2786 rptrMonitorGroupTotalFrames, 2787 rptrMonitorGroupTotalOctets, 2788 rptrMonitorGroupTotalErrors, 2790 rptrMonitorPortGroupIndex, 2791 rptrMonitorPortIndex, 2792 rptrMonitorPortReadableFrames, 2793 rptrMonitorPortReadableOctets, 2794 rptrMonitorPortFCSErrors, 2795 rptrMonitorPortAlignmentErrors, 2796 rptrMonitorPortFrameTooLongs, 2797 rptrMonitorPortShortEvents, 2798 rptrMonitorPortRunts, 2799 rptrMonitorPortCollisions, 2800 rptrMonitorPortLateEvents, 2801 rptrMonitorPortVeryLongEvents, 2802 rptrMonitorPortDataRateMismatches, 2803 rptrMonitorPortAutoPartitions, 2804 rptrMonitorPortTotalErrors } 2805 STATUS obsolete 2806 DESCRIPTION 2807 "Monitor group from RFC 1368. 2809 NOTE: this object group is OBSOLETE and replaced 2810 with snmpRptrGrpBasicRS1." 2811 ::= { snmpRptrModObjGrps 2 } 2813 snmpRptrGrpAddrTrack OBJECT-GROUP 2814 OBJECTS { rptrAddrTrackGroupIndex, 2815 rptrAddrTrackPortIndex, 2816 rptrAddrTrackLastSourceAddress, 2817 rptrAddrTrackSourceAddrChanges, 2818 rptrAddrTrackNewLastSrcAddress } 2819 STATUS obsolete 2820 DESCRIPTION 2821 "Address tracking group from RFC 1368. 2823 NOTE: this object group is OBSOLETE and replaced 2824 with snmpRptrGrpAddrTrackNewSrcAddr." 2825 ::= { snmpRptrModObjGrps 3 } 2827 snmpRptrGrpAddrTrackNewSrcAddr OBJECT-GROUP 2828 OBJECTS { rptrAddrTrackGroupIndex, 2829 rptrAddrTrackPortIndex, 2830 rptrAddrTrackSourceAddrChanges, 2831 rptrAddrTrackNewLastSrcAddress } 2832 STATUS deprecated 2833 DESCRIPTION 2834 "Address tracking group from RFC 1516. 2836 NOTE: this object group is DEPRECATED and replaced 2837 with snmpRptrGrpAddrTrackRSN." 2839 ::= { snmpRptrModObjGrps 4 } 2841 snmpRptrGrpBasicRS1 OBJECT-GROUP 2842 OBJECTS { rptrOperStatus, 2843 rptrReset, 2844 rptrTotalPartitionedPorts, 2846 rptrGroupIndex, 2847 rptrGroupObjectID, 2848 rptrGroupOperStatus, 2849 rptrGroupLastOperStatusChange, 2851 rptrPortGroupIndex, 2852 rptrPortIndex, 2853 rptrPortAdminStatus, 2854 rptrPortAutoPartitionState, 2855 rptrPortOperStatus } 2856 STATUS deprecated 2857 DESCRIPTION 2858 "Basic group for a system with exactly-one 2859 repeater-unit in restart version of the MIB 2860 module. 2862 NOTE: this object group is DEPRECATED and replaced 2863 with snmpRptrGrpBasicRSN." 2864 ::= { snmpRptrModObjGrps 5 } 2866 snmpRptrGrpBasicRSN OBJECT-GROUP 2867 OBJECTS { rptrInfoOperStatus, 2868 rptrInfoLastChange, 2869 rptrInfoReset, 2870 rptrInfoPorts, 2871 rptrInfoOperPorts, 2872 rptrInfoPartPorts, 2874 rptrGroupObjectID, 2875 rptrGroupOperStatus, 2876 rptrGroupLastOperStatusChange, 2878 rptrPortAdminStatus, 2879 rptrPortAutoPartitionState, 2880 rptrPortOperStatus, 2881 rptrPortOperRptrId } 2882 STATUS current 2883 DESCRIPTION 2884 "Basic group for a system with one or more 2885 repeater-units in restart version of the MIB 2886 module." 2887 ::= { snmpRptrModObjGrps 6 } 2889 snmpRptrGrpMonitorRS1 OBJECT-GROUP 2890 OBJECTS { rptrMonitorTransmitCollisions, 2892 rptrMonitorPortReadableFrames, 2893 rptrMonitorPortReadableOctets, 2894 rptrMonitorPortFCSErrors, 2895 rptrMonitorPortAlignmentErrors, 2896 rptrMonitorPortFrameTooLongs, 2897 rptrMonitorPortShortEvents, 2898 rptrMonitorPortRunts, 2899 rptrMonitorPortCollisions, 2900 rptrMonitorPortLateEvents, 2901 rptrMonitorPortVeryLongEvents, 2902 rptrMonitorPortDataRateMismatches, 2903 rptrMonitorPortAutoPartitions, 2904 rptrMonitorPortTotalErrors } 2905 STATUS deprecated 2906 DESCRIPTION 2907 "Monitor group for a system with exactly-one 2908 repeater-unit in restart version of the MIB 2909 module. 2911 NOTE: this object group is DEPRECATED and replaced 2912 with snmpRptrGrpMonitorRSN." 2913 ::= { snmpRptrModObjGrps 7 } 2915 snmpRptrGrpMonitorRSN OBJECT-GROUP 2916 OBJECTS { rptrMonTxColls, 2917 rptrMonTotalFrames, 2918 rptrMonTotalOctets, 2919 rptrMonTotalErrors, 2921 rptrMonitorPortReadableFrames, 2922 rptrMonitorPortReadableOctets, 2923 rptrMonitorPortFCSErrors, 2924 rptrMonitorPortAlignmentErrors, 2925 rptrMonitorPortFrameTooLongs, 2926 rptrMonitorPortShortEvents, 2927 rptrMonitorPortRunts, 2928 rptrMonitorPortCollisions, 2929 rptrMonitorPortLateEvents, 2930 rptrMonitorPortVeryLongEvents, 2931 rptrMonitorPortDataRateMismatches, 2932 rptrMonitorPortAutoPartitions, 2933 rptrMonitorPortTotalErrors, 2934 rptrMonitorPortLastChange } 2935 STATUS current 2936 DESCRIPTION 2937 "Basic group for a system with one or more 2938 repeater-units in restart version of the MIB 2939 module." 2940 ::= { snmpRptrModObjGrps 8 } 2942 snmpRptrGrpAddrTrackRSN OBJECT-GROUP 2943 OBJECTS { rptrAddrTrackSourceAddrChanges, 2944 rptrAddrTrackNewLastSrcAddress } 2945 STATUS current 2946 DESCRIPTION 2947 "Address tracking group for a system with one 2948 or more repeater-units in restart version of 2949 the MIB module." 2950 ::= { snmpRptrModObjGrps 9 } 2952 snmpRptrGrpExtAddrTrackRSN OBJECT-GROUP 2953 OBJECTS { rptrExtAddrTrackSourceAddress } 2954 STATUS current 2955 DESCRIPTION 2956 "Extended address tracking group for a system 2957 with one or more repeater-units in restart 2958 version of the MIB module." 2959 ::= { snmpRptrModObjGrps 10 } 2961 snmpRptrGrpTopNPort OBJECT-GROUP 2962 OBJECTS { rptrTopNPortRepeaterId, 2963 rptrTopNPortRateBase, 2964 rptrTopNPortTimeRemaining, 2965 rptrTopNPortDuration, 2966 rptrTopNPortRequestedSize, 2967 rptrTopNPortGrantedSize, 2968 rptrTopNPortStartTime, 2969 rptrTopNPortOwner, 2970 rptrTopNPortRowStatus, 2971 rptrTopNPortGroupIndex, 2972 rptrTopNPortPortIndex, 2973 rptrTopNPortRate } 2974 STATUS current 2975 DESCRIPTION 2976 "Top `N' group for repeater ports." 2977 ::= { snmpRptrModObjGrps 11 } 2979 -- Notification groups 2981 -- ?? later 2983 -- Compliances 2985 snmpRptrModCompl MODULE-COMPLIANCE 2986 STATUS obsolete 2987 DESCRIPTION 2988 "Compliance for RFC 1368. 2990 NOTE: this module compliance is OBSOLETE and 2991 replaced by snmpRptrModComplRSN." 2992 MODULE -- this module 2993 MANDATORY-GROUPS { snmpRptrGrpBasic } 2994 -- optional groups 2995 GROUP snmpRptrGrpMonitor 2996 DESCRIPTION 2997 "..." 2998 GROUP snmpRptrGrpAddrTrack 2999 DESCRIPTION 3000 "..." 3001 ::= { snmpRptrModCompls 1 } 3003 snmpRptrModComplNewSrcAddr MODULE-COMPLIANCE 3004 STATUS obsolete 3005 DESCRIPTION 3006 "Compliance for RFC 1516. 3008 NOTE: this module compliance is OBSOLETE and 3009 replaced by snmpRptrModComplRSN." 3010 MODULE -- this module 3011 MANDATORY-GROUPS { snmpRptrGrpBasic } 3012 -- optional groups 3013 GROUP snmpRptrGrpMonitor 3014 DESCRIPTION 3015 "..." 3016 GROUP snmpRptrGrpAddrTrack 3017 DESCRIPTION 3018 "..." 3019 ::= { snmpRptrModCompls 2 } 3021 snmpRptrModComplRS1 MODULE-COMPLIANCE 3022 STATUS deprecated 3023 DESCRIPTION 3024 "Compliance for the `restart version' of the 3025 MIB module for a system with exactly-one 3026 repeater-unit. 3028 NOTE: this module compliance is DEPRECATED and 3029 replaced by snmpRptrModComplRSN." 3030 MODULE -- this module 3031 MANDATORY-GROUPS { snmpRptrGrpBasicRS1 } 3032 -- Optional groups 3033 GROUP snmpRptrGrpMonitorRS1 3034 DESCRIPTION 3035 "..." 3036 GROUP snmpRptrGrpAddrTrackRSN 3037 DESCRIPTION 3038 "..." 3039 ::= { snmpRptrModCompls 3 } 3041 snmpRptrModComplRSN MODULE-COMPLIANCE 3042 STATUS current 3043 DESCRIPTION 3044 "Compliance for the `restart version' of the 3045 MIB module for a system with one or more 3046 repeater-units." 3047 MODULE -- this module 3048 MANDATORY-GROUPS { snmpRptrGrpBasicRSN } 3049 -- Optional groups 3050 GROUP snmpRptrGrpMonitorRSN 3051 DESCRIPTION 3052 "..." 3053 GROUP snmpRptrGrpAddrTrackRSN 3054 DESCRIPTION 3055 "..." 3056 GROUP snmpRptrGrpExtAddrTrackRSN 3057 DESCRIPTION 3058 "..." 3060 ::= { snmpRptrModCompls 4 } 3062 END 3063 4. References 3065 [1] IEEE 802.3/ISO 8802-3 Information processing systems - 3066 Local area networks - Part 3: Carrier sense multiple 3067 access with collision detection (CSMA/CD) access method 3068 and physical layer specifications, 1993. 3070 [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium 3071 Attachment Units and Repeater for 100 Mb/s Operation, 3072 Type 100BASE-T," Sections 21 through 29, Supplement to 3073 IEEE Std 802.3, October 26, 1995. 3075 [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, 3076 Supplement to IEEE Std 802.3, October 26, 1995. 3078 [4] Romascanu, D., and K. de Graaf, "Definitions of Managed 3079 Objects for IEEE 802.3 Medium Attachment Units (MAUs)", 3080 November 1995. 3082 [5] McCloghrie, K., and M. Rose, Editors, "Management 3083 Information Base for Network Management of TCP/IP-based 3084 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 3085 Performance Systems International, March 1991.