idnits 2.17.1 draft-ietf-hubmib-repeater-dev-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 5) being 59 lines 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 90 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [5], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1557 has weird spacing: '... of the parti...' == Line 2210 has weird spacing: '...maximum numbe...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (14 February 1996) is 10299 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 3116 looks like a reference -- Missing reference section? '2' on line 3121 looks like a reference -- Missing reference section? '3' on line 3126 looks like a reference -- Missing reference section? '5' on line 3133 looks like a reference -- Missing reference section? '4' on line 3129 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 4 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft 802.3 Repeater MIB 14 February 1996 4 Definitions of Managed Objects 5 for IEEE 802.3 Repeater Devices 7 14 February 1996 9 11 Dan Romascanu 12 Madge Networks (Israel) Ltd. 13 dan@lannet.com 15 Kathryn de Graaf 16 3Com Corporation 17 kdegraaf@isd.3com.com 19 Status of this Memo 21 This document is an Internet-Draft. Internet-Drafts are 22 working documents of the Internet Engineering Task Force 23 (IETF), its areas, and its working groups. Note that other 24 groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six 28 months and may be updated, replaced, or obsoleted by other 29 documents at any time. It is inappropriate to use Internet- 30 Drafts as reference material or to cite them other than as a 31 "work in progress". 33 To learn the current status of any Internet-Draft, please 34 check the "1id-abstracts.txt" listing contained in the 35 Internet-Drafts Shadow Directories on ds.internic.net (US East 36 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 37 or munnari.oz.au (Pacific Rim). 39 Abstract 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management 43 protocols in the Internet community. In particular, it 44 defines objects for managing IEEE 802.3 10 and 100 Mb/second 45 baseband repeaters based on IEEE Std 802.3 Section 30, "10 & 46 100 Mb/s Management," October 26, 1995. 48 This memo does not specify a standard for the Internet 49 community. 51 1. The SNMPv2 Network Management Framework 53 The SNMPv2 Network Management Framework consists of several 54 major components. They include: 56 o RFC 1902 which defines the SMI, the mechanisms used for 57 describing and naming objects for the purpose of 58 management. 60 o STD 17, RFC 1213 defines MIB-II, the core set of managed 61 objects for the Internet suite of protocols. 63 o RFC 1905 which defines the protocol used for network 64 access to managed objects. 66 The Framework permits new objects to be defined for the 67 purpose of experimentation and evaluation. 69 1.1. Object Definitions 71 Managed objects are accessed via a virtual information store, 72 termed the Management Information Base or MIB. Objects in the 73 MIB are defined using the subset of Abstract Syntax Notation 74 One (ASN.1) defined in the SMI. In particular, each object 75 type is named by an OBJECT IDENTIFIER, an administratively 76 assigned name. The object type together with an object 77 instance serves to uniquely identify a specific instantiation 78 of the object. For human convenience, we often use a textual 79 string, termed the descriptor, to refer to the object type. 81 2. Overview 83 Instances of the object types defined in this memo represent 84 attributes of an IEEE 802.3 (Ethernet-like) repeater, as 85 defined by Section 9, "Repeater Unit for 10 Mb/s Baseband 86 Networks" in the IEEE 802.3/ISO 8802-3 CSMA/CD standard [1], 87 and Section 27, "Repeater for 100 Mb/s Baseband Networks" in 88 the IEEE Standard 802.3u-1995 [2]. 90 These Repeater MIB objects may be used to manage non-standard 91 repeater-like devices, but defining objects to describe 92 implementation-specific properties of non-standard repeater- 93 like devices is outside the scope of this memo. 95 The definitions presented here are based on Section 30.4, 96 "Layer Management for 10 and 100 Mb/s Baseband Repeaters" and 97 Annex 30A, "GDMO Specificataions for 802.3 managed objects" of 98 [3]. 100 Implementors of these MIB objects should note that [3] 101 explicitly describes when, where, and how various repeater 102 attributes are measured. The IEEE document also describes the 103 effects of repeater actions that may be invoked by 104 manipulating instances of the MIB objects defined here. 106 The counters in this document are defined to be the same as 107 those counters in [3], with the intention that the same 108 instrumentation can be used to implement both the IEEE and 109 IETF management standards. 111 2.1. Structure of the MIB 113 Objects in this MIB are arranged into MIB groups. Each MIB 114 group is organized as a set of related objects. 116 2.1.1. The Basic Group Definitions 118 This group contains the objects which are applicable to all 119 repeaters. It contains status, parameter and control objects 120 for each repeater within the managed system, for the port 121 groups within the system, and for the individual ports 122 themselves. 124 2.1.2. The Monitor Group Definitions 126 This group contains monitoring statistics for each repeater 127 within the system and for individual ports. 129 2.1.3. The Address Tracking Group Definitions 131 This group contains objects for tracking the MAC addresses of 132 the DTEs attached to the ports within the system. 134 2.1.4. The Top N Group Definitions 136 This group contains objects for tracking the ports with the 137 most activity within the system or within particular 138 repeaters. 140 2.2. Relationship to Other MIBs 142 2.2.1. Relationship to RFC 1516 144 This MIB is intended as a superset of that defined by RFC 145 1516, which will go to historic status. This MIB includes all 146 of the objects contained in that MIB, plus some additional 147 ones, mainly for support for multiple repeaters and for 148 100BASE-T management. Certain objects have been deprecated; 149 in particular, those scalar objects used for managing a single 150 repeater are now of minimal use since they are duplicated in 151 the rptrInfoTable and rptrMonitorTable definitions. 153 2.2.2. Relationship to MIB-II 155 It is assumed that a repeater implementing this MIB will also 156 implement (at least) the 'system' group defined in MIB-II [5]. 158 2.2.2.1. Relationship to the 'system' group 160 In MIB-II, the 'system' group is defined as being mandatory 161 for all systems such that each managed entity contains one 162 instance of each object in the 'system' group. Thus, those 163 objects apply to the entity even if the entity's sole 164 functionality is management of repeaters. 166 2.2.2.2. Relationship to the 'interfaces' group 168 In MIB-II, the 'interfaces' group is defined as being 169 mandatory for all systems and contains information on an 170 entity's interfaces, where each interface is thought of as 171 being attached to a 'subnetwork'. (Note that this term is not 172 to be confused with 'subnet' which refers to an addressing 173 partitioning scheme used in the Internet suite of protocols.) 175 This Repeater MIB uses the notion of ports on a repeater. The 176 concept of a MIB-II interface has NO specific relationship to 177 a repeater's port. Therefore, the 'interfaces' group applies 178 only to the one (or more) network interfaces on which the 179 entity managing the repeater sends and receives management 180 protocol operations, and does not apply to the repeater's 181 ports. 183 This is consistent with the physical-layer nature of a 184 repeater. A repeater is a bitwise store-and-forward device. 185 It recognizes activity and bits, but does not process incoming 186 data based on any packet-related information (such as checksum 187 or addresses). A repeater has no MAC address, no MAC 188 implementation, and does not pass packets up to higher-level 189 protocol entities for processing. 191 (When a network management entity is observing a repeater, it 192 may appear as though the repeater is passing packets to a 193 higher-level protocol entity. However, this is only a means 194 of implementing management, and this passing of management 195 information is not part of the repeater functionality.) 196 3. Definitions 198 SNMP-REPEATER-MIB DEFINITIONS ::= BEGIN 200 IMPORTS 201 experimental, 202 Counter32, Counter64, Integer32, Gauge32, 203 TimeTicks, OBJECT-TYPE, 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 209 FROM SNMPv2-CONF 210 -- mib-2 211 -- FROM RFC1213-MIB 212 OwnerString 213 FROM RFC1271-MIB; 215 snmpRptrMod MODULE-IDENTITY 216 LAST-UPDATED "9602140000Z" 217 ORGANIZATION "IETF HUB MIB Working Group" 218 CONTACT-INFO 219 "WG E-mail: hubmib@hprnd.rose.hp.com 221 Chair: Dan Romascanu 222 Postal: Madge Networks (Israel) 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@isd.3com.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 5 } 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 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 rptrInfoReset 896 INTEGER, 897 rptrInfoNonDisruptTest 898 INTEGER, 899 rptrInfoPartitionedPorts 900 Gauge32, 901 rptrInfoLastChange 902 TimeStamp 903 } 905 rptrInfoId OBJECT-TYPE 906 SYNTAX Integer32 (1..2147483647) 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "This object identifies the repeater for which 911 this entry contains information." 912 ::= { rptrInfoEntry 1 } 914 rptrInfoRptrType OBJECT-TYPE 915 SYNTAX INTEGER { 916 other(1), -- undefined or unknown 917 tenMb(2), 918 onehundredMbClassI(3), 919 onehundredMbClassII(4) 920 } 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "The rptrInfoRptrType returns a value that identifies 925 the CSMA/CD repeater type." 926 REFERENCE 927 "[IEEE 802.3 Mgt], 30.4.1.1.2, aRepeaterType." 928 ::= { rptrInfoEntry 2 } 930 rptrInfoOperStatus OBJECT-TYPE 931 SYNTAX INTEGER { 932 other(1), 933 ok(2), 934 failure(3) 935 } 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "The rptrInfoOperStatus object indicates the 940 operational state of the repeater." 941 REFERENCE 942 "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState." 943 ::= { rptrInfoEntry 3 } 945 rptrInfoReset OBJECT-TYPE 946 SYNTAX INTEGER { 947 noReset(1), 948 reset(2) 949 } 950 MAX-ACCESS read-write 951 STATUS current 952 DESCRIPTION 953 "Setting this object to reset(2) causes a 954 transition to the START state of Fig 9-2 in 955 section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, 956 and to the START state of Fig 27-2 in section 27 957 of that standard for a 100Mb/s repeater. 959 Setting this object to noReset(1) has no effect. 960 The agent will always return the value noReset(1) 961 when this object is read. 963 After receiving a request to set this variable to 964 reset(2), the agent is allowed to delay the reset 965 for a short period. For example, the implementor 966 may choose to delay the reset long enough to allow 967 the SNMP response to be transmitted. In any 968 event, the SNMP response must be transmitted. 970 This action does not reset the management counters 971 defined in this document nor does it affect the 972 portAdminStatus parameters. Included in this 973 action is the execution of a disruptive Self-Test 974 with the following characteristics: a) The nature 975 of the tests is not specified. b) The test resets 976 the repeater but without affecting management 977 information about the repeater. c) The test does 978 not inject packets onto any segment. d) Packets 979 received during the test may or may not be 980 transferred. e) The test does not interfere with 981 management functions. 983 After performing this self-test, the agent will 984 update the repeater health information (including 985 rptrInfoOperStatus), and send a rptrInfoHealth trap." 986 REFERENCE 987 "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." 988 ::= { rptrInfoEntry 4 } 990 rptrInfoNonDisruptTest OBJECT-TYPE 991 SYNTAX INTEGER { 992 noSelfTest(1), 993 selfTest(2) 994 } 995 MAX-ACCESS read-write 996 STATUS current 997 DESCRIPTION 998 "Setting this object to selfTest(2) causes the 999 repeater to perform a agent-specific, non- 1000 disruptive self-test that has the following 1001 characteristics: a) The nature of the tests is 1002 not specified. b) The test does not change the 1003 state of the repeater or management information 1004 about the repeater. c) The test does not inject 1005 packets onto any segment. d) The test does not 1006 prevent the relay of any packets. e) The test 1007 does not interfere with management functions. 1009 After performing this test, the agent will update 1010 the repeater health information (including 1011 rptrInfoOperStatus) and send a rptrInfoHealth trap. 1013 Note that this definition allows returning an 1014 'okay' result after doing a trivial test. 1016 Setting this object to noSelfTest(1) has no 1017 effect. The agent will always return the value 1018 noSelfTest(1) when this object is read." 1019 REFERENCE 1020 "[IEEE 802.3 Mgt], 30.4.1.2.2, 1021 acExecuteNonDisruptiveSelfTest." 1022 ::= { rptrInfoEntry 5 } 1024 rptrInfoPartitionedPorts OBJECT-TYPE 1025 SYNTAX Gauge32 1026 MAX-ACCESS read-only 1027 STATUS current 1028 DESCRIPTION 1029 "This object returns the total number of ports in 1030 the repeater whose current state meets all three 1031 of the following criteria: rptrPortOperStatus 1032 does not have the value notPresent(3), 1033 rptrPortAdminStatus is enabled(1), and 1034 rptrPortAutoPartitionState is autoPartitioned(2)." 1035 ::= { rptrInfoEntry 6 } 1037 rptrInfoLastChange OBJECT-TYPE 1038 SYNTAX TimeStamp 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "The value of sysUpTime when any of the following 1043 conditions occurred: 1045 1) agent cold- or warm-started; 1046 2) this instance of repeater was created 1047 (such as when a device or module was 1048 added to the system); 1049 3) a change in the value of rptrInfoOperStatus; 1050 4) ports were added or removed as members of 1051 the repeater; or 1052 5) any of the counters associated with this 1053 repeater had a discontinuity." 1054 ::= { rptrInfoEntry 7 } 1056 -- 1057 -- Old version of statistics at the repeater level. 1058 -- 1059 -- Performance monitoring statistics for the repeater 1060 -- 1061 -- In a system containing a single managed repeater-unit, 1062 -- the statistics object for the repeater-unit. 1064 -- The objects contained under the rptrMonitorRptrInfo subtree are 1065 -- intended for backwards compatibility with implementations of 1066 -- RFC 1516. In newer implementations (both single- and 1067 -- multiple-repeater implementations), the rptrMonitorTable will 1068 -- be implemented. It is the preferred source of this information, 1069 -- as it contains the values for all repeaters managed by the 1070 -- agent. In all cases, the objects in the rptrMonitorRptrInfo 1071 -- subtree are duplicates of the corresponding objects in the 1072 -- first entry of the rptrMonitorTable. 1074 rptrMonitorTransmitCollisions OBJECT-TYPE 1075 SYNTAX Counter32 1076 MAX-ACCESS read-only 1077 STATUS deprecated 1078 DESCRIPTION 1079 "For a clause 9 (10Mb/s) repeater, this counter 1080 is incremented every time the repeater state 1081 machine enters the TRANSMIT COLLISION state 1082 from any state other than ONE PORT LEFT 1083 (Ref: Fig 9-2 [IEEE 802.3 Std]). 1085 For a clause 27 repeater, this counter is 1086 incremented every time the repeater core state 1087 diagram enters the Jam state as a result of 1088 Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). 1090 The approximate minimum time for rollover of this 1091 counter is 16 hours in a 10Mb/s repeater and 1.6 1092 hours in a 100Mb/s repeater." 1093 REFERENCE 1094 "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions." 1095 ::= { rptrMonitorRptrInfo 1 } 1097 -- Statistics at the group level. 1098 -- 1099 -- In a system containing a single managed repeater-unit, 1100 -- the statistics objects for each group. 1102 rptrMonitorGroupTable OBJECT-TYPE 1103 SYNTAX SEQUENCE OF RptrMonitorGroupEntry 1104 MAX-ACCESS not-accessible 1105 STATUS deprecated 1106 DESCRIPTION 1107 "Table of performance and error statistics for the 1108 groups within the repeater. The number of entries 1109 is the same as that in the rptrGroupTable." 1110 ::= { rptrMonitorGroupInfo 1 } 1112 rptrMonitorGroupEntry OBJECT-TYPE 1113 SYNTAX RptrMonitorGroupEntry 1114 MAX-ACCESS not-accessible 1115 STATUS deprecated 1116 DESCRIPTION 1117 "An entry in the table, containing total 1118 performance and error statistics for a single 1119 group. Regular retrieval of the information in 1120 this table provides a means of tracking the 1121 performance and health of the networked devices 1122 attached to this group's ports. 1124 The counters in this table are redundant in the 1125 sense that they are the summations of information 1126 already available through other objects. However, 1127 these sums provide a considerable optimization of 1128 network management traffic over the otherwise 1129 necessary retrieval of the individual counters 1130 included in each sum. 1132 Note: Group-level counters are 1133 deprecated in this MIB. It is recommended 1134 that management applications instead use 1135 the repeater-level counters contained in 1136 the rptrMonTable." 1137 INDEX { rptrMonitorGroupIndex } 1138 ::= { rptrMonitorGroupTable 1 } 1140 RptrMonitorGroupEntry ::= 1141 SEQUENCE { 1142 rptrMonitorGroupIndex 1143 Integer32, 1144 rptrMonitorGroupTotalFrames 1145 Counter32, 1146 rptrMonitorGroupTotalOctets 1147 Counter32, 1148 rptrMonitorGroupTotalErrors 1149 Counter32 1150 } 1152 rptrMonitorGroupIndex OBJECT-TYPE 1153 SYNTAX Integer32 (1..2147483647) 1154 MAX-ACCESS read-only 1155 STATUS deprecated 1156 DESCRIPTION 1157 "This object identifies the group within the 1158 repeater for which this entry contains 1159 information." 1160 ::= { rptrMonitorGroupEntry 1 } 1162 rptrMonitorGroupTotalFrames OBJECT-TYPE 1163 SYNTAX Counter32 1164 MAX-ACCESS read-only 1165 STATUS deprecated 1166 DESCRIPTION 1167 "The total number of frames of valid frame length 1168 that have been received on the ports in this group 1169 and for which the FCSError and CollisionEvent 1170 signals were not asserted. This counter is the 1171 summation of the values of the 1172 rptrMonitorPortReadableFrames counters for all of 1173 the ports in the group. 1175 This statistic provides one of the parameters 1176 necessary for obtaining the packet error rate. 1177 The approximate minimum time for rollover of this 1178 counter is 80 hours in a 10Mb/s repeater." 1179 ::= { rptrMonitorGroupEntry 2 } 1181 rptrMonitorGroupTotalOctets OBJECT-TYPE 1182 SYNTAX Counter32 1183 MAX-ACCESS read-only 1184 STATUS deprecated 1185 DESCRIPTION 1186 "The total number of octets contained in the valid 1187 frames that have been received on the ports in 1188 this group. This counter is the summation of the 1189 values of the rptrMonitorPortReadableOctets 1190 counters for all of the ports in the group. 1192 This statistic provides an indicator of the total 1193 data transferred. The approximate minimum time 1194 for rollover of this counter is 58 minutes in a 1195 10Mb/s repeater." 1196 ::= { rptrMonitorGroupEntry 3 } 1198 rptrMonitorGroupTotalErrors OBJECT-TYPE 1199 SYNTAX Counter32 1200 MAX-ACCESS read-only 1201 STATUS deprecated 1202 DESCRIPTION 1203 "The total number of errors which have occurred on 1204 all of the ports in this group. This counter is 1205 the summation of the values of the 1206 rptrMonitorPortTotalErrors counters for all of the 1207 ports in the group." 1208 ::= { rptrMonitorGroupEntry 4 } 1210 -- Statistics at the port level. 1211 -- 1213 rptrMonitorPortTable OBJECT-TYPE 1214 SYNTAX SEQUENCE OF RptrMonitorPortEntry 1215 MAX-ACCESS not-accessible 1216 STATUS current 1217 DESCRIPTION 1218 "Table of performance and error statistics for the 1219 ports. The number of entries is the same as that 1220 in the rptrPortTable. 1222 The columnar object rptrMonitorPortLastChange 1223 is used to indicate possible discontinuities 1224 of counter type columnar objects in the table." 1225 ::= { rptrMonitorPortInfo 1 } 1227 rptrMonitorPortEntry OBJECT-TYPE 1228 SYNTAX RptrMonitorPortEntry 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "An entry in the table, containing performance and 1233 error statistics for a single port." 1234 INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex } 1235 ::= { rptrMonitorPortTable 1 } 1237 RptrMonitorPortEntry ::= 1238 SEQUENCE { 1239 rptrMonitorPortGroupIndex 1240 Integer32, 1241 rptrMonitorPortIndex 1242 Integer32, 1243 rptrMonitorPortReadableFrames 1244 Counter32, 1245 rptrMonitorPortReadableOctets 1246 Counter32, 1247 rptrMonitorPortFCSErrors 1248 Counter32, 1249 rptrMonitorPortAlignmentErrors 1250 Counter32, 1251 rptrMonitorPortFrameTooLongs 1252 Counter32, 1253 rptrMonitorPortShortEvents 1254 Counter32, 1255 rptrMonitorPortRunts 1256 Counter32, 1257 rptrMonitorPortCollisions 1258 Counter32, 1259 rptrMonitorPortLateEvents 1260 Counter32, 1261 rptrMonitorPortVeryLongEvents 1262 Counter32, 1263 rptrMonitorPortDataRateMismatches 1264 Counter32, 1265 rptrMonitorPortAutoPartitions 1266 Counter32, 1267 rptrMonitorPortTotalErrors 1268 Counter32, 1269 rptrMonitorPortLastChange 1270 TimeStamp 1271 } 1273 rptrMonitorPortGroupIndex OBJECT-TYPE 1274 SYNTAX Integer32 (1..2147483647) 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "This object identifies the group containing the 1279 port for which this entry contains information." 1280 ::= { rptrMonitorPortEntry 1 } 1282 rptrMonitorPortIndex OBJECT-TYPE 1283 SYNTAX Integer32 (1..2147483647) 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "This object identifies the port within the group 1288 for which this entry contains information." 1289 REFERENCE 1290 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." 1291 ::= { rptrMonitorPortEntry 2 } 1293 rptrMonitorPortReadableFrames OBJECT-TYPE 1294 SYNTAX Counter32 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "This object is the number of frames of valid 1299 frame length that have been received on this port. 1300 This counter is incremented by one for each frame 1301 received on this port whose OctetCount is greater 1302 than or equal to minFrameSize and less than or 1303 equal to maxFrameSize (Ref: IEEE 802.3 Std, 1304 4.4.2.1) and for which the FCSError and 1305 CollisionEvent signals are not asserted. 1307 A discontinuity may occur in the value 1308 when the value of object 1309 rptrMonitorPortLastChange changes. 1311 This statistic provides one of the parameters 1312 necessary for obtaining the packet error rate. 1313 The approximate minimum time for rollover of this 1314 counter is 80 hours at 10Mb/s." 1315 REFERENCE 1316 "[IEEE 802.3 Mgt], 30.4.3.1.4, aReadableFrames." 1317 ::= { rptrMonitorPortEntry 3 } 1319 rptrMonitorPortReadableOctets OBJECT-TYPE 1320 SYNTAX Counter32 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "This object is the number of octets contained in 1325 valid frames that have been received on this port. 1326 This counter is incremented by OctetCount for each 1327 frame received on this port which has been 1328 determined to be a readable frame (i.e., including 1329 FCS octets but excluding framing bits and dribble 1330 bits). 1332 A discontinuity may occur in the value 1333 when the value of object 1334 rptrMonitorPortLastChange changes. 1336 This statistic provides an indicator of the total 1337 data transferred. The approximate minimum time 1338 for rollover of this counter in a 10Mb/s repeater 1339 is 58 minutes. 1341 For ports receiving traffic at a maximum rate in 1342 a 100Mb/s repeater, this counter can roll over 1343 in less than 6 minutes. Since that amount of time 1344 could be less than a management station's poll cycle 1345 time, in order to avoid a loss of information a 1346 management station is advised to also poll the 1347 rptrMonitorPortUpper32Octets object, or to use the 1348 64-bit counter defined by 1349 rptrMonitorPortHCReadableOctets instead of the 1350 two 32-bit counters." 1351 REFERENCE 1352 "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets." 1353 ::= { rptrMonitorPortEntry 4 } 1355 rptrMonitorPortFCSErrors OBJECT-TYPE 1356 SYNTAX Counter32 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "This counter is incremented by one for each frame 1361 received on this port with the FCSError signal 1362 asserted and the FramingError and CollisionEvent 1363 signals deasserted and whose OctetCount is greater 1364 than or equal to minFrameSize and less than or 1365 equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 1366 Std). 1368 A discontinuity may occur in the value 1369 when the value of object 1370 rptrMonitorPortLastChange changes. 1372 The approximate minimum time for rollover of this 1373 counter is 80 hours at 10Mb/s." 1374 REFERENCE 1375 "[IEEE 802.3 Mgt], 30.4.3.1.6, 1376 aFrameCheckSequenceErrors." 1377 ::= { rptrMonitorPortEntry 5 } 1379 rptrMonitorPortAlignmentErrors OBJECT-TYPE 1380 SYNTAX Counter32 1381 MAX-ACCESS read-only 1382 STATUS current 1383 DESCRIPTION 1384 "This counter is incremented by one for each frame 1385 received on this port with the FCSError and 1386 FramingError signals asserted and CollisionEvent 1387 signal deasserted and whose OctetCount is greater 1388 than or equal to minFrameSize and less than or 1389 equal to maxFrameSize (Ref: IEEE 802.3 Std, 1390 4.4.2.1). If rptrMonitorPortAlignmentErrors is 1391 incremented then the rptrMonitorPortFCSErrors 1392 Counter shall not be incremented for the same 1393 frame. 1395 A discontinuity may occur in the value 1396 when the value of object 1397 rptrMonitorPortLastChange changes. 1399 The approximate minimum time for rollover of this 1400 counter is 80 hours at 10Mb/s." 1401 REFERENCE 1402 "[IEEE 802.3 Mgt], 30.4.3.1.7, aAlignmentErrors." 1403 ::= { rptrMonitorPortEntry 6 } 1405 rptrMonitorPortFrameTooLongs OBJECT-TYPE 1406 SYNTAX Counter32 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "This counter is incremented by one for each frame 1411 received on this port whose OctetCount is greater 1412 than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). 1413 If rptrMonitorPortFrameTooLongs is incremented 1414 then neither the rptrMonitorPortAlignmentErrors 1415 nor the rptrMonitorPortFCSErrors counter shall be 1416 incremented for the frame. 1418 A discontinuity may occur in the value 1419 when the value of object 1420 rptrMonitorPortLastChange changes. 1422 The approximate minimum time for rollover of this 1423 counter is 61 days in a 10Mb/s repeater." 1424 REFERENCE 1425 "[IEEE 802.3 Mgt], 30.4.3.1.8, aFramesTooLong." 1426 ::= { rptrMonitorPortEntry 7 } 1428 rptrMonitorPortShortEvents OBJECT-TYPE 1429 SYNTAX Counter32 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "This counter is incremented by one for each 1434 CarrierEvent on this port with ActivityDuration 1435 less than ShortEventMaxTime. ShortEventMaxTime is 1436 greater than 74 bit times and less than 82 bit 1437 times. ShortEventMaxTime has tolerances included 1438 to provide for circuit losses between a 1439 conformance test point at the AUI and the 1440 measurement point within the state machine. 1442 Notes: 1444 ShortEvents may indicate externally 1445 generated noise hits which will cause the repeater 1446 to transmit Runts to its other ports, or propagate 1447 a collision (which may be late) back to the 1448 transmitting DTE and damaged frames to the rest of 1449 the network. 1451 Implementors may wish to consider selecting the 1452 ShortEventMaxTime towards the lower end of the 1453 allowed tolerance range to accommodate bit losses 1454 suffered through physical channel devices not 1455 budgeted for within this standard. 1457 The significance of this attribute is different 1458 in 10 and 100 Mb/s collision domains. Clause 9 1459 repeaters perform fragment extension of short 1460 events which would be counted as runts on the 1461 interconnect ports of other repeaters. Clause 1462 27 repeaters do not perform fragment extension. 1464 A discontinuity may occur in the value 1465 when the value of object 1466 rptrMonitorPortLastChange changes. 1468 The approximate minimum time for rollover of this 1469 counter is 16 hours in a 10Mb/s repeater." 1470 REFERENCE 1471 "[IEEE 802.3 Mgt], 30.4.3.1.9, aShortEvents." 1472 ::= { rptrMonitorPortEntry 8 } 1474 rptrMonitorPortRunts OBJECT-TYPE 1475 SYNTAX Counter32 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "This counter is incremented by one for each 1480 CarrierEvent on this port that meets one of the 1481 following two conditions. Only one test need be 1482 made. a) The ActivityDuration is greater than 1483 ShortEventMaxTime and less than ValidPacketMinTime 1484 and the CollisionEvent signal is deasserted. b) 1485 The OctetCount is less than 64, the 1486 ActivityDuration is greater than ShortEventMaxTime 1487 and the CollisionEvent signal is deasserted. 1488 ValidPacketMinTime is greater than or equal to 552 1489 bit times and less than 565 bit times. 1491 An event whose length is greater than 74 bit times 1492 but less than 82 bit times shall increment either 1493 the shortEvents counter or the runts counter but 1494 not both. A CarrierEvent greater than or equal to 1495 552 bit times but less than 565 bit times may or 1496 may not be counted as a runt. 1498 ValidPacketMinTime has tolerances included to 1499 provide for circuit losses between a conformance 1500 test point at the AUI and the measurement point 1501 within the state machine. 1503 Runts usually indicate collision fragments, a 1504 normal network event. In certain situations 1505 associated with large diameter networks a 1506 percentage of collision fragments may exceed 1507 ValidPacketMinTime. 1509 A discontinuity may occur in the value 1510 when the value of object 1511 rptrMonitorPortLastChange changes. 1513 The approximate minimum time for rollover of this 1514 counter is 16 hours in a 10Mb/s repeater." 1515 REFERENCE 1516 "[IEEE 802.3 Mgt], 30.4.3.1.10, aRunts." 1517 ::= { rptrMonitorPortEntry 9 } 1519 rptrMonitorPortCollisions OBJECT-TYPE 1520 SYNTAX Counter32 1521 MAX-ACCESS read-only 1522 STATUS current 1523 DESCRIPTION 1524 "For a clause 9 repeater, this counter is 1525 incremented by one for any CarrierEvent signal 1526 on any port for which the CollisionEvent signal 1527 on this port is asserted. For a clause 27 1528 repeater port the counter increments on entering 1529 the Collision Count Increment state of the 1530 partition state diagram (fig 27-8 of 1531 [IEEE 802.3 Std]). 1533 A discontinuity may occur in the value 1534 when the value of object 1535 rptrMonitorPortLastChange changes. 1537 The approximate minimum time for rollover of this 1538 counter is 16 hours in a 10Mb/s repeater." 1539 REFERENCE 1540 "[IEEE 802.3 Mgt], 30.4.3.1.11, aCollisions." 1541 ::= { rptrMonitorPortEntry 10 } 1543 rptrMonitorPortLateEvents OBJECT-TYPE 1544 SYNTAX Counter32 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "For a clause 9 repeater port, this counter is 1549 incremented by one for each CarrierEvent 1550 on this port in which the CollIn(X) 1551 variable transitions to the value SQE (Ref: 1552 9.6.6.2, IEEE 802.3 Std) while the 1553 ActivityDuration is greater than the 1554 LateEventThreshold. For a clause 27 repeater 1555 port, this counter is incremented by one on 1556 entering the Collision Count Increment state 1557 of the partition state diagram (fig 27-8) 1558 while the ActivityDuration is greater than 1559 the LateEvent- Threshold. Such a CarrierEvent 1560 is counted twice, as both a collision and as a 1561 lateEvent. 1563 The LateEventThreshold is greater than 480 bit 1564 times and less than 565 bit times. 1565 LateEventThreshold has tolerances included to 1566 permit an implementation to build a single 1567 threshold to serve as both the LateEventThreshold 1568 and ValidPacketMinTime threshold. 1570 A discontinuity may occur in the value 1571 when the value of object 1572 rptrMonitorPortLastChange changes. 1574 The approximate minimum time for rollover of this 1575 counter is 81 hours in a 10Mb/s repeater." 1576 REFERENCE 1577 "[IEEE 802.3 Mgt], 30.4.3.1.12, aLateEvents." 1578 ::= { rptrMonitorPortEntry 11 } 1580 rptrMonitorPortVeryLongEvents OBJECT-TYPE 1581 SYNTAX Counter32 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "For a clause 9 repeater port, this counter 1586 is incremented by one for each CarrierEvent 1587 whose ActivityDuration is greater than the 1588 MAU Jabber Lockup Protection timer TW3 1589 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). 1591 For a clause 27 repeater port, this counter 1592 is incremented by one on entry to the 1593 Rx Jabber state of the receiver timer state 1594 diagram (fig 27-7). Other counters may 1595 be incremented as appropriate. 1597 A discontinuity may occur in the value 1598 when the value of object 1599 rptrMonitorPortLastChange changes." 1600 REFERENCE 1601 "[IEEE 802.3 Mgt], 30.4.3.1.13, aVeryLongEvents." 1602 ::= { rptrMonitorPortEntry 12 } 1604 rptrMonitorPortDataRateMismatches OBJECT-TYPE 1605 SYNTAX Counter32 1606 MAX-ACCESS read-only 1607 STATUS current 1608 DESCRIPTION 1609 "This counter is incremented by one for each 1610 frame received by this port that meets all 1611 of the conditions required by only one of the 1612 following two measurement methods: 1614 Measurement method A: 1) The CollisionEvent 1615 signal is not asserted (10Mb/s operation) or 1616 the Collision Count Increment state of the 1617 partition state diagram (fig 27-8 of 1618 [IEEE 802.3 Std]) has not been entered 1619 (100Mb/s operation). 2) The ActivityDuration 1620 is greater than ValidPacketMinTime. 3) The 1621 frequency (data rate) is detectably mismatched 1622 from the local transmit frequency. 1624 Measurement method B: 1) The CollisionEvent 1625 signal is not asserted (10Mb/s operation) 1626 or the Collision Count Increment state of the 1627 partition state diagram (fig 27-8 of 1628 [IEEE 802.3 Std]) has not been entered 1629 (100Mb/s operation). 2) The OctetCount is 1630 greater than 63. 3) The frequency (data 1631 rate) is detectably mismatched from the local 1632 transmit frequency. The exact degree of 1633 mismatch is vendor specific and is to be 1634 defined by the vendor for conformance testing. 1636 When this event occurs, other counters whose 1637 increment conditions were satisfied may or may not 1638 also be incremented, at the implementor's 1639 discretion. Whether or not the repeater was able 1640 to maintain data integrity is beyond the scope of 1641 this standard. 1643 A discontinuity may occur in the value 1644 when the value of object 1645 rptrMonitorPortLastChange changes." 1646 REFERENCE 1647 "[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches." 1648 ::= { rptrMonitorPortEntry 13 } 1650 rptrMonitorPortAutoPartitions OBJECT-TYPE 1651 SYNTAX Counter32 1652 MAX-ACCESS read-only 1653 STATUS current 1654 DESCRIPTION 1655 "This counter is incremented by one for 1656 each time the repeater has automatically 1657 partitioned this port. 1659 The conditions that cause a clause 9 1660 repeater port to partition are specified in 1661 the partition state diagram in clause 9 of 1662 [IEEE 802.3 Std]. They are not differentiated 1663 here. A clause 27 repeater port partitions 1664 on entry to the Partition Wait state of the 1665 partition state diagram (fig 27-8 in 1666 [IEEE 802.3 Std]). 1668 A discontinuity may occur in the value 1669 when the value of object 1670 rptrMonitorPortLastChange changes." 1671 REFERENCE 1672 "[IEEE 802.3 Mgt], 30.4.3.1.15, aAutoPartitions." 1673 ::= { rptrMonitorPortEntry 14 } 1675 rptrMonitorPortTotalErrors OBJECT-TYPE 1676 SYNTAX Counter32 1677 MAX-ACCESS read-only 1678 STATUS current 1679 DESCRIPTION 1680 "The total number of errors which have occurred on 1681 this port. This counter is the summation of the 1682 values of other error counters (for the same 1683 port), namely: 1685 rptrMonitorPortFCSErrors, 1686 rptrMonitorPortAlignmentErrors, 1687 rptrMonitorPortFrameTooLongs, 1688 rptrMonitorPortShortEvents, 1689 rptrMonitorPortLateEvents, 1690 rptrMonitorPortVeryLongEvents, and 1691 rptrMonitorPortDataRateMismatches. 1693 This counter is redundant in the sense that it is 1694 the summation of information already available 1695 through other objects. However, it is included 1696 specifically because the regular retrieval of this 1697 object as a means of tracking the health of a port 1698 provides a considerable optimization of network 1699 management traffic over the otherwise necessary 1700 retrieval of the summed counters. 1702 Note that rptrMonitorPortRunts is not included 1703 in this total; this is because runts usually 1704 indicate collision fragments, a normal network 1705 event. 1707 [Editor's note: This sum does not include the 1708 value of the rptrMonitorPortSymbolErrors object. 1709 Perhaps we should deprecate it and define a new 1710 PortTotalErrors object which does. However, we 1711 may need to address the rollover issue in that 1712 case.] 1714 A discontinuity may occur in the value 1715 when the value of object 1716 rptrMonitorPortLastChange changes." 1718 ::= { rptrMonitorPortEntry 15 } 1720 rptrMonitorPortLastChange OBJECT-TYPE 1721 SYNTAX TimeStamp 1722 MAX-ACCESS read-only 1723 STATUS current 1724 DESCRIPTION 1725 "The value of sysUpTime when the last of 1726 the following occurred: 1727 1) the agent cold- or warm-started; 1728 2) the row for the port was created 1729 (such as when a device or module was added 1730 to the system); or 1731 3) any condition that would cause one of 1732 the counters for the row to experience 1733 a discontinuity." 1734 ::= { rptrMonitorPortEntry 16 } 1736 rptrMonitor100PortTable OBJECT-TYPE 1737 SYNTAX SEQUENCE OF RptrMonitor100PortEntry 1738 MAX-ACCESS not-accessible 1739 STATUS current 1740 DESCRIPTION 1741 "Table of additional performance and error 1742 statistics for 100Mb/s ports, above and 1743 beyond those parameters that apply to both 1744 10 and 100Mbps ports. Entries exist only for 1745 ports attached to 100Mbps repeaters. This 1746 table augments the rptrMonitorPortTable. 1748 The columnar object rptrMonitorPortLastChange 1749 is used to indicate possible discontinuities 1750 of counter type columnar objects in this table." 1751 ::= { rptrMonitorPortInfo 2 } 1753 rptrMonitor100PortEntry OBJECT-TYPE 1754 SYNTAX RptrMonitor100PortEntry 1755 MAX-ACCESS not-accessible 1756 STATUS current 1757 DESCRIPTION 1758 "An entry in the table, containing performance 1759 and error statistics for a single 100Mb/s port." 1760 AUGMENTS { rptrMonitorPortEntry } 1761 ::= { rptrMonitor100PortTable 1 } 1763 RptrMonitor100PortEntry ::= 1764 SEQUENCE { 1765 rptrMonitorPortIsolates 1766 Counter32, 1767 rptrMonitorPortSymbolErrors 1768 Counter32, 1769 rptrMonitorPortUpper32Octets 1770 Counter32, 1771 rptrMonitorPortHCReadableOctets 1772 Counter64 1773 } 1775 rptrMonitorPortIsolates OBJECT-TYPE 1776 SYNTAX Counter32 1777 MAX-ACCESS read-only 1778 STATUS current 1779 DESCRIPTION 1780 "This counter is incremented by one each time that 1781 the repeater port automatically isolates as a 1782 consequence of false carrier events. The conditions 1783 which cause a port to automatically isolate are 1784 defined by the transition from the False Carrier 1785 state to the Link Unstable state of the carrier 1786 integrity state diagram (figure 27-9) 1787 [IEEE 802.3 Standard]. 1789 Note: Isolates do not affect the value of 1790 the PortOperStatus object. 1792 A discontinuity may occur in the value 1793 when the value of object 1794 rptrMonitorPortLastChange changes." 1795 REFERENCE 1796 "[IEEE 802.3 Mgt], 30.4.3.1.16, aIsolates." 1797 ::= { rptrMonitor100PortEntry 1 } 1799 rptrMonitorPortSymbolErrors OBJECT-TYPE 1800 SYNTAX Counter32 1801 MAX-ACCESS read-only 1802 STATUS current 1803 DESCRIPTION 1804 "This counter is incremented by one each time when 1805 valid length packet was received at the port and 1806 there was at least one occurrence of an invalid 1807 data symbol. This can increment only once per valid 1808 carrier event. A collision presence at any port of 1809 the repeater containing port N, will not cause this 1810 attribute to increment. 1812 A discontinuity may occur in the value 1813 when the value of object 1814 rptrMonitorPortLastChange changes. 1816 The approximate minimum time for rollover of this 1817 counter is 7.4 hours at 100Mb/s." 1818 REFERENCE 1819 "[IEEE 802.3 Mgt], 30.4.3.1.17, 1820 aSymbolErrorDuringPacket." 1821 ::= { rptrMonitor100PortEntry 2 } 1823 rptrMonitorPortUpper32Octets OBJECT-TYPE 1824 SYNTAX Counter32 1825 MAX-ACCESS read-only 1826 STATUS current 1827 DESCRIPTION 1828 "This object is the number of octets contained in 1829 valid frames that have been received on this port, 1830 modulo 2**32. That is, it contains the upper 32 1831 bits of a 64-bit octets counter, of which the 1832 lower 32 bits are contained in the 1833 rptrMonitorPortReadableOctets object. 1835 This two-counter mechanism is provided for those 1836 network management protocols that do not support 1837 64-bit counters (e.g. SNMP V1) and are used to 1838 manage a repeater type of 100Mb/s. 1840 A discontinuity may occur in the value 1841 when the value of object 1842 rptrMonitorPortLastChange changes." 1843 ::= { rptrMonitor100PortEntry 3 } 1845 rptrMonitorPortHCReadableOctets OBJECT-TYPE 1846 SYNTAX Counter64 1847 MAX-ACCESS read-only 1848 STATUS current 1849 DESCRIPTION 1850 "This object is the number of octets contained in 1851 valid frames that have been received on this port. 1852 This counter is incremented by OctetCount for each 1853 frame received on this port which has been 1854 determined to be a readable frame (i.e., including 1855 FCS octets but excluding framing bits and dribble 1856 bits). 1858 This statistic provides an indicator of the total 1859 data transferred. 1861 This counter is a 64-bit version of rptrMonitor- 1862 PortReadableOctets. It should be used by network 1863 management protocols which suppport 64-bit counters 1864 (e.g. SNMPv2). 1866 A discontinuity may occur in the value 1867 when the value of object 1868 rptrMonitorPortLastChange changes." 1869 REFERENCE 1870 "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets." 1871 ::= { rptrMonitor100PortEntry 4 } 1873 -- New version of statistics at the repeater level. 1874 -- 1875 -- Statistics objects for each managed repeater 1876 -- in the system. 1878 rptrMonTable OBJECT-TYPE 1879 SYNTAX SEQUENCE OF RptrMonEntry 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "A table of information about each 1884 non-trivial repeater. The number of entries 1885 in this table is the same as the number of 1886 entries in the rptrInfoTable. 1888 The columnar object rptrInfoLastChange is 1889 used to indicate possible discontinuities of 1890 counter type columnar objects in this table." 1891 ::= { rptrMonitorAllRptrInfo 1 } 1893 rptrMonEntry OBJECT-TYPE 1894 SYNTAX RptrMonEntry 1895 MAX-ACCESS not-accessible 1896 STATUS current 1897 DESCRIPTION 1898 "An entry in the table, containing information 1899 about a single non-trivial repeater." 1900 AUGMENTS { rptrInfoEntry } 1901 ::= { rptrMonTable 1 } 1903 RptrMonEntry ::= 1904 SEQUENCE { 1905 rptrMonTxCollisions 1906 Counter32, 1907 rptrMonTotalFrames 1908 Counter32, 1909 rptrMonTotalErrors 1910 Counter32, 1911 rptrMonTotalOctets 1912 Counter32 1913 } 1915 rptrMonTxCollisions OBJECT-TYPE 1916 SYNTAX Counter32 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "For a clause 9 (10Mb/s) repeater, this counter 1921 is incremented every time the repeater state 1922 machine enters the TRANSMIT COLLISION state 1923 from any state other than ONE PORT LEFT 1924 (Ref: Fig 9-2 [IEEE 802.3 Std]). 1926 For a clause 27 repeater, this counter is 1927 incremented every time the repeater core state 1928 diagram enters the Jam state as a result of 1929 Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). 1931 The approximate minimum time for rollover of this 1932 counter is 16 hours in a 10Mb/s repeater and 1.6 1933 hours in a 100Mb/s repeater." 1934 REFERENCE 1935 "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions" 1936 ::= { rptrMonEntry 1 } 1938 rptrMonTotalFrames OBJECT-TYPE 1939 SYNTAX Counter32 1940 MAX-ACCESS read-only 1941 STATUS current 1942 DESCRIPTION 1943 "The number of frames of valid frame length 1944 that have been received on the ports in this repeater 1945 and for which the FCSError and CollisionEvent 1946 signals were not asserted. If an implementation 1947 can not obtain a count of frames as seen by 1948 the repeater itself, this counter may be 1949 implemented as the summation of the values of the 1950 rptrMonitorPortReadableFrames counters for all of 1951 the ports in the repeater. 1953 This statistic provides one of the parameters 1954 necessary for obtaining the packet error rate. 1955 The approximate minimum time for rollover of this 1956 counter is 80 hours in a 10Mb/s repeater." 1957 ::= { rptrMonEntry 3 } 1959 rptrMonTotalErrors OBJECT-TYPE 1960 SYNTAX Counter32 1961 MAX-ACCESS read-only 1962 STATUS current 1963 DESCRIPTION 1964 "The total number of errors which have occurred on 1965 all of the ports in this repeater. The errors 1966 included in this count are the same as those listed 1967 for the rptrMonitorPortTotalErrors counter. If an 1968 implementation can not obtain a count of these 1969 errors as seen by the repeater itself, this counter 1970 may be implemented as the summation of the values of 1971 the rptrMonitorPortTotalErrors counters for all of 1972 the ports in the repeater." 1973 ::= { rptrMonEntry 4 } 1975 rptrMonTotalOctets OBJECT-TYPE 1976 SYNTAX Counter32 1977 MAX-ACCESS read-only 1978 STATUS current 1979 DESCRIPTION 1980 "The total number of octets contained in the valid 1981 frames that have been received on the ports in 1982 this group. If an implementation can not obtain 1983 a count of octets as seen by the repeater itself, 1984 this counter may be the summation of the 1985 values of the rptrMonitorPortReadableOctets 1986 counters for all of the ports in the group. 1988 This statistic provides an indicator of the total 1989 data transferred. The approximate minimum time 1990 for rollover of this counter in a 10Mb/s repeater 1991 is 58 minutes divided by the number of ports in 1992 the repeater. 1994 For 100Mb/s repeaters processing traffic at a 1995 maximum rate, this counter can roll over in less 1996 than 6 minutes divided by the number of ports in 1997 the repeater. Since that amount of time could 1998 be less than a management station's poll cycle 1999 time, in order to avoid a loss of information a 2000 management station is advised to also poll the 2001 rptrMonUpper32TotalOctets object, or to use the 2002 64-bit counter defined by rptrMonHCTotalOctets 2003 instead of the two 32-bit counters." 2004 ::= { rptrMonEntry 5 } 2006 rptrMon100Table OBJECT-TYPE 2007 SYNTAX SEQUENCE OF RptrMon100Entry 2008 MAX-ACCESS not-accessible 2009 STATUS current 2010 DESCRIPTION 2011 "A table of additional information about each 2012 100Mb/s repeater, augmenting the entries in 2013 the rptrMonTable. Entries exist in this table 2014 only for 100Mb/s repeaters. 2016 The columnar object rptrInfoLastChange is 2017 used to indicate possible discontinuities of 2018 counter type columnar objects in this table." 2019 ::= { rptrMonitorAllRptrInfo 2 } 2021 rptrMon100Entry OBJECT-TYPE 2022 SYNTAX RptrMon100Entry 2023 MAX-ACCESS not-accessible 2024 STATUS current 2025 DESCRIPTION 2026 "An entry in the table, containing information 2027 about a single 100Mbps repeater." 2028 AUGMENTS { rptrInfoEntry } 2029 ::= { rptrMon100Table 1 } 2031 RptrMon100Entry ::= 2032 SEQUENCE { 2033 rptrMonUpper32TotalOctets 2034 Counter32, 2035 rptrMonHCTotalOctets 2036 Counter64 2037 } 2039 rptrMonUpper32TotalOctets OBJECT-TYPE 2040 SYNTAX Counter32 2041 MAX-ACCESS read-only 2042 STATUS current 2043 DESCRIPTION 2044 "The total number of octets contained in the valid 2045 frames that have been received on the ports in 2046 this repeater, modulo 2**32. That is, it contains 2047 the upper 32 bits of a 64-bit counter, of which 2048 the lower 32 bits are contained in the 2049 rptrMonTotalOctets object. If an implementation 2050 can not obtain a count of octets as seen 2051 by the repeater itself, the 64-bit value 2052 may be the summation of the values of the 2053 rptrMonitorPortReadableOctets counters combined 2054 with the corresponding rptrMonitorPortUpper32Octets 2055 counters for all of the ports in the repeater. 2057 This statistic provides an indicator of the total 2058 data transferred within the repeater. 2060 This two-counter mechanism is provided for those 2061 network management protocols that do not support 2062 64-bit counters (e.g. SNMP V1) and are used to 2063 manage a repeater type of 100Mb/s." 2064 ::= { rptrMon100Entry 1 } 2066 rptrMonHCTotalOctets OBJECT-TYPE 2067 SYNTAX Counter64 2068 MAX-ACCESS read-only 2069 STATUS current 2070 DESCRIPTION 2071 "The total number of octets contained in the valid 2072 frames that have been received on the ports in 2073 this group. If a implementation can not obtain 2074 a count of octets as seen by the repeater itself, 2075 this counter may be the summation of the 2076 values of the rptrMonitorPortReadableOctets 2077 counters for all of the ports in the group. 2079 This statistic provides an indicator of the total 2080 data transferred. 2082 This counter is a 64-bit (high-capacity) version 2083 of rptrMonUpper32TotalOctets and rptrMonTotalOctets. 2084 It should be used by network management protocols 2085 which support 64-bit counters (e.g. SNMPv2). " 2086 ::= { rptrMon100Entry 2 } 2088 -- 2089 -- The Port Address Tracking Table 2090 -- 2092 rptrAddrTrackTable OBJECT-TYPE 2093 SYNTAX SEQUENCE OF RptrAddrTrackEntry 2094 MAX-ACCESS not-accessible 2095 STATUS current 2096 DESCRIPTION 2097 "Table of address mapping information about the 2098 ports." 2099 ::= { rptrAddrTrackPortInfo 1 } 2101 rptrAddrTrackEntry OBJECT-TYPE 2102 SYNTAX RptrAddrTrackEntry 2103 MAX-ACCESS not-accessible 2104 STATUS current 2105 DESCRIPTION 2106 "An entry in the table, containing address mapping 2107 information about a single port." 2108 INDEX { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex } 2109 ::= { rptrAddrTrackTable 1 } 2111 RptrAddrTrackEntry ::= 2112 SEQUENCE { 2113 rptrAddrTrackGroupIndex 2114 INTEGER, 2115 rptrAddrTrackPortIndex 2116 INTEGER, 2117 rptrAddrTrackLastSourceAddress -- DEPRECATED OBJECT 2118 MacAddress, 2119 rptrAddrTrackSourceAddrChanges 2120 Counter32, 2122 rptrAddrTrackNewLastSrcAddress 2123 OptMacAddr, 2124 rptrAddrTrackCapacity 2125 Integer32 2126 } 2128 rptrAddrTrackGroupIndex OBJECT-TYPE 2129 SYNTAX INTEGER (1..2147483647) 2130 MAX-ACCESS read-only 2131 STATUS current 2132 DESCRIPTION 2133 "This object identifies the group containing the 2134 port for which this entry contains information." 2135 ::= { rptrAddrTrackEntry 1 } 2137 rptrAddrTrackPortIndex OBJECT-TYPE 2138 SYNTAX INTEGER (1..2147483647) 2139 MAX-ACCESS read-only 2140 STATUS current 2141 DESCRIPTION 2142 "This object identifies the port within the group 2143 for which this entry contains information." 2144 REFERENCE 2145 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." 2146 ::= { rptrAddrTrackEntry 2 } 2148 rptrAddrTrackLastSourceAddress OBJECT-TYPE 2149 SYNTAX MacAddress 2150 MAX-ACCESS read-only 2151 STATUS deprecated 2152 DESCRIPTION 2153 "This object is the SourceAddress of the last 2154 readable frame (i.e., counted by 2155 rptrMonitorPortReadableFrames) received by this 2156 port. 2158 This object has been deprecated because its value 2159 is undefined when no frames have been observed on 2160 this port. The replacement object is 2161 rptrAddrTrackNewLastSrcAddress." 2162 REFERENCE 2163 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2164 ::= { rptrAddrTrackEntry 3 } 2166 rptrAddrTrackSourceAddrChanges OBJECT-TYPE 2167 SYNTAX Counter32 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "This counter is incremented by one for each time 2172 that the rptrAddrTrackLastSourceAddress attribute 2173 for this port has changed. 2175 This may indicate whether a link is connected to a 2176 single DTE or another multi-user segment. 2178 A discontinuity may occur in the value when the 2179 value of object rptrMonitorPortLastChange changes. 2181 The approximate minimum time for rollover of this 2182 counter is 81 hours in a 10Mb/s repeater." 2183 REFERENCE 2184 "[IEEE 802.3 Mgt], 30.4.3.1.19, aSourceAddressChanges." 2185 ::= { rptrAddrTrackEntry 4 } 2187 rptrAddrTrackNewLastSrcAddress OBJECT-TYPE 2188 SYNTAX OptMacAddr 2189 MAX-ACCESS read-only 2190 STATUS current 2191 DESCRIPTION 2192 "This object is the SourceAddress of the last 2193 readable frame (i.e., counted by 2194 rptrMonitorPortReadableFrames) received by this 2195 port. If no frames have been received by this 2196 port since the agent began monitoring the port 2197 activity, the agent shall return a string of 2198 length zero." 2199 REFERENCE 2200 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2201 ::= { rptrAddrTrackEntry 5 } 2203 rptrAddrTrackCapacity OBJECT-TYPE 2204 SYNTAX Integer32 2205 MAX-ACCESS read-only 2206 STATUS current 2207 DESCRIPTION 2208 "The maximum number of addresses that can be 2209 detected on this port. This value indicates 2210 to the maximum number of entries in the 2211 rptrExtAddrTrackTable relative to this port. 2213 If this object has the value of 1, the agent 2214 implements only the LastSourceAddress mechanism 2215 described by RFC 1368 or RFC 1516." 2216 ::= { rptrAddrTrackEntry 6 } 2218 -- Table for multiple addresses per port 2220 rptrExtAddrTrackTable OBJECT-TYPE 2221 SYNTAX SEQUENCE OF RptrExtAddrTrackEntry 2222 MAX-ACCESS not-accessible 2223 STATUS current 2224 DESCRIPTION 2225 "A table to extend the address tracking table (i.e., 2226 rptrAddrTrackTable) with a list of source MAC 2227 addresses that were recently received on each port. 2228 The number of ports is the same as the number 2229 of entries in table rptrPortTable. The number of 2230 entries in this table depends on the agent/repeater 2231 implementation and the number of different 2232 addresses received on each port. 2234 The first entry for each port contains 2235 the same MAC address that is given by the 2236 rptrAddrTrackNewLastSrcAddress for that port. 2238 Entries in this table for a particular port are 2239 retained when that port is switched from one 2240 repeater to another. 2242 The ordering of MAC addresses listed for a 2243 particular port is implementation dependent." 2244 ::= { rptrAddrTrackPortInfo 2 } 2246 rptrExtAddrTrackEntry OBJECT-TYPE 2247 SYNTAX RptrExtAddrTrackEntry 2248 MAX-ACCESS not-accessible 2249 STATUS current 2250 DESCRIPTION 2251 "A row in the table of extended address tracking 2252 information for ports. Entries can not be directly 2253 created or deleted via SNMP operations." 2254 INDEX { rptrAddrTrackGroupIndex, 2255 rptrAddrTrackPortIndex, 2256 rptrExtAddrTrackMacIndex } 2258 ::= { rptrExtAddrTrackTable 1 } 2260 RptrExtAddrTrackEntry ::= SEQUENCE { 2261 rptrExtAddrTrackMacIndex Integer32, 2262 rptrExtAddrTrackSourceAddress MacAddress 2263 } 2265 rptrExtAddrTrackMacIndex OBJECT-TYPE 2266 SYNTAX Integer32 (1..2147483647) 2267 MAX-ACCESS read-only 2268 STATUS current 2269 DESCRIPTION 2270 "The index of a source MAC address seen on 2271 the port." 2272 ::= { rptrExtAddrTrackEntry 1 } 2274 rptrExtAddrTrackSourceAddress OBJECT-TYPE 2275 SYNTAX MacAddress 2276 MAX-ACCESS read-only 2277 STATUS current 2278 DESCRIPTION 2279 "The source MAC address from a readable frame 2280 (i.e., counted by rptrMonitorPortReadableFrames) 2281 recently received by the port." 2282 REFERENCE 2283 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." 2284 ::= { rptrExtAddrTrackEntry 2 } 2286 rptrAddrTrackReset OBJECT-TYPE 2287 SYNTAX INTEGER { 2288 noReset(1), 2289 reset(2) 2290 } 2291 MAX-ACCESS read-write 2292 STATUS current 2293 DESCRIPTION 2294 "Setting this object to reset(2) causes 2295 the agent to empty the contents of the 2296 rptrExtAddrTrackTable. The contents of 2297 the rptrAddrTrackTable are not affected. 2299 Setting this object to noReset(1) has no effect. 2300 The agent will always return the value noReset(1) 2301 when this object is read." 2302 ::= { rptrAddrTrackPortInfo 3 } 2304 -- The Repeater Top "N" Port Group 2306 -- The Repeater Top N Port group is used to prepare reports that 2307 -- describe a list of ports ordered by one of the statistics in the 2308 -- Repeater Monitor Port Table. The statistic chosen by the 2309 -- management station is sampled over a management 2310 -- station-specified time interval, making the report rate based. 2311 -- The management station also specifies the number of ports that 2312 -- are reported. 2313 -- 2314 -- The rptrTopNPortControlTable is used to initiate the generation 2315 -- of a report. The management station may select the parameters 2316 -- of such a report, such as which repeater, which statistic, how 2317 -- many ports, and the start & stop times of the sampling. When 2318 -- the report is prepared, entries are created in the 2319 -- rptrTopNPortTable associated with the relevent 2320 -- rptrTopNControlEntry. These entries are static for 2321 -- each report after it has been prepared. 2323 -- Note that counter discontinuities may appear in some 2324 -- implementations if ports' assignment to repeaters changes 2325 -- during the collection of data for a Top "N" report. 2326 -- A management application could read the corresponding 2327 -- rptrMonitorPortLastChange timestamp in order to check 2328 -- whether a discontinuity occurred. 2330 rptrTopNPortControlTable OBJECT-TYPE 2331 SYNTAX SEQUENCE OF RptrTopNPortControlEntry 2332 MAX-ACCESS not-accessible 2333 STATUS current 2334 DESCRIPTION 2335 "A table of control records for reports on the top `N' 2336 ports for the rate of a selected counter. The number 2337 of entries depends on the configuration of the agent. 2338 The maximum number of entries is implementation 2339 dependent." 2340 ::= { rptrTopNPortInfo 1 } 2342 rptrTopNPortControlEntry OBJECT-TYPE 2343 SYNTAX RptrTopNPortControlEntry 2344 MAX-ACCESS not-accessible 2345 STATUS current 2346 DESCRIPTION 2347 "A set of parameters that control the creation of a 2348 report of the top N ports according to several metrics." 2349 INDEX { rptrTopNPortControlIndex } 2350 ::= { rptrTopNPortControlTable 1 } 2352 RptrTopNPortControlEntry ::= SEQUENCE { 2353 rptrTopNPortControlIndex 2354 Integer32, 2355 rptrTopNPortRepeaterId 2356 Integer32, 2357 rptrTopNPortRateBase 2358 INTEGER, 2359 rptrTopNPortTimeRemaining 2360 Integer32, 2361 rptrTopNPortDuration 2362 Integer32, 2363 rptrTopNPortRequestedSize 2364 Integer32, 2365 rptrTopNPortGrantedSize 2366 Integer32, 2367 rptrTopNPortStartTime 2368 TimeStamp, 2369 rptrTopNPortOwner 2370 OwnerString, 2371 rptrTopNPortRowStatus 2372 RowStatus 2373 } 2375 rptrTopNPortControlIndex OBJECT-TYPE 2376 SYNTAX Integer32 (1 .. 65535) 2377 MAX-ACCESS read-only 2378 STATUS current 2379 DESCRIPTION 2380 "An index that uniquely identifies an entry in the 2381 rptrTopNPortControl table. Each such entry defines 2382 one top N report prepared for a repeater or system." 2383 ::= { rptrTopNPortControlEntry 1 } 2385 rptrTopNPortRepeaterId OBJECT-TYPE 2386 SYNTAX Integer32 (0..2147483647) 2387 MAX-ACCESS read-create 2388 STATUS current 2389 DESCRIPTION 2390 "Identifies the repeater for which a top N report will 2391 be prepared (see rptrInfoId). If the value of this 2392 object is positive, only ports assigned to this repeater 2393 will be used to form the list in which to order the 2394 Top N table. If this value is zero, all ports will be 2395 eligible for inclusion on the list. 2397 The value of this object may not be modified if the 2398 associated rptrTopNPortRowStatus object is equal to 2399 active(1)." 2400 ::= { rptrTopNPortControlEntry 2 } 2402 rptrTopNPortRateBase OBJECT-TYPE 2403 SYNTAX INTEGER { 2404 rptrMonitorPortReadableFrames(1), 2405 rptrMonitorPortReadableOctets(2), 2406 rptrMonitorPortFCSErrors(3), 2407 rptrMonitorPortAlignmentErrors(4), 2408 rptrMonitorPortFrameTooLongs(5), 2409 rptrMonitorPortShortEvents(6), 2410 rptrMonitorPortRunts(7), 2411 rptrMonitorPortCollisions(8), 2412 rptrMonitorPortLateEvents(9), 2413 rptrMonitorPortVeryLongEvents(10), 2414 rptrMonitorPortDataRateMismatches(11), 2415 rptrMonitorPortAutoPartitions(12), 2416 rptrMonitorPortTotalErrors(13), 2417 rptrMonitorPortIsolates(14), 2418 rptrMonitorPortSymbolErrors(15) 2419 } 2420 MAX-ACCESS read-create 2421 STATUS current 2422 DESCRIPTION 2423 "The monitored variable, which the rptrTopNPortRate 2424 variable is based upon. 2426 The value of this object may not be modified if 2427 the associated rptrTopNPortRowStatus object has 2428 a value of active(1)." 2429 ::= { rptrTopNPortControlEntry 3 } 2431 rptrTopNPortTimeRemaining OBJECT-TYPE 2432 SYNTAX Integer32 (0..2147483647) 2433 MAX-ACCESS read-create 2434 STATUS current 2435 DESCRIPTION 2436 "The number of seconds left in the report 2437 currently being collected. When this object 2438 is modified by the management station, a new 2439 collection is started, possibly aborting a 2440 currently running report. The new value is 2441 used as the requested duration of this report, 2442 which is loaded into the associated 2443 rptrTopNPortDuration object. 2445 When this object is set to a non-zero value, 2446 any associated rptrTopNPortEntries shall be 2447 made inaccessible by the agent. While the value 2448 of this object is non-zero, it decrements by one 2449 per second until it reaches zero. During this 2450 time, all associated rptrTopNPortEntries shall 2451 remain inaccessible. At the time that this object 2452 decrements to zero, the report is made accessible 2453 in the rptrTopNPortTable. Thus, the rptrTopNPort 2454 table needs to be created only at the end of the 2455 collection interval." 2456 DEFVAL { 0 } 2457 ::= { rptrTopNPortControlEntry 4 } 2459 rptrTopNPortDuration OBJECT-TYPE 2460 SYNTAX Integer32 (0..2147483647) 2461 MAX-ACCESS read-only 2462 STATUS current 2463 DESCRIPTION 2464 "The number of seconds that this report has 2465 collected during the last sampling interval, 2466 or if this report is currently being collected, 2467 the number of seconds that this report is being 2468 collected during this sampling interval. 2470 When the associated rptrTopNPortTimeRemaining 2471 object is set, this object shall be set by the 2472 agent to the same value and shall not be modified 2473 until the next time the rptrTopNPortTimeRemaining 2474 is set. 2476 This value shall be zero if no reports have been 2477 requested for this rptrTopNPortControlEntry." 2478 ::= { rptrTopNPortControlEntry 5 } 2480 rptrTopNPortRequestedSize OBJECT-TYPE 2481 SYNTAX Integer32 2482 MAX-ACCESS read-create 2483 STATUS current 2484 DESCRIPTION 2485 "The maximum number of repeater ports requested 2486 for the Top N Table. 2488 When this object is created or modified, the 2489 agent should set rptrTopNPortGrantedSize as close 2490 to this object as is possible for the particular 2491 implementation and available resources." 2492 DEFVAL { 10 } 2493 ::= { rptrTopNPortControlEntry 6 } 2495 rptrTopNPortGrantedSize OBJECT-TYPE 2496 SYNTAX Integer32 (0..65535) 2497 MAX-ACCESS read-only 2498 STATUS current 2499 DESCRIPTION 2500 "The maximum number of repeater ports in the 2501 top N table. 2503 When the associated rptrTopNPortRequestedSize object is 2504 created or modified, the agent should set this object as 2505 closely to the requested value as is possible for the 2506 particular implementation and available resources. The 2507 agent must not lower this value except as a result of a 2508 set to the associated rptrTopNPortRequestedSize object." 2509 ::= { rptrTopNPortControlEntry 7 } 2511 rptrTopNPortStartTime OBJECT-TYPE 2512 SYNTAX TimeStamp 2513 MAX-ACCESS read-only 2514 STATUS current 2515 DESCRIPTION 2516 "The value of sysUpTime when this top N report was 2517 last started. In other words, this is the time that 2518 the associated rptrTopNPortTimeRemaining object was 2519 modified to start the requested report." 2520 ::= { rptrTopNPortControlEntry 8 } 2522 rptrTopNPortOwner OBJECT-TYPE 2523 SYNTAX OwnerString 2524 MAX-ACCESS read-create 2525 STATUS current 2526 DESCRIPTION 2527 "The entity that configured this entry and is 2528 using the resources assigned to it." 2529 ::= { rptrTopNPortControlEntry 9 } 2531 rptrTopNPortRowStatus OBJECT-TYPE 2532 SYNTAX RowStatus 2533 MAX-ACCESS read-create 2534 STATUS current 2535 DESCRIPTION 2536 "The status of this row." 2537 ::= { rptrTopNPortControlEntry 10 } 2539 -- Top "N" reports 2541 rptrTopNPortTable OBJECT-TYPE 2542 SYNTAX SEQUENCE OF RptrTopNPortEntry 2543 MAX-ACCESS not-accessible 2544 STATUS current 2545 DESCRIPTION 2546 "A table of reports for the top `N' ports based on 2547 setting of associated control table entries. The 2548 maximum number of entries depends on the number 2549 of entries in table rptrTopNPortControlTable and 2550 the value of object rptrTopNPortGrantedSize for 2551 each entry. 2553 For each entry in the rptrTopNPortControlTable, 2554 repeater ports with the highest value of 2555 rptrTopNPortRate shall be placed in this table 2556 in decreasing order of that rate until there is 2557 no more room or until there are no more ports." 2558 ::= { rptrTopNPortInfo 2 } 2560 rptrTopNPortEntry OBJECT-TYPE 2561 SYNTAX RptrTopNPortEntry 2562 MAX-ACCESS not-accessible 2563 STATUS current 2564 DESCRIPTION 2565 "A set of statistics for a repeater port that is 2566 part of a top N report." 2567 INDEX { rptrTopNPortControlIndex, 2568 rptrTopNPortIndex } 2569 ::= { rptrTopNPortTable 1 } 2571 RptrTopNPortEntry ::= SEQUENCE { 2572 rptrTopNPortIndex 2573 Integer32, 2574 rptrTopNPortGroupIndex 2575 Integer32, 2576 rptrTopNPortPortIndex 2577 Integer32, 2578 rptrTopNPortRate 2579 Gauge32 2580 } 2582 rptrTopNPortIndex OBJECT-TYPE 2583 SYNTAX Integer32 (1..65535) 2584 MAX-ACCESS read-only 2585 STATUS current 2586 DESCRIPTION 2587 "An index that uniquely identifies an entry in 2588 the rptrTopNPort table among those in the same 2589 report. This index is between 1 and N, where N 2590 is the number of entries in this report. Increasing 2591 values of rptrTopNPortIndex shall be assigned to 2592 entries with decreasing values of rptrTopNPortRate 2593 until index N is assigned to the entry with the 2594 lowest value of rptrTopNPortRate or there are no 2595 more rptrTopNPortEntries. 2597 No ports are included in a report where their 2598 value of rptrTopNPortRate would be zero." 2599 ::= { rptrTopNPortEntry 1 } 2601 rptrTopNPortGroupIndex OBJECT-TYPE 2602 SYNTAX Integer32 (1..2147483647) 2603 MAX-ACCESS read-only 2604 STATUS current 2605 DESCRIPTION 2606 "This object identifes the group containing 2607 the port for this entry. (See also object 2608 type rptrGroupIndex.)" 2609 ::= { rptrTopNPortEntry 2 } 2611 rptrTopNPortPortIndex OBJECT-TYPE 2612 SYNTAX Integer32 (1..2147483647) 2613 MAX-ACCESS read-only 2614 STATUS current 2615 DESCRIPTION 2616 "The index of the repeater port. 2618 (See object type rptrPortIndex.)" 2619 ::= { rptrTopNPortEntry 3 } 2621 rptrTopNPortRate OBJECT-TYPE 2622 SYNTAX Gauge32 2623 MAX-ACCESS read-only 2624 STATUS current 2625 DESCRIPTION 2626 "The amount of change in the selected variable 2627 during this sampling interval for the identified 2628 port. The selected variable is that port's 2629 instance of the object selected by 2630 rptrTopNPortRateBase." 2631 ::= { rptrTopNPortEntry 4 } 2633 -- Notifications for use by Repeaters 2635 rptrHealth NOTIFICATION-TYPE 2636 OBJECTS { rptrOperStatus } 2637 STATUS deprecated 2638 DESCRIPTION 2639 "In a system containing a single managed repeater, 2640 the rptrHealth notification conveys information 2641 related to the operational status of the repeater. 2642 It is sent either when the value of 2643 rptrOperStatus changes, or upon completion of a 2644 non-disruptive test. 2646 The rptrHealth notification must contain the 2647 rptrOperStatus object. The agent may optionally 2648 include the rptrHealthText object in the varBind 2649 list. See the rptrOperStatus and rptrHealthText 2650 objects for descriptions of the information that 2651 is sent. 2653 The agent must throttle the generation of 2654 consecutive rptrHealth traps so that there is at 2655 least a five-second gap between traps of this 2656 type. When traps are throttled, they are dropped, 2657 not queued for sending at a future time. (Note 2658 that 'generating' a trap means sending to all 2659 configured recipients.)" 2660 REFERENCE 2661 "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth 2662 notification." 2663 ::= { snmpDot3RptrMgt 0 1 } 2665 rptrGroupChange NOTIFICATION-TYPE 2666 OBJECTS { rptrGroupIndex } 2667 STATUS deprecated 2668 DESCRIPTION 2669 "In a system containing a single managed repeater, 2670 this notification is sent when a change occurs in the 2671 group structure of the repeater. This occurs only 2672 when a group is logically or physically removed 2673 from or added to a repeater. The varBind list 2674 contains the identifier of the group that was 2675 removed or added. 2677 The agent must throttle the generation of 2678 consecutive rptrGroupChange traps for the same 2679 group so that there is at least a five-second gap 2680 between traps of this type. When traps are 2681 throttled, they are dropped, not queued for 2682 sending at a future time. (Note that 'generating' 2683 a trap means sending to all configured 2684 recipients.)" 2685 REFERENCE 2686 "[IEEE 802.3 Mgt], 30.4.1.3.3, nGroupMapChange 2687 notification." 2688 ::= { snmpDot3RptrMgt 0 2 } 2690 rptrResetEvent NOTIFICATION-TYPE 2691 OBJECTS { rptrOperStatus } 2692 STATUS deprecated 2693 DESCRIPTION 2694 "In a system containing a single managed repeater-unit, 2695 the rptrResetEvent notification conveys information 2696 related to the operational status of the repeater. 2697 This trap is sent on completion of a repeater 2698 reset action. A repeater reset action is defined 2699 as an a transition to the START state of Fig 9-2 2700 in section 9 [IEEE 802.3 Std], when triggered by a 2701 management command (e.g., an SNMP Set on the 2702 rptrReset object). 2704 The agent must throttle the generation of 2705 consecutive rptrResetEvent traps so that there is 2706 at least a five-second gap between traps of this 2707 type. When traps are throttled, they are dropped, 2708 not queued for sending at a future time. (Note 2709 that 'generating' a trap means sending to all 2710 configured recipients.) 2712 The rptrResetEvent trap is not sent when the agent 2713 restarts and sends an SNMP coldStart or warmStart 2714 trap. However, it is recommended that a repeater 2715 agent send the rptrOperStatus object as an 2716 optional object with its coldStart and warmStart 2717 trap PDUs. 2719 The rptrOperStatus object must be included in the 2720 varbind list sent with this trap. The agent may 2721 optionally include the rptrHealthText object as 2722 well." 2723 REFERENCE 2724 "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset 2725 notification." 2726 ::= { snmpDot3RptrMgt 0 3 } 2728 -- Notifications for repeaters in a multiple-repeater implementation. 2729 -- An implementation may send either the single-repeater OR 2730 -- multiple-repeater version of these notifications (1 or 4; 2 or 5) 2731 -- but not both. 2733 rptrInfoHealth NOTIFICATION-TYPE 2734 OBJECTS { rptrInfoOperStatus } 2735 STATUS current 2736 DESCRIPTION 2737 "In a system containing multiple managed repeaters, 2738 the rptrInfoHealth notification conveys information 2739 related to the operational status of a repeater. 2740 It is sent either when the value of rptrInfoOperStatus 2741 changes, or upon completion of a non-disruptive test. 2743 The agent must throttle the generation of 2744 consecutive rptrInfoHealth notifications for 2745 the same repeater so that there is at least 2746 a five-second gap between notifications of this type. 2747 When notifications are throttled, they are dropped, 2748 not queued for sending at a future time. (Note 2749 that 'generating' a notification means sending 2750 to all configured recipients.)" 2752 REFERENCE 2753 "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth 2754 notification." 2755 ::= { snmpDot3RptrMgt 0 4 } 2757 rptrInfoResetEvent NOTIFICATION-TYPE 2758 OBJECTS { rptrInfoOperStatus } 2759 STATUS current 2760 DESCRIPTION 2761 "In a system containing multiple managed 2762 repeaters, the rptrInfoResetEvent notification 2763 conveys information related to the operational 2764 status of a repeater. This notification is sent 2765 on completion of a repeater reset action. A 2766 repeater reset action is defined as a transition 2767 to the START state of Fig 9-2 in section 9 of 2768 [IEEE 802.3 Std], when triggered by a management 2769 command (e.g., an SNMP Set on the rptrInfoReset 2770 object). 2772 The agent must throttle the generation of 2773 consecutive rptrInfoResetEvent notifications for 2774 a single repeater so that there is at least 2775 a five-second gap between notifications of 2776 this type. When notifications are throttled, 2777 they are dropped, not queued for sending at 2778 a future time. (Note that 'generating' a 2779 notification means sending to all configured 2780 recipients.) 2782 The rptrInfoResetEvent trap is not sent when the 2783 agent restarts and sends an SNMP coldStart or 2784 warmStart trap. However, it is recommended that 2785 a repeater agent send the rptrInfoOperStatus 2786 object as an optional object with its coldStart 2787 and warmStart trap PDUs." 2788 REFERENCE 2789 "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset 2790 notification." 2791 ::= { snmpDot3RptrMgt 0 5 } 2793 -- Conformance information 2795 snmpRptrModConf 2796 OBJECT IDENTIFIER ::= { snmpRptrMod 1 } 2797 snmpRptrModCompls 2798 OBJECT IDENTIFIER ::= { snmpRptrModConf 1 } 2799 snmpRptrModObjGrps 2800 OBJECT IDENTIFIER ::= { snmpRptrModConf 2 } 2801 snmpRptrModNotGrps 2802 OBJECT IDENTIFIER ::= { snmpRptrModConf 3 } 2804 -- Object groups 2806 snmpRptrGrpBasic OBJECT-GROUP 2807 OBJECTS { rptrGroupCapacity, 2808 rptrOperStatus, 2809 rptrHealthText, 2810 rptrReset, 2811 rptrNonDisruptTest, 2812 rptrTotalPartitionedPorts, 2814 rptrGroupIndex, 2815 rptrGroupDescr, 2816 rptrGroupObjectID, 2817 rptrGroupOperStatus, 2818 rptrGroupLastOperStatusChange, 2819 rptrGroupPortCapacity, 2821 rptrPortGroupIndex, 2822 rptrPortIndex, 2823 rptrPortAdminStatus, 2824 rptrPortAutoPartitionState, 2825 rptrPortOperStatus } 2826 STATUS deprecated 2827 DESCRIPTION 2828 "Basic group from RFCs 1368 and 1516. 2830 NOTE: this object group is DEPRECATED and replaced 2831 with snmpRptrGrpBasicRS." 2832 ::= { snmpRptrModObjGrps 1 } 2834 snmpRptrGrpMonitor OBJECT-GROUP 2835 OBJECTS { rptrMonitorTransmitCollisions, 2837 rptrMonitorGroupIndex, 2838 rptrMonitorGroupTotalFrames, 2839 rptrMonitorGroupTotalOctets, 2840 rptrMonitorGroupTotalErrors, 2842 rptrMonitorPortGroupIndex, 2843 rptrMonitorPortIndex, 2844 rptrMonitorPortReadableFrames, 2845 rptrMonitorPortReadableOctets, 2846 rptrMonitorPortFCSErrors, 2847 rptrMonitorPortAlignmentErrors, 2848 rptrMonitorPortFrameTooLongs, 2849 rptrMonitorPortShortEvents, 2850 rptrMonitorPortRunts, 2851 rptrMonitorPortCollisions, 2852 rptrMonitorPortLateEvents, 2853 rptrMonitorPortVeryLongEvents, 2854 rptrMonitorPortDataRateMismatches, 2855 rptrMonitorPortAutoPartitions, 2856 rptrMonitorPortTotalErrors } 2857 STATUS deprecated 2858 DESCRIPTION 2859 "Monitor group from RFCs 1368 and 1516. 2861 NOTE: this object group is DEPRECATED and replaced 2862 with snmpRptrGrpMonitorRS." 2863 ::= { snmpRptrModObjGrps 2 } 2865 snmpRptrGrpAddrTrack OBJECT-GROUP 2866 OBJECTS { rptrAddrTrackGroupIndex, 2867 rptrAddrTrackPortIndex, 2868 rptrAddrTrackLastSourceAddress, 2869 rptrAddrTrackSourceAddrChanges } 2870 STATUS obsolete 2871 DESCRIPTION 2872 "Address tracking group from RFC 1368. 2874 NOTE: this object group is OBSOLETE and replaced 2875 with snmpRptrGrpAddrTrackNewSrcAddr." 2876 ::= { snmpRptrModObjGrps 3 } 2878 snmpRptrGrpAddrTrackNewSrcAddr OBJECT-GROUP 2879 OBJECTS { rptrAddrTrackGroupIndex, 2880 rptrAddrTrackPortIndex, 2881 rptrAddrTrackLastSourceAddress, 2882 rptrAddrTrackSourceAddrChanges, 2883 rptrAddrTrackNewLastSrcAddress } 2884 STATUS deprecated 2885 DESCRIPTION 2886 "Address tracking group from RFC 1516. 2888 NOTE: this object group is DEPRECATED and 2889 replaced with snmpRptrGrpAddrTrackRS." 2890 ::= { snmpRptrModObjGrps 4 } 2892 snmpRptrGrpBasicRS OBJECT-GROUP 2893 OBJECTS { rptrGroupIndex, 2894 rptrGroupDescr, 2895 rptrGroupObjectID, 2896 rptrGroupOperStatus, 2897 rptrGroupLastOperStatusChange, 2898 rptrGroupPortCapacity, 2900 rptrPortGroupIndex, 2901 rptrPortIndex, 2902 rptrPortAdminStatus, 2903 rptrPortAutoPartitionState, 2904 rptrPortOperStatus, 2905 rptrPortRptrId, 2907 rptrInfoId, 2908 rptrInfoRptrType, 2909 rptrInfoOperStatus, 2910 rptrInfoReset, 2911 rptrInfoNonDisruptTest, 2912 rptrInfoPartitionedPorts, 2913 rptrInfoLastChange } 2914 STATUS current 2915 DESCRIPTION 2916 "Basic group for a system with one or more 2917 repeater-units in restart version of the MIB 2918 module." 2919 ::= { snmpRptrModObjGrps 5 } 2921 snmpRptrGrpMonitorRS OBJECT-GROUP 2922 OBJECTS { rptrMonitorPortGroupIndex, 2923 rptrMonitorPortIndex, 2924 rptrMonitorPortReadableFrames, 2925 rptrMonitorPortReadableOctets, 2926 rptrMonitorPortFCSErrors, 2927 rptrMonitorPortAlignmentErrors, 2928 rptrMonitorPortFrameTooLongs, 2929 rptrMonitorPortShortEvents, 2930 rptrMonitorPortRunts, 2931 rptrMonitorPortCollisions, 2932 rptrMonitorPortLateEvents, 2933 rptrMonitorPortVeryLongEvents, 2934 rptrMonitorPortDataRateMismatches, 2935 rptrMonitorPortAutoPartitions, 2936 rptrMonitorPortTotalErrors, 2937 rptrMonitorPortLastChange, 2939 rptrMonTxCollisions, 2940 rptrMonTotalFrames, 2941 rptrMonTotalErrors, 2942 rptrMonTotalOctets } 2943 STATUS current 2944 DESCRIPTION 2945 "Monitor group for a system with one or more 2946 repeater-units in restart version of the MIB 2947 module." 2948 ::= { snmpRptrModObjGrps 6 } 2950 snmpRptrGrpMonitor100RS OBJECT-GROUP 2951 OBJECTS { rptrMonitorPortIsolates, 2952 rptrMonitorPortSymbolErrors, 2953 rptrMonitorPortUpper32Octets, 2954 rptrMonitorPortHCReadableOctets, 2956 rptrMonUpper32TotalOctets, 2957 rptrMonHCTotalOctets } 2958 STATUS current 2959 DESCRIPTION 2960 "Monitor group for 100Mb/s ports and repeaters in a 2961 system with one or more repeater-units in restart 2962 version of the MIB module." 2963 ::= { snmpRptrModObjGrps 7 } 2965 snmpRptrGrpAddrTrackRS OBJECT-GROUP 2966 OBJECTS { rptrAddrTrackGroupIndex, 2967 rptrAddrTrackPortIndex, 2968 rptrAddrTrackSourceAddrChanges, 2969 rptrAddrTrackNewLastSrcAddress, 2970 rptrAddrTrackCapacity } 2971 STATUS current 2972 DESCRIPTION 2973 "Address tracking group for restart version 2974 of the MIB module." 2976 ::= { snmpRptrModObjGrps 8 } 2978 snmpRptrGrpExtAddrTrack OBJECT-GROUP 2979 OBJECTS { rptrExtAddrTrackMacIndex, 2980 rptrExtAddrTrackSourceAddress, 2981 rptrAddrTrackReset } 2982 STATUS current 2983 DESCRIPTION 2984 "Extended address tracking group for a system 2985 with one or more repeater-units in restart 2986 version of the MIB module." 2987 ::= { snmpRptrModObjGrps 9 } 2989 snmpRptrGrpTopNPort OBJECT-GROUP 2990 OBJECTS { rptrTopNPortControlIndex, 2991 rptrTopNPortRepeaterId, 2992 rptrTopNPortRateBase, 2993 rptrTopNPortTimeRemaining, 2994 rptrTopNPortDuration, 2995 rptrTopNPortRequestedSize, 2996 rptrTopNPortGrantedSize, 2997 rptrTopNPortStartTime, 2998 rptrTopNPortOwner, 2999 rptrTopNPortRowStatus, 3000 rptrTopNPortIndex, 3001 rptrTopNPortGroupIndex, 3002 rptrTopNPortPortIndex, 3003 rptrTopNPortRate } 3004 STATUS current 3005 DESCRIPTION 3006 "Top `N' group for repeater ports." 3007 ::= { snmpRptrModObjGrps 10 } 3009 -- Notification groups 3011 -- ?? later 3013 -- Compliances 3015 snmpRptrModComplRFC1368 MODULE-COMPLIANCE 3016 STATUS obsolete 3017 DESCRIPTION 3018 "Compliance for RFC 1368. 3020 NOTE: this module compliance is OBSOLETE and 3021 replaced by snmpRptrModComplRFC1516." 3023 MODULE -- this module 3024 MANDATORY-GROUPS { snmpRptrGrpBasic } 3026 GROUP snmpRptrGrpMonitor 3027 DESCRIPTION 3028 "Implementation of this optional group is 3029 recommended for systems which have the 3030 instrumentation to do performance monitoring." 3032 GROUP snmpRptrGrpAddrTrack 3033 DESCRIPTION 3034 "Implementation of this group is 3035 recommended for systems which have 3036 the necessary instrumentation." 3038 ::= { snmpRptrModCompls 1 } 3040 snmpRptrModComplRFC1516 MODULE-COMPLIANCE 3041 STATUS deprecated 3042 DESCRIPTION 3043 "Compliance for RFC 1516 and for backwards 3044 compatibility with single-repeater, 3045 10Mb/s-only implementations." 3047 MODULE -- this module 3048 MANDATORY-GROUPS { snmpRptrGrpBasic } 3050 GROUP snmpRptrGrpMonitor 3051 DESCRIPTION 3052 "Implementation of this optional group is 3053 recommended for systems which have the 3054 instrumentation to do performance monitoring." 3056 GROUP snmpRptrGrpAddrTrackNewSrcAddr 3057 DESCRIPTION 3058 "Implementation of this group is 3059 recommended for systems which have 3060 the necessary instrumentation." 3062 ::= { snmpRptrModCompls 2 } 3064 snmpRptrModComplRS MODULE-COMPLIANCE 3065 STATUS current 3066 DESCRIPTION 3067 "Compliance for the `restart version' of the 3068 MIB module for a system with one or more 3069 repeater-units." 3071 MODULE -- this module 3072 MANDATORY-GROUPS { snmpRptrGrpBasicRS } 3074 GROUP snmpRptrGrpMonitorRS 3075 DESCRIPTION 3076 "Implementation of this optional group is 3077 recommended for systems which have the 3078 instrumentation to do performance monitoring." 3080 GROUP snmpRptrGrpMonitor100RS 3081 DESCRIPTION 3082 "Implementation of this optional group 3083 is recommended for systems which contain 3084 100Mb/s repeaters and have the 3085 instrumentation to do performance 3086 monitoring." 3088 GROUP snmpRptrGrpAddrTrackRS 3089 DESCRIPTION 3090 "Implementation of this group is 3091 recommended for systems which have 3092 the necessary instrumentation to 3093 track MAC address of a single DTE 3094 attached to a repeater port." 3096 GROUP snmpRptrGrpExtAddrTrack 3097 DESCRIPTION 3098 "Implementation of this group is 3099 appropriate for systems which have 3100 the necessary instrumentation to track 3101 MAC addresses of multiple DTEs attached 3102 to a single repeater port." 3104 GROUP snmpRptrGrpTopNPort 3105 DESCRIPTION 3106 "Implementation of this group is 3107 recommended for systems which have 3108 the necessary resources to support 3109 TopN statistics reporting." 3111 ::= { snmpRptrModCompls 3 } 3113 END 3114 4. References 3116 [1] IEEE 802.3/ISO 8802-3 Information processing systems - 3117 Local area networks - Part 3: Carrier sense multiple 3118 access with collision detection (CSMA/CD) access method 3119 and physical layer specifications, 1993. 3121 [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium 3122 Attachment Units and Repeater for 100 Mb/s Operation, 3123 Type 100BASE-T," Sections 21 through 29, Supplement to 3124 IEEE Std 802.3, October 26, 1995. 3126 [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, 3127 Supplement to IEEE Std 802.3, October 26, 1995. 3129 [4] Romascanu, D., and K. de Graaf, "Definitions of Managed 3130 Objects for IEEE 802.3 Medium Attachment Units (MAUs)", 3131 February 1996. 3133 [5] McCloghrie, K., and M. Rose, Editors, "Management 3134 Information Base for Network Management of TCP/IP-based 3135 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 3136 Performance Systems International, March 1991.