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

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/