--- 1/draft-ietf-hubmib-repeater-dev-02.txt 2006-02-04 23:26:35.000000000 +0100 +++ 2/draft-ietf-hubmib-repeater-dev-03.txt 2006-02-04 23:26:35.000000000 +0100 @@ -1,45 +1,48 @@ Definitions of Managed Objects for IEEE 802.3 Repeater Devices - 14 May 1996 + 14 September 1996 - + + + Kathryn de Graaf + 3Com Corporation Dan Romascanu Madge Networks (Israel) Ltd. - dromasca@madge.com - Kathryn de Graaf - 3Com Corporation - kdegraaf@isd.3com.com + Donna McMaster + Coloma Communications + Keith McCloghrie + Cisco Systems Inc. + +, Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as a "work in progress". To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), - -, or munnari.oz.au (Pacific Rim). Abstract This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 10 and 100 Mb/second baseband repeaters based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995. @@ -49,40 +52,39 @@ 1. The SNMP Network Management Framework The SNMP Network Management Framework presently consists of three major components. They are: o the SMI, described in RFC 1902 [6] - the mechanisms used for describing and naming objects for the purpose of management. +, o the MIB-II, STD 17, RFC 1213 [5] - the core set of managed objects for the Internet suite of protocols. o the protocol, RFC 1157 [10] and/or RFC 1905 [9] - the protocol used for accessing managed information. Textual conventions are defined in RFC 1903 [7], and conformance statements are defined in RFC 1904 [8]. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 1.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object - -, type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. , 2. Overview 2.1. Relationship to RFC 1516 @@ -226,36 +228,33 @@ higher-level protocol entity. However, this is only a means of implementing management, and this passing of management information is not part of the repeater functionality.) , 3. Definitions SNMP-REPEATER-MIB DEFINITIONS ::= BEGIN IMPORTS - --experimental, - Counter32, Counter64, Integer32, Gauge32, - TimeTicks, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE + Counter32, Counter64, Integer32, Gauge32, TimeTicks, + OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 FROM SNMPv2-SMI TimeStamp, DisplayString, MacAddress, TEXTUAL-CONVENTION, RowStatus, TestAndIncr FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF - mib-2 - FROM RFC1213-MIB OwnerString - FROM RFC1271-MIB; + FROM IF-MIB; snmpRptrMod MODULE-IDENTITY - LAST-UPDATED "9605140000Z" + LAST-UPDATED "9609140000Z" ORGANIZATION "IETF HUB MIB Working Group" CONTACT-INFO "WG E-mail: hubmib@hprnd.rose.hp.com Chair: Dan Romascanu Postal: Madge Networks (Israel) Ltd. Atidim Technology Park, Bldg. 3 Tel Aviv 61131, Israel Tel: 972-3-6458414, 6458458 Fax: 972-3-6487146 @@ -264,24 +263,24 @@ Editor: Kathryn de Graaf Postal: 3Com Corporation 118 Turnpike Rd. Southborough, MA 01772 USA Tel: (508)229-1627 Fax: (508)490-5882 E-mail: kdegraaf@isd.3com.com" DESCRIPTION "Management information for 802.3 repeaters. -, The following references are used throughout this MIB module: +, [IEEE 802.3 Std] refers to IEEE 802.3/ISO 8802-3 Information processing systems - Local area networks - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications (1993). [IEEE 802.3 Mgt] refers to IEEE 802.3u-1995, '10 Mb/s & 100 Mb/s Management, Section 30,' @@ -310,25 +309,24 @@ package. Trivial repeater-unit - An isolated port that can gather statistics. Group - A recommended, but optional, entity defined by the IEEE 802.3 management standard, in order to support a modular numbering scheme. The classical example allows an implementor to represent field-replaceable units as groups of - -, ports, with the port numbering matching the modular hardware implementation. +, System interconnect segment - An internal segment allowing interconnection of ports belonging to different physical entities into the same logical manageable repeater. Examples of implementation might be backplane busses in modular hubs, or chaining cables in stacks of hubs. Stack - A scalable system that may include managed repeaters, in which modularity is @@ -354,25 +352,25 @@ OptMacAddr ::= TEXTUAL-CONVENTION DISPLAY-HINT "1x:" STATUS current DESCRIPTION "Either a 6 octet address in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first if a value is available or a zero length string." REFERENCE - -, "See MacAddress in SNMPv2-TC. The only difference is that a zero length string is allowed as a value for OptMacAddr and not for MacAddress." + +, SYNTAX OCTET STRING (SIZE (0 | 6)) -- Basic information at the repeater, group, and port level. rptrBasicPackage OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 1 } rptrRptrInfo OBJECT IDENTIFIER ::= { rptrBasicPackage 1 } rptrGroupInfo OBJECT IDENTIFIER ::= { rptrBasicPackage 2 } @@ -399,25 +397,25 @@ OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 3 } rptrAddrTrackRptrInfo OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 1 } rptrAddrTrackGroupInfo -- this subtree is currently unused OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 2 } rptrAddrTrackPortInfo OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 3 } -- TopN information. - -, rptrTopNPackage OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 4 } rptrTopNRptrInfo + +, -- this subtree is currently unused OBJECT IDENTIFIER ::= { rptrTopNPackage 1 } rptrTopNGroupInfo -- this subtree is currently unused OBJECT IDENTIFIER ::= { rptrTopNPackage 2 } rptrTopNPortInfo OBJECT IDENTIFIER ::= { rptrTopNPackage 3 } -- Old version of basic information at the repeater level. -- @@ -446,23 +444,24 @@ that can be contained within the repeater. Within each managed repeater, the groups are uniquely numbered in the range from 1 to rptrGroupCapacity. Some groups may not be present in the repeater, in which case the actual number of groups present will be less than rptrGroupCapacity. The number of groups present will never be greater than rptrGroupCapacity. -, Note: In practice, this will generally be the number of field-replaceable units (i.e., modules, + +, cards, or boards) that can fit in the physical repeater enclosure, and the group numbers will correspond to numbers marked on the physical enclosure." REFERENCE "[IEEE 802.3 Mgt], 30.4.1.1.3, aRepeaterGroupCapacity." ::= { rptrRptrInfo 1 } rptrOperStatus OBJECT-TYPE @@ -492,23 +491,24 @@ priority first: rptrFailure(3) groupFailure(4) portFailure(5) generalFailure(6)." REFERENCE "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState." ::= { rptrRptrInfo 2 } -, rptrHealthText OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) + +, MAX-ACCESS read-only STATUS deprecated DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** The health text object is a text string that provides information relevant to the operational state of the repeater. Agents may use this string to provide detailed information on current failures, including how they were detected, and/or @@ -538,23 +538,24 @@ The agent will always return the value noReset(1) when this object is read. After receiving a request to set this variable to reset(2), the agent is allowed to delay the reset for a short period. For example, the implementor may choose to delay the reset long enough to allow the SNMP response to be transmitted. In any event, the SNMP response must be transmitted. -, This action does not reset the management counters defined in this document nor does it affect the + +, portAdminStatus parameters. Included in this action is the execution of a disruptive Self-Test with the following characteristics: a) The nature of the tests is not specified. b) The test resets the repeater but without affecting management information about the repeater. c) The test does not inject packets onto any segment. d) Packets received during the test may or may not be transferred. e) The test does not interfere with management functions. @@ -584,24 +585,23 @@ not specified. b) The test does not change the state of the repeater or management information about the repeater. c) The test does not inject packets onto any segment. d) The test does not prevent the relay of any packets. e) The test does not interfere with management functions. After performing this test, the agent will update the repeater health information (including rptrOperStatus and rptrHealthText) and send a - -, rptrHealth trap. +, Note that this definition allows returning an 'okay' result after doing a trivial test. Setting this object to noSelfTest(1) has no effect. The agent will always return the value noSelfTest(1) when this object is read." REFERENCE "[IEEE 802.3 Mgt], 30.4.1.2.2, acExecuteNonDisruptiveSelfTest." ::= { rptrRptrInfo 5 } @@ -630,22 +630,23 @@ rptrGroupTable OBJECT-TYPE SYNTAX SEQUENCE OF RptrGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of descriptive and status information about the groups of ports." ::= { rptrGroupInfo 1 } -, rptrGroupEntry OBJECT-TYPE + +, SYNTAX RptrGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table, containing information about a single group of ports." INDEX { rptrGroupIndex } ::= { rptrGroupTable 1 } RptrGroupEntry ::= @@ -676,22 +677,23 @@ "[IEEE 802.3 Mgt], 30.4.2.1.1, aGroupID." ::= { rptrGroupEntry 1 } rptrGroupDescr OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** -, A textual description of the group. This value + +, should include the full name and version identification of the group's hardware type and indicate how the group is differentiated from other types of groups in the repeater. Plug-in Module, Rev A' or 'Barney Rubble 10BASE-T 4-port SIMM socket Version 2.1' are examples of valid group descriptions. It is mandatory that this only contain printable ASCII characters." @@ -722,24 +724,23 @@ operational(2), malfunctioning(3), notPresent(4), underTest(5), resetInProgress(6) } MAX-ACCESS read-only STATUS current DESCRIPTION "An object that indicates the operational status - -, of the group. +, A status of notPresent(4) indicates that the group is temporarily or permanently physically and/or logically not a part of the repeater. It is an implementation-specific matter as to whether the agent effectively removes notPresent entries from the table. A status of operational(2) indicates that the group is functioning, and a status of malfunctioning(3) indicates that the group is @@ -770,22 +771,23 @@ SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The rptrGroupPortCapacity is the number of ports that can be contained within the group. Valid range is 1-2147483647. Within each group, the ports are uniquely numbered in the range from 1 to rptrGroupPortCapacity. -, Some ports may not be present in the system, in + +, which case the actual number of ports present will be less than the value of rptrGroupPortCapacity. The number of ports present in the group will never be greater than the value of rptrGroupPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment." REFERENCE @@ -815,23 +817,23 @@ MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table, containing information about a single port." INDEX { rptrPortGroupIndex, rptrPortIndex } ::= { rptrPortTable 1 } RptrPortEntry ::= SEQUENCE { + rptrPortGroupIndex , - rptrPortGroupIndex Integer32, rptrPortIndex Integer32, rptrPortAdminStatus INTEGER, rptrPortAutoPartitionState INTEGER, rptrPortOperStatus INTEGER, rptrPortRptrId @@ -862,23 +864,23 @@ REFERENCE "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." ::= { rptrPortEntry 2 } rptrPortAdminStatus OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write + STATUS current , - STATUS current DESCRIPTION "Setting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The admin status takes precedence over auto- @@ -909,23 +911,23 @@ STATUS current DESCRIPTION "The autoPartitionState flag indicates whether the port is currently partitioned by the repeater's auto-partition protection. The conditions that cause port partitioning are specified in partition state machine in Sections 9 and 27 of [IEEE 802.3 Std]. They are not differentiated here." + REFERENCE , - REFERENCE "[IEEE 802.3 Mgt], 30.4.3.1.3, aAutoPartitionState." ::= { rptrPortEntry 4 } rptrPortOperStatus OBJECT-TYPE SYNTAX INTEGER { operational(1), notOperational(2), notPresent(3) } MAX-ACCESS read-only @@ -955,23 +957,23 @@ which this port belongs. The repeater identified by a particular value of this object is the same as that identified by the same value of rptrInfoId. A value of zero indicates that this port currently is not a member of any repeater." ::= { rptrPortEntry 6 } -- New version of basic information at the repeater level. -- + -- Configuration, status, and control objects for , - -- Configuration, status, and control objects for -- each managed repeater in the system. rptrInfoTable OBJECT-TYPE SYNTAX SEQUENCE OF RptrInfoEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of information about each non-trivial repeater. The number of entries depends on the physical configuration of the @@ -1002,23 +1004,23 @@ Gauge32, rptrInfoLastChange TimeStamp } rptrInfoId OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION + "This object identifies the repeater for which , - "This object identifies the repeater for which this entry contains information." ::= { rptrInfoEntry 1 } rptrInfoRptrType OBJECT-TYPE SYNTAX INTEGER { other(1), -- undefined or unknown tenMb(2), onehundredMbClassI(3), onehundredMbClassII(4) } @@ -1049,23 +1051,23 @@ rptrInfoReset OBJECT-TYPE SYNTAX INTEGER { noReset(1), reset(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to reset(2) causes a transition to the START state of Fig 9-2 in + section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, , - section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, and to the START state of Fig 27-2 in section 27 of that standard for a 100Mb/s repeater. Setting this object to noReset(1) has no effect. The agent will always return the value noReset(1) when this object is read. After receiving a request to set this variable to reset(2), the agent is allowed to delay the reset for a short period. For example, the implementor @@ -1081,21 +1083,22 @@ of the tests is not specified. b) The test resets the repeater but without affecting management information about the repeater. c) The test does not inject packets onto any segment. d) Packets received during the test may or may not be transferred. e) The test does not interfere with management functions. After performing this self-test, the agent will update the repeater health information (including - rptrInfoOperStatus), and send a rptrInfoHealth trap." + rptrInfoOperStatus), and send a rptrInfoResetEvent + notification." REFERENCE "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." ::= { rptrInfoEntry 4 } rptrInfoPartitionedPorts OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object returns the total number of ports in @@ -2670,83 +2673,74 @@ rptrExtAddrTrackMacIndex Integer32, rptrExtAddrTrackSourceAddress MacAddress } rptrExtAddrTrackMacIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The index of a source MAC address seen on - the port." + the port. + + The ordering of MAC addresses listed for a + particular port is implementation dependent. + + There is no implied relationship between a + particular index and a particular MAC + +, + address. The index for a particular MAC + address may change without notice." ::= { rptrExtAddrTrackEntry 1 } rptrExtAddrTrackSourceAddress OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-only STATUS current - -, DESCRIPTION "The source MAC address from a readable frame (i.e., counted by rptrMonitorPortReadableFrames) recently received by the port." REFERENCE "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." ::= { rptrExtAddrTrackEntry 2 } - rptrAddrTrackReset OBJECT-TYPE - SYNTAX INTEGER { - noReset(1), - reset(2) - } - MAX-ACCESS read-write - STATUS current - DESCRIPTION - "Setting this object to reset(2) causes - the agent to empty the contents of the - rptrExtAddrTrackTable. The contents of - the rptrAddrTrackTable are not affected. - - Setting this object to noReset(1) has no effect. - The agent will always return the value noReset(1) - when this object is read." - ::= { rptrAddrTrackPortInfo 3 } - -- The Repeater Top "N" Port Group -- The Repeater Top N Port group is used to prepare reports that -- describe a list of ports ordered by one of the statistics in the -- Repeater Monitor Port Table. The statistic chosen by the -- management station is sampled over a management -- station-specified time interval, making the report rate based. -- The management station also specifies the number of ports that -- are reported. -- -- The rptrTopNPortControlTable is used to initiate the generation -- of a report. The management station may select the parameters -- of such a report, such as which repeater, which statistic, how -- many ports, and the start & stop times of the sampling. When -- the report is prepared, entries are created in the -- rptrTopNPortTable associated with the relevent -- rptrTopNControlEntry. These entries are static for -- each report after it has been prepared. -, -- Note that counter discontinuities may appear in some -- implementations if ports' assignment to repeaters changes -- during the collection of data for a Top "N" report. -- A management application could read the corresponding -- rptrMonitorPortLastChange timestamp in order to check -- whether a discontinuity occurred. rptrTopNPortControlTable OBJECT-TYPE + +, SYNTAX SEQUENCE OF RptrTopNPortControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of control records for reports on the top `N' ports for the rate of a selected counter. The number of entries depends on the configuration of the agent. The maximum number of entries is implementation dependent." ::= { rptrTopNPortInfo 1 } @@ -2769,31 +2763,31 @@ rptrTopNPortRateBase INTEGER, rptrTopNPortTimeRemaining Integer32, rptrTopNPortDuration Integer32, rptrTopNPortRequestedSize Integer32, rptrTopNPortGrantedSize Integer32, - -, rptrTopNPortStartTime TimeStamp, rptrTopNPortOwner OwnerString, rptrTopNPortRowStatus RowStatus } rptrTopNPortControlIndex OBJECT-TYPE + +, SYNTAX Integer32 (1 .. 65535) MAX-ACCESS read-only STATUS current DESCRIPTION "An index that uniquely identifies an entry in the rptrTopNPortControl table. Each such entry defines one top N report prepared for a repeater or system." ::= { rptrTopNPortControlEntry 1 } rptrTopNPortRepeaterId OBJECT-TYPE @@ -2803,42 +2797,56 @@ DESCRIPTION "Identifies the repeater for which a top N report will be prepared (see rptrInfoId). If the value of this object is positive, only ports assigned to this repeater will be used to form the list in which to order the Top N table. If this value is zero, all ports will be eligible for inclusion on the list. The value of this object may not be modified if the associated rptrTopNPortRowStatus object is equal to - active(1)." + active(1). + + If, for a particular row in this table, the repeater + specified by the value of this object goes away (is + removed from the rptrInfoTable) while the associated + rptrTopNPortRowStatus object is equal to active(1), + the row in this table is preserved by the agent but + the value of rptrTopNPortRowStatus is changed to + notInService(2), and the agent may time out the row + if appropriate. If the specified repeater comes + back (reappears in the rptrInfoTable) before the row + has been timed out, the management station must set + the value of the rptrTopNPortRowStatus object back + to active(1) if desired (the agent doesn't do this + automatically)." ::= { rptrTopNPortControlEntry 2 } rptrTopNPortRateBase OBJECT-TYPE SYNTAX INTEGER { - rptrMonitorPortReadableFrames(1), - rptrMonitorPortReadableOctets(2), - rptrMonitorPortFCSErrors(3), - rptrMonitorPortAlignmentErrors(4), - rptrMonitorPortFrameTooLongs(5), - rptrMonitorPortShortEvents(6), - rptrMonitorPortRunts(7), - rptrMonitorPortCollisions(8), + readableFrames(1), + readableOctets(2), + fcsErrors(3), , - rptrMonitorPortLateEvents(9), - rptrMonitorPortVeryLongEvents(10), - rptrMonitorPortDataRateMismatches(11), - rptrMonitorPortAutoPartitions(12), - rptrMonitorPortTotalErrors(13), - rptrMonitorPortIsolates(14), - rptrMonitorPortSymbolErrors(15) + alignmentErrors(4), + frameTooLongs(5), + shortEvents(6), + runts(7), + collisions(8), + lateEvents(9), + veryLongEvents(10), + dataRateMismatches(11), + autoPartitions(12), + totalErrors(13), + isolates(14), + symbolErrors(15) } MAX-ACCESS read-create STATUS current DESCRIPTION "The monitored variable, which the rptrTopNPortRate variable is based upon. The value of this object may not be modified if the associated rptrTopNPortRowStatus object has a value of active(1)." @@ -2858,27 +2866,32 @@ which is loaded into the associated rptrTopNPortDuration object. When this object is set to a non-zero value, any associated rptrTopNPortEntries shall be made inaccessible by the agent. While the value of this object is non-zero, it decrements by one per second until it reaches zero. During this time, all associated rptrTopNPortEntries shall remain inaccessible. At the time that this object + +, decrements to zero, the report is made accessible in the rptrTopNPortTable. Thus, the rptrTopNPort table needs to be created only at the end of the - collection interval." - DEFVAL { 0 } + collection interval. -, + If the value of this object is set to zero + while the associated report is running, the + running report is aborted and no associated + rptrTopNPortEntries are created." + DEFVAL { 0 } ::= { rptrTopNPortControlEntry 4 } rptrTopNPortDuration OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of seconds that this report has collected during the last sampling interval, or if this report is currently being collected, @@ -2900,78 +2913,87 @@ MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of repeater ports requested for the Top N Table. When this object is created or modified, the agent should set rptrTopNPortGrantedSize as close to this object as is possible for the particular implementation and available resources." + +, DEFVAL { 10 } ::= { rptrTopNPortControlEntry 6 } rptrTopNPortGrantedSize OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of repeater ports in the top N table. -, When the associated rptrTopNPortRequestedSize object is created or modified, the agent should set this object as closely to the requested value as is possible for the particular implementation and available resources. The agent must not lower this value except as a result of a set to the associated rptrTopNPortRequestedSize object." ::= { rptrTopNPortControlEntry 7 } rptrTopNPortStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated rptrTopNPortTimeRemaining object was - modified to start the requested report." + modified to start the requested report. + + If the report has not yet been started, the value + of this object is zero." ::= { rptrTopNPortControlEntry 8 } rptrTopNPortOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is using the resources assigned to it." ::= { rptrTopNPortControlEntry 9 } rptrTopNPortRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create + +, STATUS current DESCRIPTION - "The status of this row." + "The status of this row. + + If the value of this object is not equal to + active(1), all associated entries in the + rptrTopNPortTable shall be deleted by the + agent." ::= { rptrTopNPortControlEntry 10 } -- Top "N" reports rptrTopNPortTable OBJECT-TYPE SYNTAX SEQUENCE OF RptrTopNPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of reports for the top `N' ports based on - -, setting of associated control table entries. The maximum number of entries depends on the number of entries in table rptrTopNPortControlTable and the value of object rptrTopNPortGrantedSize for each entry. For each entry in the rptrTopNPortControlTable, repeater ports with the highest value of rptrTopNPortRate shall be placed in this table in decreasing order of that rate until there is @@ -2984,41 +3006,41 @@ STATUS current DESCRIPTION "A set of statistics for a repeater port that is part of a top N report." INDEX { rptrTopNPortControlIndex, rptrTopNPortIndex } ::= { rptrTopNPortTable 1 } RptrTopNPortEntry ::= SEQUENCE { rptrTopNPortIndex + +, Integer32, rptrTopNPortGroupIndex Integer32, rptrTopNPortPortIndex Integer32, rptrTopNPortRate Gauge32 } rptrTopNPortIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "An index that uniquely identifies an entry in the rptrTopNPort table among those in the same report. This index is between 1 and N, where N is the number of entries in this report. Increasing values of rptrTopNPortIndex shall be assigned to - -, entries with decreasing values of rptrTopNPortRate until index N is assigned to the entry with the lowest value of rptrTopNPortRate or there are no more rptrTopNPortEntries. No ports are included in a report where their value of rptrTopNPortRate would be zero." ::= { rptrTopNPortEntry 1 } rptrTopNPortGroupIndex OBJECT-TYPE @@ -3031,39 +3053,39 @@ type rptrGroupIndex.)" ::= { rptrTopNPortEntry 2 } rptrTopNPortPortIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The index of the repeater port. (See object type rptrPortIndex.)" + +, ::= { rptrTopNPortEntry 3 } rptrTopNPortRate OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The amount of change in the selected variable during this sampling interval for the identified port. The selected variable is that port's instance of the object selected by rptrTopNPortRateBase." ::= { rptrTopNPortEntry 4 } -- Notifications for use by Repeaters rptrHealth NOTIFICATION-TYPE - -, OBJECTS { rptrOperStatus } STATUS deprecated DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** In a system containing a single managed repeater, the rptrHealth notification conveys information related to the operational status of the repeater. It is sent either when the value of rptrOperStatus changes, or upon completion of a @@ -3076,40 +3098,41 @@ objects for descriptions of the information that is sent. The agent must throttle the generation of consecutive rptrHealth traps so that there is at least a five-second gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a trap means sending to all configured recipients.)" + +, REFERENCE "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth notification." ::= { snmpDot3RptrMgt 0 1 } rptrGroupChange NOTIFICATION-TYPE OBJECTS { rptrGroupIndex } STATUS deprecated DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** In a system containing a single managed repeater, this notification is sent when a change occurs in the group structure of the repeater. This occurs only when a group is logically or physically removed from or added to a repeater. The varBind list contains the identifier of the group that was removed or added. -, The agent must throttle the generation of consecutive rptrGroupChange traps for the same group so that there is at least a five-second gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a trap means sending to all configured recipients.)" REFERENCE "[IEEE 802.3 Mgt], 30.4.1.3.3, nGroupMapChange @@ -3122,41 +3145,41 @@ DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** In a system containing a single managed repeater-unit, the rptrResetEvent notification conveys information related to the operational status of the repeater. This trap is sent on completion of a repeater reset action. A repeater reset action is defined as an a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std], when triggered by a + +, management command (e.g., an SNMP Set on the rptrReset object). The agent must throttle the generation of consecutive rptrResetEvent traps so that there is at least a five-second gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a trap means sending to all configured recipients.) The rptrResetEvent trap is not sent when the agent restarts and sends an SNMP coldStart or warmStart trap. However, it is recommended that a repeater agent send the rptrOperStatus object as an optional object with its coldStart and warmStart trap PDUs. The rptrOperStatus object must be included in the - -, varbind list sent with this trap. The agent may optionally include the rptrHealthText object as well." REFERENCE "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset notification." ::= { snmpDot3RptrMgt 0 3 } -- Notifications for repeaters in a multiple-repeater implementation. -- An implementation may send either the single-repeater OR @@ -3168,86 +3191,86 @@ STATUS current DESCRIPTION "In a system containing multiple managed repeaters, the rptrInfoHealth notification conveys information related to the operational status of a repeater. It is sent either when the value of rptrInfoOperStatus changes, or upon completion of a non-disruptive test. The agent must throttle the generation of consecutive rptrInfoHealth notifications for + +, the same repeater so that there is at least a five-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a notification means sending to all configured recipients.)" REFERENCE "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth notification." ::= { snmpDot3RptrMgt 0 4 } rptrInfoResetEvent NOTIFICATION-TYPE OBJECTS { rptrInfoOperStatus } STATUS current DESCRIPTION "In a system containing multiple managed repeaters, the rptrInfoResetEvent notification conveys information related to the operational status of a repeater. This notification is sent - -, on completion of a repeater reset action. A repeater reset action is defined as a transition to the START state of Fig 9-2 in section 9 of [IEEE 802.3 Std], when triggered by a management command (e.g., an SNMP Set on the rptrInfoReset object). The agent must throttle the generation of consecutive rptrInfoResetEvent notifications for a single repeater so that there is at least a five-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a notification means sending to all configured recipients.) - The rptrInfoResetEvent trap is not sent when the + The rptrInfoResetEvent is not sent when the agent restarts and sends an SNMP coldStart or warmStart trap. However, it is recommended that a repeater agent send the rptrInfoOperStatus object as an optional object with its coldStart and warmStart trap PDUs." REFERENCE "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset notification." + +, ::= { snmpDot3RptrMgt 0 5 } -- Conformance information snmpRptrModConf OBJECT IDENTIFIER ::= { snmpRptrMod 1 } snmpRptrModCompls OBJECT IDENTIFIER ::= { snmpRptrModConf 1 } snmpRptrModObjGrps OBJECT IDENTIFIER ::= { snmpRptrModConf 2 } snmpRptrModNotGrps OBJECT IDENTIFIER ::= { snmpRptrModConf 3 } -- Object groups - snmpRptrGrpBasic OBJECT-GROUP + snmpRptrGrpBasic1516 OBJECT-GROUP OBJECTS { rptrGroupCapacity, - -, rptrOperStatus, rptrHealthText, rptrReset, rptrNonDisruptTest, rptrTotalPartitionedPorts, rptrGroupIndex, rptrGroupDescr, rptrGroupObjectID, rptrGroupOperStatus, @@ -3259,89 +3282,90 @@ rptrPortAdminStatus, rptrPortAutoPartitionState, rptrPortOperStatus } STATUS deprecated DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** Basic group from RFCs 1368 and 1516. NOTE: this object group is DEPRECATED and replaced - with snmpRptrGrpBasicRS." + with snmpRptrGrpBasic." + +, ::= { snmpRptrModObjGrps 1 } - snmpRptrGrpMonitor OBJECT-GROUP + snmpRptrGrpMonitor1516 OBJECT-GROUP OBJECTS { rptrMonitorTransmitCollisions, rptrMonitorGroupIndex, rptrMonitorGroupTotalFrames, rptrMonitorGroupTotalOctets, rptrMonitorGroupTotalErrors, rptrMonitorPortGroupIndex, rptrMonitorPortIndex, rptrMonitorPortReadableFrames, rptrMonitorPortReadableOctets, rptrMonitorPortFCSErrors, rptrMonitorPortAlignmentErrors, rptrMonitorPortFrameTooLongs, rptrMonitorPortShortEvents, rptrMonitorPortRunts, - -, rptrMonitorPortCollisions, rptrMonitorPortLateEvents, rptrMonitorPortVeryLongEvents, rptrMonitorPortDataRateMismatches, rptrMonitorPortAutoPartitions, rptrMonitorPortTotalErrors } STATUS deprecated DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** Monitor group from RFCs 1368 and 1516. NOTE: this object group is DEPRECATED and replaced - with snmpRptrGrpMonitorRS." + with snmpRptrGrpMonitor." ::= { snmpRptrModObjGrps 2 } - snmpRptrGrpAddrTrack OBJECT-GROUP + snmpRptrGrpAddrTrack1368 OBJECT-GROUP OBJECTS { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex, rptrAddrTrackLastSourceAddress, rptrAddrTrackSourceAddrChanges } STATUS obsolete DESCRIPTION "Address tracking group from RFC 1368. NOTE: this object group is OBSOLETE and replaced - with snmpRptrGrpAddrTrackNewSrcAddr." + +, + with snmpRptrGrpAddrTrack1516." ::= { snmpRptrModObjGrps 3 } - snmpRptrGrpAddrTrackNewSrcAddr OBJECT-GROUP + snmpRptrGrpAddrTrack1516 OBJECT-GROUP OBJECTS { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex, rptrAddrTrackLastSourceAddress, rptrAddrTrackSourceAddrChanges, rptrAddrTrackNewLastSrcAddress } STATUS deprecated DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** Address tracking group from RFC 1516. NOTE: this object group is DEPRECATED and - replaced with snmpRptrGrpAddrTrackRS." + replaced with snmpRptrGrpAddrTrack." ::= { snmpRptrModObjGrps 4 } -, - snmpRptrGrpBasicRS OBJECT-GROUP + snmpRptrGrpBasic OBJECT-GROUP OBJECTS { rptrGroupIndex, rptrGroupObjectID, rptrGroupOperStatus, rptrGroupPortCapacity, rptrPortGroupIndex, rptrPortIndex, rptrPortAdminStatus, rptrPortAutoPartitionState, rptrPortOperStatus, @@ -3349,239 +3373,217 @@ rptrInfoId, rptrInfoRptrType, rptrInfoOperStatus, rptrInfoReset, rptrInfoPartitionedPorts, rptrInfoLastChange } STATUS current DESCRIPTION "Basic group for a system with one or more - repeater-units in restart version of the MIB - module." + repeater-units in multi-segment (post-RFC 1516) + version of the MIB module." ::= { snmpRptrModObjGrps 5 } - snmpRptrGrpMonitorRS OBJECT-GROUP +, + snmpRptrGrpMonitor OBJECT-GROUP OBJECTS { rptrMonitorPortGroupIndex, rptrMonitorPortIndex, rptrMonitorPortReadableFrames, rptrMonitorPortReadableOctets, rptrMonitorPortFCSErrors, rptrMonitorPortAlignmentErrors, rptrMonitorPortFrameTooLongs, rptrMonitorPortShortEvents, rptrMonitorPortRunts, rptrMonitorPortCollisions, rptrMonitorPortLateEvents, rptrMonitorPortVeryLongEvents, rptrMonitorPortDataRateMismatches, rptrMonitorPortAutoPartitions, rptrMonitorPortTotalErrors, rptrMonitorPortLastChange, rptrMonTxCollisions, - -, rptrMonTotalFrames, rptrMonTotalErrors, rptrMonTotalOctets } STATUS current DESCRIPTION "Monitor group for a system with one or more - repeater-units in restart version of the MIB - module." + repeater-units in multi-segment (post-RFC 1516) + version of the MIB module." ::= { snmpRptrModObjGrps 6 } snmpRptrGrpMonitor100 OBJECT-GROUP OBJECTS { rptrMonitorPortIsolates, rptrMonitorPortSymbolErrors, rptrMonitorPortUpper32Octets, rptrMonUpper32TotalOctets } STATUS current DESCRIPTION "Monitor group for 100Mb/s ports and repeaters in a system with one or more repeater-units in - restart version of the MIB module. Systems which - support Counter64 should also implement - snmpRptrGrpMonitor100w64." + multi-segment (post-RFC 1516) version of the MIB + module. Systems which support Counter64 should + also implement snmpRptrGrpMonitor100w64." ::= { snmpRptrModObjGrps 7 } snmpRptrGrpMonitor100w64 OBJECT-GROUP + +, OBJECTS { rptrMonitorPortHCReadableOctets, rptrMonHCTotalOctets } STATUS current DESCRIPTION "Monitor group for 100Mb/s ports and repeaters in a system with one or more repeater-units and support for Counter64." ::= { snmpRptrModObjGrps 8 } - snmpRptrGrpAddrTrackRS OBJECT-GROUP + snmpRptrGrpAddrTrack OBJECT-GROUP OBJECTS { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex, rptrAddrTrackSourceAddrChanges, rptrAddrTrackNewLastSrcAddress, rptrAddrTrackCapacity } STATUS current DESCRIPTION - "Passive address tracking group for restart + "Passive address tracking group for post-RFC 1516 version of the MIB module." - -, ::= { snmpRptrModObjGrps 9 } snmpRptrGrpExtAddrTrack OBJECT-GROUP OBJECTS { rptrExtAddrTrackMacIndex, - rptrExtAddrTrackSourceAddress, - rptrAddrTrackReset } + rptrExtAddrTrackSourceAddress } STATUS current DESCRIPTION "Extended passive address tracking group for a system with one or more repeater-units in - restart version of the MIB module." + post-RFC 1516 version of the MIB module." ::= { snmpRptrModObjGrps 10 } snmpRptrGrpRptrAddrSearch OBJECT-GROUP OBJECTS { rptrAddrSearchLock, rptrAddrSearchStatus, rptrAddrSearchAddress, rptrAddrSearchState, rptrAddrSearchGroup, rptrAddrSearchPort, rptrAddrSearchOwner } STATUS current DESCRIPTION "Active MAC address search group and topology mapping support for repeaters." ::= { snmpRptrModObjGrps 11 } +, snmpRptrGrpTopNPort OBJECT-GROUP OBJECTS { rptrTopNPortControlIndex, rptrTopNPortRepeaterId, rptrTopNPortRateBase, rptrTopNPortTimeRemaining, rptrTopNPortDuration, rptrTopNPortRequestedSize, rptrTopNPortGrantedSize, rptrTopNPortStartTime, rptrTopNPortOwner, rptrTopNPortRowStatus, rptrTopNPortIndex, rptrTopNPortGroupIndex, rptrTopNPortPortIndex, rptrTopNPortRate } STATUS current DESCRIPTION "Top `N' group for repeater ports." - -, ::= { snmpRptrModObjGrps 12 } -- Compliances snmpRptrModComplRFC1368 MODULE-COMPLIANCE STATUS obsolete DESCRIPTION "Compliance for RFC 1368. NOTE: this module compliance is OBSOLETE and replaced by snmpRptrModComplRFC1516." MODULE -- this module - MANDATORY-GROUPS { snmpRptrGrpBasic } + MANDATORY-GROUPS { snmpRptrGrpBasic1516 } - GROUP snmpRptrGrpMonitor + GROUP snmpRptrGrpMonitor1516 DESCRIPTION "Implementation of this optional group is recommended for systems which have the instrumentation to do performance monitoring." - GROUP snmpRptrGrpAddrTrack + GROUP snmpRptrGrpAddrTrack1368 DESCRIPTION "Implementation of this group is recommended for systems which have the necessary instrumentation." +, ::= { snmpRptrModCompls 1 } snmpRptrModComplRFC1516 MODULE-COMPLIANCE STATUS deprecated DESCRIPTION "********* THIS COMPLIANCE IS DEPRECATED ********** Compliance for RFC 1516 and for backwards compatibility with single-repeater, 10Mb/s-only implementations." MODULE -- this module - MANDATORY-GROUPS { snmpRptrGrpBasic } + MANDATORY-GROUPS { snmpRptrGrpBasic1516 } - GROUP snmpRptrGrpMonitor + GROUP snmpRptrGrpMonitor1516 DESCRIPTION "Implementation of this optional group is - -, recommended for systems which have the instrumentation to do performance monitoring." - GROUP snmpRptrGrpAddrTrackNewSrcAddr + GROUP snmpRptrGrpAddrTrack1516 DESCRIPTION "Implementation of this group is recommended for systems which have the necessary instrumentation." ::= { snmpRptrModCompls 2 } - snmpRptrModComplRS MODULE-COMPLIANCE + snmpRptrModCompl MODULE-COMPLIANCE STATUS current DESCRIPTION - "Compliance for the `restart version' of the + "Compliance for the multi-segment version of the MIB module for a system with one or more repeater-units." MODULE -- this module - MANDATORY-GROUPS { snmpRptrGrpBasicRS } - - GROUP snmpRptrGrpMonitorRS - DESCRIPTION - "Implementation of this optional group is - recommended for systems which have the - instrumentation to do performance monitoring." + MANDATORY-GROUPS { snmpRptrGrpBasic, + snmpRptrGrpMonitor, + snmpRptrGrpAddrTrack } GROUP snmpRptrGrpMonitor100 DESCRIPTION - "Implementation of this optional group - is recommended for systems which contain - 100Mb/s repeaters and have the - instrumentation to do performance - monitoring." - - GROUP snmpRptrGrpMonitor100w64 - DESCRIPTION - "Implementation of this optional group - is recommended for systems which - contain 100Mb/s repeaters, have the - instrumentation to do performance - monitoring, and can support Counter64. - Implementation of snmpRptrGrpMonitor100 - is a pre-requisite for implementation of - this group." + "Implementation of this group is + mandatory for managed systems which + contain 100Mb/s repeaters." , - GROUP snmpRptrGrpAddrTrackRS + GROUP snmpRptrGrpMonitor100w64 DESCRIPTION "Implementation of this group is - recommended for systems which have - the necessary instrumentation to - track MAC address of a single DTE - attached to a repeater port." + mandatory for managed systems which + contain 100Mb/s repeaters and which + can support Counter64." GROUP snmpRptrGrpExtAddrTrack DESCRIPTION "Implementation of this group is recommended for systems which have the necessary instrumentation to track MAC addresses of multiple DTEs attached to a single repeater port." GROUP snmpRptrGrpRptrAddrSearch @@ -3822,124 +3824,133 @@ This document was produced by the IETF Hub MIB Working Group, whose efforts were greatly advanced by the contributions of the following people: Chuck Black John Flick Jeff Johnson Leon Leong Mike Lui - Keith McCloghrie - Donna McMaster Dave Perkins Geoff Thompson Maurice Turcotte Paul Woodruff - This document is based on an earlier version of the same name, - published as RFC 1516, and produced by the same working group - under the chairmanship of Donna McMaster and the editorship of - Keith McCloghrie. - , 6. References [1] IEEE 802.3/ISO 8802-3 Information processing systems - Local area networks - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications, 1993. [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium Attachment Units and Repeater for 100 Mb/s Operation, Type 100BASE-T," Sections 21 through 29, Supplement to IEEE Std 802.3, October 26, 1995. [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, Supplement to IEEE Std 802.3, October 26, 1995. - [4] Romascanu, D., and K. de Graaf, "Definitions of Managed - Objects for IEEE 802.3 Medium Attachment Units (MAUs)", - Internet Draft, February 1996. + [4] de Graaf, K., D. Romascanu, D. McMaster, K. McCloghrie, + and S. Roberts, "Definitions of Managed Objects for IEEE + 802.3 Medium Attachment Units (MAUs)", Internet Draft, + August 1996. [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. - [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., + [6] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996. - [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., + [7] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, and S. Waldbusser, "Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996. - [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., + [8] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, and S. Waldbusser, "Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996. - [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., + [9] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, and S. Waldbusser, "Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. , - [10] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple + [10] Case, J., M. Fedor, M. Schoffstall, and J. Davin, "Simple Network Management Protocol", RFC 1157, SNMP Research, Performance Systems International, MIT Laboratory for Computer Science, May 1990. - [11] McMaster, D., K. McCloghrie, "Definitions of Managed + [11] McMaster, D., and K. McCloghrie, "Definitions of Managed Objects for IEEE 802.3 Repeater Devices", RFC 1516, September 1993. - [12] McAnally, G., D. Gilbert, J. Flick, "Conditional Grant of - Rights to Specific Hewlett-Packard Patents In Conjunction - With the Internet Engineering Task Force's Internet- - Standard Network Management Framework", Internet Draft, - May 1996. + [12] McAnally, G., D. Gilbert, and J. Flick, "Conditional + Grant of Rights to Specific Hewlett-Packard Patents In + Conjunction With the Internet Engineering Task Force's + Internet-Standard Network Management Framework", Internet + Draft, May 1996. [13] Hewlett-Packard Company, US Patents 5,293,635 and 5,421,024. + [14] McCloghrie, K., and F. Kastenholz, "Evolution of the + Interfaces Group of MIB-II", RFC 1573, January 1994. + , 7. Security Considerations Security issues are not discussed in this memo. 8. Authors' Addresses + Kathryn de Graaf + 3Com Corporation + 118 Turnpike Rd. + Southborough, MA 01772 USA + Tel: (508)229-1627 + Fax: (508)490-5882 + E-mail: kdegraaf@isd.3com.com + Dan Romascanu Madge Networks (Israel) Ltd. Atidim Technology Park, Bldg. 3 Tel Aviv 61131, Israel Tel: 972-3-6458414, 6458458 Fax: 972-3-6487146 E-mail: dromasca@madge.com - Kathryn de Graaf - 3Com Corporation - 118 Turnpike Rd. - Southborough, MA 01772 USA - Tel: (508)229-1627 - Fax: (508)490-5882 - E-mail: kdegraaf@isd.3com.com + Donna McMaster + Coloma Communications + Tel: (916) 642-2402 + E-Mail: donna@coloma.com + + Keith McCloghrie + Cisco Systems Inc. + 170 West Tasman Drive + San Jose, CA 95134 + Tel: (408) 526-5260 + E-Mail: kzm@cisco.com , Table of Contents 1 The SNMP Network Management Framework ................. 2 - 1.1 Object Definitions .................................. 2 + 1.1 Object Definitions .................................. 3 2 Overview .............................................. 4 2.1 Relationship to RFC 1516 ............................ 4 2.2 Repeater Management ................................. 4 2.3 Structure of the MIB ................................ 5 2.3.1 Basic Definitions ................................. 5 2.3.2 Monitor Definitions ............................... 5 2.3.3 Address Tracking Definitions ...................... 5 2.3.4 Top N Definitions ................................. 6 2.4 Relationship to Other MIBs .......................... 6 2.4.1 Relationship to MIB-II ............................ 6