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