draft-ietf-hubmib-repeater-dev-03.txt   rfc2108.txt 
Internet Draft 802.3 Repeater MIB 14 September 1996 Network Working Group K. de Graaf
Request for Comments: 2108 3Com Corporation
Definitions of Managed Objects Obsoletes: 1516 D. Romascanu
for IEEE 802.3 Repeater Devices Category: Standards Track Madge Networks (Israel) Ltd.
D. McMaster
14 September 1996 Coloma Communications
K. McCloghrie
<draft-ietf-hubmib-repeater-dev-03.txt> Cisco Systems Inc.
February 1997
Kathryn de Graaf
3Com Corporation
Dan Romascanu
Madge Networks (Israel) Ltd.
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.
This memo does not specify a standard for the Internet
community.
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
This MIB is intended as a superset of that defined by RFC 1516
[11], which will go to historic status. This MIB includes all
of the objects contained in that MIB, plus several new ones
which provide for significant additional capabilities.
Implementors are encouraged to support all applicable
conformance groups in order to make the best use of the new
functionality provided by this MIB. The new objects provide
support for:
o multiple repeaters
o 100BASE-T management
o port TopN capability
o address search and topology mapping
Certain objects have been deprecated; in particular, those
scalar objects used for managing a single repeater are now of
minimal use since they are duplicated in the new multiple-
repeater definitions. Additional objects have been deprecated
based on implementation experience with RFC 1516.
2.2. Repeater Management
Instances of the object types defined in this memo represent
attributes of an IEEE 802.3 (Ethernet-like) repeater, as
defined by Section 9, "Repeater Unit for 10 Mb/s Baseband
Networks" in the IEEE 802.3/ISO 8802-3 CSMA/CD standard [1],
and Section 27, "Repeater for 100 Mb/s Baseband Networks" in
the IEEE Standard 802.3u-1995 [2].
These Repeater MIB objects may be used to manage non-standard
repeater-like devices, but defining objects to describe
implementation-specific properties of non-standard repeater-
like devices is outside the scope of this memo.
The definitions presented here are based on Section 30.4,
"Layer Management for 10 and 100 Mb/s Baseband Repeaters" and
Annex 30A, "GDMO Specificataions for 802.3 managed objects" of
,
[3].
Implementors of these MIB objects should note that [3]
explicitly describes when, where, and how various repeater
attributes are measured. The IEEE document also describes the
effects of repeater actions that may be invoked by
manipulating instances of the MIB objects defined here.
The counters in this document are defined to be the same as
those counters in [3], with the intention that the same
instrumentation can be used to implement both the IEEE and
IETF management standards.
2.3. Structure of the MIB
Objects in this MIB are arranged into packages, each of which
contains a set of related objects within a broad functional
category. Objects within a package are generally defined
under the same OID subtree. These packages are intended for
organizational convenience ONLY, and have no relation to the
conformance groups defined later in the document.
2.3.1. Basic Definitions
The basic definitions include objects which are applicable to
all repeaters: status, parameter and control objects for each
repeater within the managed system, for the port groups within
the system, and for the individual ports themselves.
2.3.2. Monitor Definitions
The monitor definitions include monitoring statistics for each
repeater within the system and for individual ports.
2.3.3. Address Tracking Definitions
This collection includes objects for tracking the MAC
addresses of the DTEs attached to the ports within the system
and for mapping the topology of a network.
,
Note: These definitions are based on a technology which has
been patented by Hewlett-Packard Company. HP has granted
rights to this technology to implementors of this MIB. See
[12] and [13] for details.
2.3.4. Top N Definitions
These objects may be used for tracking the ports with the most
activity within the system or within particular repeaters.
2.4. Relationship to Other MIBs
2.4.1. Relationship to MIB-II
It is assumed that a repeater implementing this MIB will also
implement (at least) the 'system' group defined in MIB-II [5].
2.4.1.1. Relationship to the 'system' group
In MIB-II, the 'system' group is defined as being mandatory
for all systems such that each managed entity contains one
instance of each object in the 'system' group. Thus, those
objects apply to the entity even if the entity's sole
functionality is management of repeaters.
2.4.1.2. Relationship to the 'interfaces' group
In MIB-II, the 'interfaces' group is defined as being
mandatory for all systems and contains information on an
entity's interfaces, where each interface is thought of as
being attached to a 'subnetwork'. (Note that this term is not
to be confused with 'subnet' which refers to an addressing
partitioning scheme used in the Internet suite of protocols.)
This Repeater MIB uses the notion of ports on a repeater. The
concept of a MIB-II interface has NO specific relationship to
a repeater's port. Therefore, the 'interfaces' group applies
only to the one (or more) network interfaces on which the
entity managing the repeater sends and receives management
protocol operations, and does not apply to the repeater's
ports.
,
This is consistent with the physical-layer nature of a
repeater. A repeater is a bitwise store-and-forward device.
It recognizes activity and bits, but does not process incoming
data based on any packet-related information (such as checksum
or addresses). A repeater has no MAC address, no MAC
implementation, and does not pass packets up to higher-level
protocol entities for processing.
(When a network management entity is observing a repeater, it
may appear as though the repeater is passing packets to a
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
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
OwnerString
FROM IF-MIB;
snmpRptrMod MODULE-IDENTITY
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
E-mail: dromasca@madge.com
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,'
Supplement to ANSI/IEEE 802.3.
The following terms are used throughout this
MIB module. For complete formal definitions,
the IEEE 802.3 standards should be consulted
wherever possible:
System - A managed entity compliant with this
MIB, and incorporating at least one managed
802.3 repeater.
Chassis - An enclosure for one managed repeater,
part of a managed repeater, or several managed
repeaters. It typically contains an integral
power supply and a variable number of available
module slots.
Repeater-unit - The portion of the repeater set
that is inboard of the physical media interfaces.
The physical media interfaces (MAUs, AUIs) may be
physically separated from the repeater-unit, or
they may be integrated into the same physical
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.
, Definitions of Managed Objects
System interconnect segment - An internal for IEEE 802.3 Repeater Devices
segment allowing interconnection of ports using SMIv2
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 Status of this Memo
managed repeaters, in which modularity is
achieved by interconnecting a number of
different chassis.
Module - A building block in a modular This document specifies an Internet standards track protocol for the
chassis. It typically maps into one 'slot'; Internet community, and requests discussion and suggestions for
however, the range of configurations may be improvements. Please refer to the current edition of the "Internet
very large, with several modules entering Official Protocol Standards" (STD 1) for the standardization state
one slot, or one module covering several and status of this protocol. Distribution of this memo is unlimited.
slots.
"
REVISION "9309010000Z"
DESCRIPTION
"Published as RFC 1516"
REVISION "9210010000Z"
DESCRIPTION
"Published as RFC 1368"
::= { snmpDot3RptrMgt 5 }
snmpDot3RptrMgt OBJECT IDENTIFIER ::= { mib-2 22 } Abstract
OptMacAddr ::= TEXTUAL-CONVENTION This memo defines a portion of the Management Information Base (MIB)
DISPLAY-HINT "1x:" for use with network management protocols in the Internet community.
STATUS current In particular, it defines objects for managing IEEE 802.3 10 and 100
DESCRIPTION Mb/second baseband repeaters based on IEEE Std 802.3 Section 30, "10
"Either a 6 octet address in the `canonical' & 100 Mb/s Management," October 26, 1995.
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."
, Table of Contents
SYNTAX OCTET STRING (SIZE (0 | 6)) 1. The SNMP Network Management Framework.................... 2
1.1. Object Definitions..................................... 2
2. Overview................................................. 2
2.1. Relationship to RFC 1516............................... 2
2.2. Repeater Management.................................... 3
2.3. Structure of the MIB................................... 4
2.3.1. Basic Definitions.................................... 4
2.3.2. Monitor Definitions.................................. 4
2.3.3. Address Tracking Definitions......................... 4
2.3.4. Top N Definitions.................................... 4
2.4. Relationship to Other MIBs............................. 4
2.4.1. Relationship to MIB-II............................... 4
2.4.1.1. Relationship to the 'system' group................. 5
2.4.1.2. Relationship to the 'interfaces' group............. 5
3. Definitions............................................... 6
4. Topology Mapping......................................... 75
5. Acknowledgements......................................... 79
6. References............................................... 80
7. Security Considerations.................................. 81
8. Authors' Addresses....................................... 81
-- Basic information at the repeater, group, and port level. 1. The SNMP Network Management Framework
rptrBasicPackage The SNMP Network Management Framework presently consists of three
OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 1 } major components. They are:
rptrRptrInfo
OBJECT IDENTIFIER ::= { rptrBasicPackage 1 }
rptrGroupInfo
OBJECT IDENTIFIER ::= { rptrBasicPackage 2 }
rptrPortInfo
OBJECT IDENTIFIER ::= { rptrBasicPackage 3 }
rptrAllRptrInfo
OBJECT IDENTIFIER ::= { rptrBasicPackage 4 }
-- Monitoring information at the repeater, group, and port level. o the SMI, described in RFC 1902 [6] - the mechanisms used
rptrMonitorPackage for describing and naming objects for the purpose of
OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 2 } management.
rptrMonitorRptrInfo
OBJECT IDENTIFIER ::= { rptrMonitorPackage 1 }
rptrMonitorGroupInfo
OBJECT IDENTIFIER ::= { rptrMonitorPackage 2 }
rptrMonitorPortInfo
OBJECT IDENTIFIER ::= { rptrMonitorPackage 3 }
rptrMonitorAllRptrInfo
OBJECT IDENTIFIER ::= { rptrMonitorPackage 4 }
-- Address tracking information at the repeater, group, o the MIB-II, STD 17, RFC 1213 [5] - the core set of
-- and port level. managed objects for the Internet suite of protocols.
rptrAddrTrackPackage
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. o the protocol, STD 15, RFC 1157 [10] and/or RFC 1905
rptrTopNPackage [9] - the protocol used for accessing managed information.
OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 4 }
rptrTopNRptrInfo
, Textual conventions are defined in RFC 1903 [7], and conformance
-- this subtree is currently unused statements are defined in RFC 1904 [8].
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. The Framework permits new objects to be defined for the purpose of
-- experimentation and evaluation.
-- In a system containing a single managed repeater,
-- configuration, status, and control objects for the overall
-- repeater.
--
-- The objects contained under the rptrRptrInfo subtree are
-- intended for backwards compatibility with implementations of
-- RFC 1516 [11]. In newer implementations (both single- and
-- multiple-repeater implementations) the rptrInfoTable should
-- be implemented. It is the preferred source of this information,
-- as it contains the values for all repeaters managed by the
-- agent. In all cases, the objects in the rptrRptrInfo subtree
-- are duplicates of the corresponding objects in the first entry
-- of the rptrInfoTable.
rptrGroupCapacity OBJECT-TYPE 1.1. Object Definitions
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
The rptrGroupCapacity is the number of groups Managed objects are accessed via a virtual information store, termed
that can be contained within the repeater. Within the Management Information Base or MIB. Objects in the MIB are
each managed repeater, the groups are uniquely defined using the subset of Abstract Syntax Notation one (ASN.1)
numbered in the range from 1 to rptrGroupCapacity. 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.
Some groups may not be present in the repeater, in 2. Overview
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 2.1. Relationship to RFC 1516
number of field-replaceable units (i.e., modules,
, This MIB is intended as a superset of that defined by RFC 1516 [11],
cards, or boards) that can fit in the physical which will go to historic status. This MIB includes all of the
repeater enclosure, and the group numbers will objects contained in that MIB, plus several new ones which provide
correspond to numbers marked on the physical for significant additional capabilities. Implementors are encouraged
enclosure." to support all applicable conformance groups in order to make the
REFERENCE best use of the new functionality provided by this MIB. The new
"[IEEE 802.3 Mgt], 30.4.1.1.3, objects provide support for:
aRepeaterGroupCapacity."
::= { rptrRptrInfo 1 }
rptrOperStatus OBJECT-TYPE o multiple repeaters
SYNTAX INTEGER {
other(1), -- undefined or unknown
ok(2), -- no known failures
rptrFailure(3), -- repeater-related failure
groupFailure(4), -- group-related failure
portFailure(5), -- port-related failure
generalFailure(6) -- failure, unspecified type
}
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
The rptrOperStatus object indicates the o 100BASE-T management
operational state of the repeater. The
rptrHealthText object may be consulted for more
specific information about the state of the
repeater's health.
In the case of multiple kinds of failures (e.g., o port TopN capability
repeater failure and port failure), the value of
this attribute shall reflect the highest priority
failure in the following order, listed highest
priority first:
rptrFailure(3) o address search and topology mapping
groupFailure(4)
portFailure(5)
generalFailure(6)."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
::= { rptrRptrInfo 2 }
rptrHealthText OBJECT-TYPE Certain objects have been deprecated; in particular, those scalar
SYNTAX DisplayString (SIZE (0..255)) objects used for managing a single repeater are now of minimal use
since they are duplicated in the new multiple- repeater definitions.
Additional objects have been deprecated based on implementation
experience with RFC 1516.
, 2.2. Repeater Management
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
The health text object is a text string that Instances of the object types defined in this memo represent
provides information relevant to the operational attributes of an IEEE 802.3 (Ethernet-like) repeater, as defined by
state of the repeater. Agents may use this string Section 9, "Repeater Unit for 10 Mb/s Baseband Networks" in the IEEE
to provide detailed information on current 802.3/ISO 8802-3 CSMA/CD standard [1], and Section 27, "Repeater for
failures, including how they were detected, and/or 100 Mb/s Baseband Networks" in the IEEE Standard 802.3u-1995 [2].
instructions for problem resolution. The contents
are agent-specific."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.6, aRepeaterHealthText."
::= { rptrRptrInfo 3 }
rptrReset OBJECT-TYPE These Repeater MIB objects may be used to manage non-standard
SYNTAX INTEGER { repeater-like devices, but defining objects to describe
noReset(1), implementation-specific properties of non-standard repeater- like
reset(2) devices is outside the scope of this memo.
}
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
Setting this object to reset(2) causes a The definitions presented here are based on Section 30.4, "Layer
transition to the START state of Fig 9-2 in Management for 10 and 100 Mb/s Baseband Repeaters" and Annex 30A,
section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, "GDMO Specificataions for 802.3 managed objects" of [3].
and 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. Implementors of these MIB objects should note that [3] explicitly
The agent will always return the value noReset(1) describes when, where, and how various repeater attributes are
when this object is read. measured. The IEEE document also describes the effects of repeater
actions that may be invoked by manipulating instances of the MIB
objects defined here.
After receiving a request to set this variable to The counters in this document are defined to be the same as those
reset(2), the agent is allowed to delay the reset counters in [3], with the intention that the same instrumentation can
for a short period. For example, the implementor be used to implement both the IEEE and IETF management standards.
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 2.3. Structure of the MIB
defined in this document nor does it affect the
, Objects in this MIB are arranged into packages, each of which
portAdminStatus parameters. Included in this contains a set of related objects within a broad functional category.
action is the execution of a disruptive Self-Test Objects within a package are generally defined under the same OID
with the following characteristics: a) The nature subtree. These packages are intended for organizational convenience
of the tests is not specified. b) The test resets ONLY, and have no relation to the conformance groups defined later in
the repeater but without affecting management the document.
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 2.3.1. Basic Definitions
update the repeater health information (including
rptrOperStatus and rptrHealthText), and send a
rptrHealth trap."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
::= { rptrRptrInfo 4 }
rptrNonDisruptTest OBJECT-TYPE The basic definitions include objects which are applicable to all
SYNTAX INTEGER { repeaters: status, parameter and control objects for each repeater
noSelfTest(1), within the managed system, for the port groups within the system, and
selfTest(2) for the individual ports themselves.
}
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
Setting this object to selfTest(2) causes the 2.3.2. Monitor Definitions
repeater to perform a agent-specific, non-
disruptive self-test that has the following
characteristics: a) The nature of the tests is
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 monitor definitions include monitoring statistics for each
the repeater health information (including repeater within the system and for individual ports.
rptrOperStatus and rptrHealthText) and send a
rptrHealth trap.
, 2.3.3. Address Tracking Definitions
Note that this definition allows returning an
'okay' result after doing a trivial test.
Setting this object to noSelfTest(1) has no This collection includes objects for tracking the MAC addresses of
effect. The agent will always return the value the DTEs attached to the ports within the system and for mapping the
noSelfTest(1) when this object is read." topology of a network.
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.2.2,
acExecuteNonDisruptiveSelfTest."
::= { rptrRptrInfo 5 }
rptrTotalPartitionedPorts OBJECT-TYPE Note: These definitions are based on a technology which has been
SYNTAX Gauge32 patented by Hewlett-Packard Company. HP has granted rights to this
MAX-ACCESS read-only technology to implementors of this MIB. See [12] and [13] for
STATUS deprecated details.
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
This object returns the total number of ports in 2.3.4. Top N Definitions
the repeater whose current state meets all three
of the following criteria: rptrPortOperStatus
does not have the value notPresent(3),
rptrPortAdminStatus is enabled(1), and
rptrPortAutoPartitionState is autoPartitioned(2)."
::= { rptrRptrInfo 6 }
-- Basic information at the group level. These objects may be used for tracking the ports with the most
-- activity within the system or within particular repeaters.
-- Configuration and status objects for each
-- managed group in the system, independent
-- of whether there is one or more managed
-- repeater-units in the system.
rptrGroupTable OBJECT-TYPE 2.4. Relationship to Other MIBs
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 2.4.1. Relationship to MIB-II
, It is assumed that a repeater implementing this MIB will also
SYNTAX RptrGroupEntry implement (at least) the 'system' group defined in MIB-II [5].
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 ::= 2.4.1.1. Relationship to the 'system' group
SEQUENCE {
rptrGroupIndex
Integer32,
rptrGroupDescr
DisplayString,
rptrGroupObjectID
OBJECT IDENTIFIER,
rptrGroupOperStatus
INTEGER,
rptrGroupLastOperStatusChange
TimeTicks,
rptrGroupPortCapacity
Integer32
}
rptrGroupIndex OBJECT-TYPE In MIB-II, the 'system' group is defined as being mandatory for all
SYNTAX Integer32 (1..2147483647) systems such that each managed entity contains one instance of each
MAX-ACCESS read-only object in the 'system' group. Thus, those objects apply to the
STATUS current entity even if the entity's sole functionality is management of
DESCRIPTION repeaters.
"This object identifies the group within the
system for which this entry contains
information."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.2.1.1, aGroupID."
::= { rptrGroupEntry 1 }
rptrGroupDescr OBJECT-TYPE 2.4.1.2. Relationship to the 'interfaces' group
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
A textual description of the group. This value In MIB-II, the 'interfaces' group is defined as being mandatory for
all systems and contains information on an entity's interfaces, where
each interface is thought of as being attached to a 'subnetwork'.
(Note that this term is not to be confused with 'subnet' which refers
to an addressing partitioning scheme used in the Internet suite of
protocols.)
, This Repeater MIB uses the notion of ports on a repeater. The
should include the full name and version concept of a MIB-II interface has NO specific relationship to a
identification of the group's hardware type and repeater's port. Therefore, the 'interfaces' group applies only to
indicate how the group is differentiated from the one (or more) network interfaces on which the entity managing the
other types of groups in the repeater. Plug-in repeater sends and receives management protocol operations, and does
Module, Rev A' or 'Barney Rubble 10BASE-T 4-port not apply to the repeater's ports.
SIMM socket Version 2.1' are examples of valid
group descriptions.
It is mandatory that this only contain printable This is consistent with the physical-layer nature of a repeater. A
ASCII characters." repeater is a bitwise store-and-forward device. It recognizes
::= { rptrGroupEntry 2 } activity and bits, but does not process incoming data based on any
packet-related information (such as checksum or addresses). A
repeater has no MAC address, no MAC implementation, and does not pass
packets up to higher-level protocol entities for processing.
rptrGroupObjectID OBJECT-TYPE (When a network management entity is observing a repeater, it may
SYNTAX OBJECT IDENTIFIER appear as though the repeater is passing packets to a higher-level
MAX-ACCESS read-only protocol entity. However, this is only a means of implementing
STATUS current management, and this passing of management information is not part of
DESCRIPTION the repeater functionality.)
"The vendor's authoritative identification of the
group. This value may be allocated within the SMI
enterprises subtree (1.3.6.1.4.1) and provides a
straight-forward and unambiguous means for
determining what kind of group is being managed.
For example, this object could take the value 3. Definitions
1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones,
Inc.' was assigned the subtree 1.3.6.1.4.1.4242,
and had assigned the identifier
1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone
6-Port FOIRL Plug-in Module.'"
::= { rptrGroupEntry 3 }
rptrGroupOperStatus OBJECT-TYPE SNMP-REPEATER-MIB DEFINITIONS ::= BEGIN
SYNTAX INTEGER {
other(1),
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.
, IMPORTS
A status of notPresent(4) indicates that the group Counter32, Counter64, Integer32, Gauge32, TimeTicks,
is temporarily or permanently physically and/or OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2
logically not a part of the repeater. It is an FROM SNMPv2-SMI
implementation-specific matter as to whether the TimeStamp, DisplayString, MacAddress, TEXTUAL-CONVENTION,
agent effectively removes notPresent entries from RowStatus, TestAndIncr
the table. FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF
OwnerString
FROM IF-MIB;
A status of operational(2) indicates that the snmpRptrMod MODULE-IDENTITY
group is functioning, and a status of LAST-UPDATED "9609140000Z"
malfunctioning(3) indicates that the group is ORGANIZATION "IETF HUB MIB Working Group"
malfunctioning in some way." CONTACT-INFO
::= { rptrGroupEntry 4 } "WG E-mail: hubmib@hprnd.rose.hp.com
rptrGroupLastOperStatusChange OBJECT-TYPE Chair: Dan Romascanu
SYNTAX TimeTicks Postal: Madge Networks (Israel) Ltd.
MAX-ACCESS read-only Atidim Technology Park, Bldg. 3
STATUS deprecated Tel Aviv 61131, Israel
DESCRIPTION Tel: 972-3-6458414, 6458458
"********* THIS OBJECT IS DEPRECATED ********** Fax: 972-3-6487146
E-mail: dromasca@madge.com
An object that contains the value of sysUpTime at Editor: Kathryn de Graaf
the time when the last of the following occurred: Postal: 3Com Corporation
1) the agent cold- or warm-started; 118 Turnpike Rd.
2) the row for the group was created (such Southborough, MA 01772 USA
as when the group was added to the system); or Tel: (508)229-1627
3) the value of rptrGroupOperStatus for the Fax: (508)490-5882
group changed. E-mail: kdegraaf@isd.3com.com"
DESCRIPTION
"Management information for 802.3 repeaters.
A value of zero indicates that the group's The following references are used throughout
operational status has not changed since the agent this MIB module:
last restarted."
::= { rptrGroupEntry 5 }
rptrGroupPortCapacity OBJECT-TYPE [IEEE 802.3 Std]
SYNTAX Integer32 (1..2147483647) refers to IEEE 802.3/ISO 8802-3 Information
MAX-ACCESS read-only processing systems - Local area networks -
STATUS current Part 3: Carrier sense multiple access with
DESCRIPTION collision detection (CSMA/CD) access method
"The rptrGroupPortCapacity is the number of ports and physical layer specifications (1993).
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 [IEEE 802.3 Mgt]
refers to IEEE 802.3u-1995, '10 Mb/s &
100 Mb/s Management, Section 30,'
Supplement to ANSI/IEEE 802.3.
, The following terms are used throughout this
which case the actual number of ports present MIB module. For complete formal definitions,
will be less than the value of rptrGroupPortCapacity. the IEEE 802.3 standards should be consulted
The number of ports present in the group will never wherever possible:
be greater than the value of rptrGroupPortCapacity.
Note: In practice, this will generally be the System - A managed entity compliant with this
number of ports on a module, card, or board, and MIB, and incorporating at least one managed
the port numbers will correspond to numbers marked 802.3 repeater.
on the physical embodiment."
REFERENCE
"IEEE 802.3 Mgt, 30.4.2.1.2, aGroupPortCapacity."
::= { rptrGroupEntry 6 }
-- Basic information at the port level. Chassis - An enclosure for one managed repeater,
-- part of a managed repeater, or several managed
-- Configuration and status objects for repeaters. It typically contains an integral
-- each managed repeater port in the system, power supply and a variable number of available
-- independent of whether there is one or more module slots.
-- managed repeater-units in the system.
rptrPortTable OBJECT-TYPE Repeater-unit - The portion of the repeater set
SYNTAX SEQUENCE OF RptrPortEntry that is inboard of the physical media interfaces.
MAX-ACCESS not-accessible The physical media interfaces (MAUs, AUIs) may be
STATUS current physically separated from the repeater-unit, or
DESCRIPTION they may be integrated into the same physical
"Table of descriptive and status information about package.
the repeater ports in the system. The number of
entries is independent of the number of repeaters
in the managed system."
::= { rptrPortInfo 1 }
rptrPortEntry OBJECT-TYPE Trivial repeater-unit - An isolated port that can
SYNTAX RptrPortEntry gather statistics.
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single port."
INDEX { rptrPortGroupIndex, rptrPortIndex }
::= { rptrPortTable 1 }
RptrPortEntry ::= Group - A recommended, but optional, entity
SEQUENCE { defined by the IEEE 802.3 management standard,
rptrPortGroupIndex 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
Integer32, segment allowing interconnection of ports
rptrPortIndex belonging to different physical entities
Integer32, into the same logical manageable repeater.
rptrPortAdminStatus Examples of implementation might be
INTEGER, backplane busses in modular hubs, or
rptrPortAutoPartitionState chaining cables in stacks of hubs.
INTEGER,
rptrPortOperStatus
INTEGER,
rptrPortRptrId
Integer32
}
rptrPortGroupIndex OBJECT-TYPE Stack - A scalable system that may include
SYNTAX Integer32 (1..2147483647) managed repeaters, in which modularity is
MAX-ACCESS read-only achieved by interconnecting a number of
STATUS current different chassis.
DESCRIPTION
"This object identifies the group containing the
port for which this entry contains information."
::= { rptrPortEntry 1 }
rptrPortIndex OBJECT-TYPE Module - A building block in a modular
SYNTAX Integer32 (1..2147483647) chassis. It typically maps into one 'slot';
MAX-ACCESS read-only however, the range of configurations may be
STATUS current very large, with several modules entering
DESCRIPTION one slot, or one module covering several
"This object identifies the port within the group slots.
for which this entry contains information. This "
identifies the port independently from the repeater REVISION "9309010000Z"
it may be attached to. The numbering scheme for DESCRIPTION
ports is implementation specific; however, this "Published as RFC 1516"
value can never be greater than REVISION "9210010000Z"
rptrGroupPortCapacity for the associated group." DESCRIPTION
REFERENCE "Published as RFC 1368"
"[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." ::= { snmpDot3RptrMgt 5 }
::= { rptrPortEntry 2 }
rptrPortAdminStatus OBJECT-TYPE snmpDot3RptrMgt OBJECT IDENTIFIER ::= { mib-2 22 }
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
, OptMacAddr ::= TEXTUAL-CONVENTION
DESCRIPTION DISPLAY-HINT "1x:"
"Setting this object to disabled(2) disables the STATUS current
port. A disabled port neither transmits nor DESCRIPTION
receives. Once disabled, a port must be "Either a 6 octet address in the `canonical'
explicitly enabled to restore operation. A port order defined by IEEE 802.1a, i.e., as if it
which is disabled when power is lost or when a were transmitted least significant bit first
reset is exerted shall remain disabled when normal if a value is available or a zero length string."
operation resumes. 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))
The admin status takes precedence over auto- -- Basic information at the repeater, group, and port level.
partition and functionally operates between the
auto-partition mechanism and the AUI/PMA.
Setting this object to enabled(1) enables the port rptrBasicPackage
and exerts a BEGIN on the port's auto-partition OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 1 }
state machine. rptrRptrInfo
OBJECT IDENTIFIER ::= { rptrBasicPackage 1 }
rptrGroupInfo
OBJECT IDENTIFIER ::= { rptrBasicPackage 2 }
rptrPortInfo
OBJECT IDENTIFIER ::= { rptrBasicPackage 3 }
rptrAllRptrInfo
OBJECT IDENTIFIER ::= { rptrBasicPackage 4 }
(In effect, when a port is disabled, the value of -- Monitoring information at the repeater, group, and port level.
rptrPortAutoPartitionState for that port is frozen rptrMonitorPackage
until the port is next enabled. When the port OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 2 }
becomes enabled, the rptrPortAutoPartitionState rptrMonitorRptrInfo
becomes notAutoPartitioned(1), regardless of its OBJECT IDENTIFIER ::= { rptrMonitorPackage 1 }
pre-disabling state.)" rptrMonitorGroupInfo
REFERENCE OBJECT IDENTIFIER ::= { rptrMonitorPackage 2 }
"[IEEE 802.3 Mgt], 30.4.3.1.2, aPortAdminState rptrMonitorPortInfo
and 30.4.3.2.1, acPortAdminControl." OBJECT IDENTIFIER ::= { rptrMonitorPackage 3 }
::= { rptrPortEntry 3 } rptrMonitorAllRptrInfo
OBJECT IDENTIFIER ::= { rptrMonitorPackage 4 }
rptrPortAutoPartitionState OBJECT-TYPE -- Address tracking information at the repeater, group,
SYNTAX INTEGER { -- and port level.
notAutoPartitioned(1), rptrAddrTrackPackage
autoPartitioned(2) OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 3 }
} rptrAddrTrackRptrInfo
MAX-ACCESS read-only OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 1 }
STATUS current rptrAddrTrackGroupInfo
DESCRIPTION -- this subtree is currently unused
"The autoPartitionState flag indicates whether the OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 2 }
port is currently partitioned by the repeater's rptrAddrTrackPortInfo
auto-partition protection. OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 3 }
The conditions that cause port partitioning are -- TopN information.
specified in partition state machine in Sections rptrTopNPackage
9 and 27 of [IEEE 802.3 Std]. They are not OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 4 }
differentiated here." rptrTopNRptrInfo
REFERENCE -- 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.
"[IEEE 802.3 Mgt], 30.4.3.1.3, aAutoPartitionState." --
::= { rptrPortEntry 4 } -- In a system containing a single managed repeater,
-- configuration, status, and control objects for the overall
-- repeater.
rptrPortOperStatus OBJECT-TYPE --
SYNTAX INTEGER { -- The objects contained under the rptrRptrInfo subtree are
operational(1), -- intended for backwards compatibility with implementations of
notOperational(2), -- RFC 1516 [11]. In newer implementations (both single- and
notPresent(3) -- multiple-repeater implementations) the rptrInfoTable should
} -- be implemented. It is the preferred source of this information,
MAX-ACCESS read-only -- as it contains the values for all repeaters managed by the
STATUS current -- agent. In all cases, the objects in the rptrRptrInfo subtree
DESCRIPTION -- are duplicates of the corresponding objects in the first entry
"This object indicates the port's operational -- of the rptrInfoTable.
status. The notPresent(3) status indicates the
port is physically removed (note this may or may
not be possible depending on the type of port.)
The operational(1) status indicates that the port
is enabled (see rptrPortAdminStatus) and working,
even though it might be auto-partitioned (see
rptrPortAutoPartitionState).
If this object has the value operational(1) and rptrGroupCapacity OBJECT-TYPE
rptrPortAdminStatus is set to disabled(2), it is SYNTAX Integer32 (1..2147483647)
expected that this object's value will soon change MAX-ACCESS read-only
to notOperational(2)." STATUS deprecated
::= { rptrPortEntry 5 } DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
rptrPortRptrId OBJECT-TYPE The rptrGroupCapacity is the number of groups
SYNTAX Integer32 (0..2147483647) that can be contained within the repeater. Within
MAX-ACCESS read-only each managed repeater, the groups are uniquely
STATUS current numbered in the range from 1 to rptrGroupCapacity.
DESCRIPTION
"This object identifies the repeater to
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. Some groups may not be present in the repeater, in
-- which case the actual number of groups present
-- Configuration, status, and control objects for will be less than rptrGroupCapacity. The number
of groups present will never be greater than
rptrGroupCapacity.
, Note: In practice, this will generally be the
-- each managed repeater in the system. 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 }
rptrInfoTable OBJECT-TYPE rptrOperStatus OBJECT-TYPE
SYNTAX SEQUENCE OF RptrInfoEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible other(1), -- undefined or unknown
STATUS current ok(2), -- no known failures
DESCRIPTION rptrFailure(3), -- repeater-related failure
"A table of information about each groupFailure(4), -- group-related failure
non-trivial repeater. The number of entries portFailure(5), -- port-related failure
depends on the physical configuration of the generalFailure(6) -- failure, unspecified type
managed system."
::= { rptrAllRptrInfo 1 }
rptrInfoEntry OBJECT-TYPE }
SYNTAX RptrInfoEntry MAX-ACCESS read-only
MAX-ACCESS not-accessible STATUS deprecated
STATUS current DESCRIPTION
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
"An entry in the table, containing information
about a single non-trivial repeater."
INDEX { rptrInfoId }
::= { rptrInfoTable 1 }
RptrInfoEntry ::= The rptrOperStatus object indicates the
SEQUENCE { operational state of the repeater. The
rptrInfoId rptrHealthText object may be consulted for more
Integer32, specific information about the state of the
rptrInfoRptrType repeater's health.
INTEGER,
rptrInfoOperStatus
INTEGER,
rptrInfoReset
INTEGER,
rptrInfoPartitionedPorts
Gauge32,
rptrInfoLastChange
TimeStamp
}
rptrInfoId OBJECT-TYPE In the case of multiple kinds of failures (e.g.,
SYNTAX Integer32 (1..2147483647) repeater failure and port failure), the value of
MAX-ACCESS read-only this attribute shall reflect the highest priority
STATUS current failure in the following order, listed highest
DESCRIPTION priority first:
"This object identifies the repeater for which
, rptrFailure(3)
this entry contains information." groupFailure(4)
::= { rptrInfoEntry 1 } portFailure(5)
generalFailure(6)."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
::= { rptrRptrInfo 2 }
rptrInfoRptrType OBJECT-TYPE rptrHealthText OBJECT-TYPE
SYNTAX INTEGER { SYNTAX DisplayString (SIZE (0..255))
other(1), -- undefined or unknown MAX-ACCESS read-only
tenMb(2), STATUS deprecated
onehundredMbClassI(3), DESCRIPTION
onehundredMbClassII(4) "********* THIS OBJECT IS DEPRECATED **********
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The rptrInfoRptrType returns a value that identifies
the CSMA/CD repeater type."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.2, aRepeaterType."
::= { rptrInfoEntry 2 }
rptrInfoOperStatus OBJECT-TYPE The health text object is a text string that
SYNTAX INTEGER { provides information relevant to the operational
other(1), state of the repeater. Agents may use this string
ok(2), to provide detailed information on current
failure(3) failures, including how they were detected, and/or
} instructions for problem resolution. The contents
MAX-ACCESS read-only are agent-specific."
STATUS current REFERENCE
DESCRIPTION "[IEEE 802.3 Mgt], 30.4.1.1.6, aRepeaterHealthText."
"The rptrInfoOperStatus object indicates the ::= { rptrRptrInfo 3 }
operational state of the repeater."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
::= { rptrInfoEntry 3 }
rptrInfoReset OBJECT-TYPE rptrReset OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noReset(1), noReset(1),
reset(2) 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,
, }
and to the START state of Fig 27-2 in section 27 MAX-ACCESS read-write
of that standard for a 100Mb/s repeater. STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
Setting this object to noReset(1) has no effect. Setting this object to reset(2) causes a
The agent will always return the value noReset(1) transition to the START state of Fig 9-2 in
when this object is read. section 9 [IEEE 802.3 Std] for a 10Mb/s repeater,
and the START state of Fig 27-2 in section 27
of that standard for a 100Mb/s repeater.
After receiving a request to set this variable to Setting this object to noReset(1) has no effect.
reset(2), the agent is allowed to delay the reset The agent will always return the value noReset(1)
for a short period. For example, the implementor when this object is read.
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 After receiving a request to set this variable to
defined in this document nor does it affect the reset(2), the agent is allowed to delay the reset
portAdminStatus parameters. Included in this for a short period. For example, the implementor
action is the execution of a disruptive Self-Test may choose to delay the reset long enough to allow
with the following characteristics: a) The nature the SNMP response to be transmitted. In any
of the tests is not specified. b) The test resets event, the SNMP response must be transmitted.
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 This action does not reset the management counters
update the repeater health information (including defined in this document nor does it affect the
rptrInfoOperStatus), and send a rptrInfoResetEvent portAdminStatus parameters. Included in this
notification." action is the execution of a disruptive Self-Test
REFERENCE with the following characteristics: a) The nature
"[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater." of the tests is not specified. b) The test resets
::= { rptrInfoEntry 4 } 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.
rptrInfoPartitionedPorts OBJECT-TYPE After performing this self-test, the agent will
SYNTAX Gauge32 update the repeater health information (including
MAX-ACCESS read-only rptrOperStatus and rptrHealthText), and send a
STATUS current rptrHealth trap."
DESCRIPTION REFERENCE
"This object returns the total number of ports in "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
the repeater whose current state meets all three ::= { rptrRptrInfo 4 }
of the following criteria: rptrPortOperStatus
does not have the value notPresent(3),
rptrPortAdminStatus is enabled(1), and
, rptrNonDisruptTest OBJECT-TYPE
rptrPortAutoPartitionState is autoPartitioned(2)." SYNTAX INTEGER {
::= { rptrInfoEntry 5 } noSelfTest(1),
selfTest(2)
rptrInfoLastChange OBJECT-TYPE }
SYNTAX TimeStamp MAX-ACCESS read-write
MAX-ACCESS read-only STATUS deprecated
STATUS current DESCRIPTION
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
"The value of sysUpTime when any of the following
conditions occurred:
1) agent cold- or warm-started;
2) this instance of repeater was created
(such as when a device or module was
added to the system);
3) a change in the value of rptrInfoOperStatus;
4) ports were added or removed as members of
the repeater; or
5) any of the counters associated with this
repeater had a discontinuity."
::= { rptrInfoEntry 6 }
-- Setting this object to selfTest(2) causes the
-- Old version of statistics at the repeater level. repeater to perform a agent-specific, non-
-- disruptive self-test that has the following
-- Performance monitoring statistics for the repeater characteristics: a) The nature of the tests is
-- not specified. b) The test does not change the
-- In a system containing a single managed repeater-unit, state of the repeater or management information
-- the statistics object for the repeater-unit. 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.
-- The objects contained under the rptrMonitorRptrInfo subtree are After performing this test, the agent will update
-- intended for backwards compatibility with implementations of the repeater health information (including
-- RFC 1516 [11]. In newer implementations (both single- and rptrOperStatus and rptrHealthText) and send a
-- multiple-repeater implementations), the rptrMonitorTable will rptrHealth trap.
-- be implemented. It is the preferred source of this information,
-- as it contains the values for all repeaters managed by the
-- agent. In all cases, the objects in the rptrMonitorRptrInfo
-- subtree are duplicates of the corresponding objects in the
-- first entry of the rptrMonitorTable.
rptrMonitorTransmitCollisions OBJECT-TYPE Note that this definition allows returning an
SYNTAX Counter32 'okay' result after doing a trivial test.
, Setting this object to noSelfTest(1) has no
MAX-ACCESS read-only effect. The agent will always return the value
STATUS deprecated noSelfTest(1) when this object is read."
DESCRIPTION REFERENCE
"********* THIS OBJECT IS DEPRECATED ********** "[IEEE 802.3 Mgt], 30.4.1.2.2,
acExecuteNonDisruptiveSelfTest."
::= { rptrRptrInfo 5 }
For a clause 9 (10Mb/s) repeater, this counter rptrTotalPartitionedPorts OBJECT-TYPE
is incremented every time the repeater state SYNTAX Gauge32
machine enters the TRANSMIT COLLISION state MAX-ACCESS read-only
from any state other than ONE PORT LEFT STATUS deprecated
(Ref: Fig 9-2 [IEEE 802.3 Std]). DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
For a clause 27 repeater, this counter is This object returns the total number of ports in
incremented every time the repeater core state the repeater whose current state meets all three
diagram enters the Jam state as a result of of the following criteria: rptrPortOperStatus
Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). does not have the value notPresent(3),
rptrPortAdminStatus is enabled(1), and
rptrPortAutoPartitionState is autoPartitioned(2)."
::= { rptrRptrInfo 6 }
The approximate minimum time for rollover of this -- Basic information at the group level.
counter is 16 hours in a 10Mb/s repeater and 1.6 --
hours in a 100Mb/s repeater." -- Configuration and status objects for each
REFERENCE -- managed group in the system, independent
"[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions." -- of whether there is one or more managed
::= { rptrMonitorRptrInfo 1 } -- repeater-units in the system.
-- Statistics at the group level. rptrGroupTable OBJECT-TYPE
-- SYNTAX SEQUENCE OF RptrGroupEntry
-- In a system containing a single managed repeater-unit, MAX-ACCESS not-accessible
-- the statistics objects for each group. STATUS current
DESCRIPTION
"Table of descriptive and status information about
the groups of ports."
::= { rptrGroupInfo 1 }
rptrMonitorGroupTable OBJECT-TYPE rptrGroupEntry OBJECT-TYPE
SYNTAX SEQUENCE OF RptrMonitorGroupEntry SYNTAX RptrGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS current
DESCRIPTION DESCRIPTION
"********* THIS OBJECT IS DEPRECATED ********** "An entry in the table, containing information
about a single group of ports."
INDEX { rptrGroupIndex }
::= { rptrGroupTable 1 }
Table of performance and error statistics for the RptrGroupEntry ::=
groups within the repeater. The number of entries SEQUENCE {
is the same as that in the rptrGroupTable." rptrGroupIndex
::= { rptrMonitorGroupInfo 1 } Integer32,
rptrGroupDescr
DisplayString,
rptrGroupObjectID
OBJECT IDENTIFIER,
rptrGroupOperStatus
INTEGER,
rptrGroupLastOperStatusChange
TimeTicks,
rptrGroupPortCapacity
Integer32
}
rptrMonitorGroupEntry OBJECT-TYPE rptrGroupIndex OBJECT-TYPE
SYNTAX RptrMonitorGroupEntry SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS deprecated STATUS current
DESCRIPTION
"This object identifies the group within the
system for which this entry contains
information."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.2.1.1, aGroupID."
::= { rptrGroupEntry 1 }
, rptrGroupDescr OBJECT-TYPE
DESCRIPTION SYNTAX DisplayString (SIZE (0..255))
"********* THIS OBJECT IS DEPRECATED ********** MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
An entry in the table, containing total A textual description of the group. This value
performance and error statistics for a single should include the full name and version
group. Regular retrieval of the information in identification of the group's hardware type and
this table provides a means of tracking the indicate how the group is differentiated from
performance and health of the networked devices other types of groups in the repeater. Plug-in
attached to this group's ports. Module, Rev A' or 'Barney Rubble 10BASE-T 4-port
SIMM socket Version 2.1' are examples of valid
group descriptions.
The counters in this table are redundant in the It is mandatory that this only contain printable
sense that they are the summations of information ASCII characters."
already available through other objects. However, ::= { rptrGroupEntry 2 }
these sums provide a considerable optimization of
network management traffic over the otherwise
necessary retrieval of the individual counters
included in each sum.
Note: Group-level counters are rptrGroupObjectID OBJECT-TYPE
deprecated in this MIB. It is recommended SYNTAX OBJECT IDENTIFIER
that management applications instead use MAX-ACCESS read-only
the repeater-level counters contained in STATUS current
the rptrMonTable." DESCRIPTION
INDEX { rptrMonitorGroupIndex } "The vendor's authoritative identification of the
::= { rptrMonitorGroupTable 1 } group. This value may be allocated within the SMI
enterprises subtree (1.3.6.1.4.1) and provides a
straight-forward and unambiguous means for
determining what kind of group is being managed.
RptrMonitorGroupEntry ::= For example, this object could take the value
SEQUENCE { 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones,
rptrMonitorGroupIndex Inc.' was assigned the subtree 1.3.6.1.4.1.4242,
Integer32, and had assigned the identifier
rptrMonitorGroupTotalFrames 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone
Counter32, 6-Port FOIRL Plug-in Module.'"
rptrMonitorGroupTotalOctets ::= { rptrGroupEntry 3 }
Counter32,
rptrMonitorGroupTotalErrors
Counter32
}
rptrMonitorGroupIndex OBJECT-TYPE rptrGroupOperStatus OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX INTEGER {
MAX-ACCESS read-only other(1),
STATUS deprecated operational(2),
DESCRIPTION malfunctioning(3),
"********* THIS OBJECT IS DEPRECATED ********** 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
This object identifies the group within the is temporarily or permanently physically and/or
repeater for which this entry contains logically not a part of the repeater. It is an
information." implementation-specific matter as to whether the
::= { rptrMonitorGroupEntry 1 } agent effectively removes notPresent entries from
the table.
rptrMonitorGroupTotalFrames OBJECT-TYPE A status of operational(2) indicates that the
SYNTAX Counter32 group is functioning, and a status of
MAX-ACCESS read-only malfunctioning(3) indicates that the group is
STATUS deprecated malfunctioning in some way."
DESCRIPTION ::= { rptrGroupEntry 4 }
"********* THIS OBJECT IS DEPRECATED **********
The total number of frames of valid frame length rptrGroupLastOperStatusChange OBJECT-TYPE
that have been received on the ports in this group SYNTAX TimeTicks
and for which the FCSError and CollisionEvent MAX-ACCESS read-only
signals were not asserted. This counter is the STATUS deprecated
summation of the values of the DESCRIPTION
rptrMonitorPortReadableFrames counters for all of "********* THIS OBJECT IS DEPRECATED **********
the ports in the group.
This statistic provides one of the parameters An object that contains the value of sysUpTime at
necessary for obtaining the packet error rate. the time when the last of the following occurred:
The approximate minimum time for rollover of this 1) the agent cold- or warm-started;
counter is 80 hours in a 10Mb/s repeater." 2) the row for the group was created (such
::= { rptrMonitorGroupEntry 2 } as when the group was added to the system); or
3) the value of rptrGroupOperStatus for the
group changed.
rptrMonitorGroupTotalOctets OBJECT-TYPE A value of zero indicates that the group's
SYNTAX Counter32 operational status has not changed since the agent
MAX-ACCESS read-only last restarted."
STATUS deprecated ::= { rptrGroupEntry 5 }
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
The total number of octets contained in the valid rptrGroupPortCapacity OBJECT-TYPE
frames that have been received on the ports in SYNTAX Integer32 (1..2147483647)
this group. This counter is the summation of the MAX-ACCESS read-only
values of the rptrMonitorPortReadableOctets STATUS current
counters for all of the ports in the group. 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.
This statistic provides an indicator of the total Some ports may not be present in the system, in
data transferred. The approximate minimum time which case the actual number of ports present
for rollover of this counter is 58 minutes in a will be less than the value of rptrGroupPortCapacity.
10Mb/s repeater." The number of ports present in the group will never
::= { rptrMonitorGroupEntry 3 } 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
"IEEE 802.3 Mgt, 30.4.2.1.2, aGroupPortCapacity."
::= { rptrGroupEntry 6 }
rptrMonitorGroupTotalErrors OBJECT-TYPE -- Basic information at the port level.
SYNTAX Counter32 --
MAX-ACCESS read-only -- Configuration and status objects for
STATUS deprecated -- each managed repeater port in the system,
DESCRIPTION -- independent of whether there is one or more
"********* THIS OBJECT IS DEPRECATED ********** -- managed repeater-units in the system.
The total number of errors which have occurred on rptrPortTable OBJECT-TYPE
all of the ports in this group. This counter is SYNTAX SEQUENCE OF RptrPortEntry
the summation of the values of the MAX-ACCESS not-accessible
rptrMonitorPortTotalErrors counters for all of the STATUS current
ports in the group." DESCRIPTION
::= { rptrMonitorGroupEntry 4 } "Table of descriptive and status information about
the repeater ports in the system. The number of
entries is independent of the number of repeaters
in the managed system."
::= { rptrPortInfo 1 }
-- Statistics at the port level. rptrPortEntry OBJECT-TYPE
-- SYNTAX RptrPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single port."
rptrMonitorPortTable OBJECT-TYPE INDEX { rptrPortGroupIndex, rptrPortIndex }
SYNTAX SEQUENCE OF RptrMonitorPortEntry ::= { rptrPortTable 1 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of performance and error statistics for the
ports. The number of entries is the same as that
in the rptrPortTable.
The columnar object rptrMonitorPortLastChange RptrPortEntry ::=
is used to indicate possible discontinuities SEQUENCE {
of counter type columnar objects in the table." rptrPortGroupIndex
::= { rptrMonitorPortInfo 1 } Integer32,
rptrPortIndex
Integer32,
rptrPortAdminStatus
INTEGER,
rptrPortAutoPartitionState
INTEGER,
rptrPortOperStatus
INTEGER,
rptrPortRptrId
Integer32
}
rptrMonitorPortEntry OBJECT-TYPE rptrPortGroupIndex OBJECT-TYPE
SYNTAX RptrMonitorPortEntry SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing performance and "This object identifies the group containing the
error statistics for a single port." port for which this entry contains information."
INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex } ::= { rptrPortEntry 1 }
::= { rptrMonitorPortTable 1 }
RptrMonitorPortEntry ::= rptrPortIndex OBJECT-TYPE
SEQUENCE { SYNTAX Integer32 (1..2147483647)
rptrMonitorPortGroupIndex MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the port within the group
for which this entry contains information. This
identifies the port independently from the repeater
it may be attached to. The numbering scheme for
ports is implementation specific; however, this
value can never be greater than
rptrGroupPortCapacity for the associated group."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
::= { rptrPortEntry 2 }
, rptrPortAdminStatus OBJECT-TYPE
Integer32, SYNTAX INTEGER {
rptrMonitorPortIndex enabled(1),
Integer32, disabled(2)
rptrMonitorPortReadableFrames
Counter32,
rptrMonitorPortReadableOctets
Counter32,
rptrMonitorPortFCSErrors
Counter32,
rptrMonitorPortAlignmentErrors
Counter32,
rptrMonitorPortFrameTooLongs
Counter32,
rptrMonitorPortShortEvents
Counter32,
rptrMonitorPortRunts
Counter32,
rptrMonitorPortCollisions
Counter32,
rptrMonitorPortLateEvents
Counter32,
rptrMonitorPortVeryLongEvents
Counter32,
rptrMonitorPortDataRateMismatches
Counter32,
rptrMonitorPortAutoPartitions
Counter32,
rptrMonitorPortTotalErrors
Counter32,
rptrMonitorPortLastChange
TimeStamp
}
rptrMonitorPortGroupIndex OBJECT-TYPE }
SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-write
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "Setting this object to disabled(2) disables the
"This object identifies the group containing the port. A disabled port neither transmits nor
port for which this entry contains information." receives. Once disabled, a port must be
::= { rptrMonitorPortEntry 1 } 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.
rptrMonitorPortIndex OBJECT-TYPE The admin status takes precedence over auto-
SYNTAX Integer32 (1..2147483647) partition and functionally operates between the
MAX-ACCESS read-only auto-partition mechanism and the AUI/PMA.
, Setting this object to enabled(1) enables the port
STATUS current and exerts a BEGIN on the port's auto-partition
DESCRIPTION state machine.
"This object identifies the port within the group
for which this entry contains information."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
::= { rptrMonitorPortEntry 2 }
rptrMonitorPortReadableFrames OBJECT-TYPE (In effect, when a port is disabled, the value of
SYNTAX Counter32 rptrPortAutoPartitionState for that port is frozen
MAX-ACCESS read-only until the port is next enabled. When the port
STATUS current becomes enabled, the rptrPortAutoPartitionState
DESCRIPTION becomes notAutoPartitioned(1), regardless of its
"This object is the number of frames of valid pre-disabling state.)"
frame length that have been received on this port. REFERENCE
This counter is incremented by one for each frame "[IEEE 802.3 Mgt], 30.4.3.1.2, aPortAdminState
received on this port whose OctetCount is greater and 30.4.3.2.1, acPortAdminControl."
than or equal to minFrameSize and less than or ::= { rptrPortEntry 3 }
equal to maxFrameSize (Ref: IEEE 802.3 Std,
4.4.2.1) and for which the FCSError and
CollisionEvent signals are not asserted.
A discontinuity may occur in the value rptrPortAutoPartitionState OBJECT-TYPE
when the value of object SYNTAX INTEGER {
rptrMonitorPortLastChange changes. notAutoPartitioned(1),
autoPartitioned(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The autoPartitionState flag indicates whether the
port is currently partitioned by the repeater's
auto-partition protection.
This statistic provides one of the parameters The conditions that cause port partitioning are
necessary for obtaining the packet error rate. specified in partition state machine in Sections
The approximate minimum time for rollover of this 9 and 27 of [IEEE 802.3 Std]. They are not
counter is 80 hours at 10Mb/s." differentiated here."
REFERENCE REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.4, aReadableFrames." "[IEEE 802.3 Mgt], 30.4.3.1.3, aAutoPartitionState."
::= { rptrMonitorPortEntry 3 } ::= { rptrPortEntry 4 }
rptrMonitorPortReadableOctets OBJECT-TYPE rptrPortOperStatus OBJECT-TYPE
SYNTAX Counter32 SYNTAX INTEGER {
MAX-ACCESS read-only operational(1),
STATUS current notOperational(2),
DESCRIPTION notPresent(3)
"This object is the number of octets contained in }
valid frames that have been received on this port. MAX-ACCESS read-only
This counter is incremented by OctetCount for each STATUS current
frame received on this port which has been DESCRIPTION
determined to be a readable frame (i.e., including "This object indicates the port's operational
FCS octets but excluding framing bits and dribble status. The notPresent(3) status indicates the
port is physically removed (note this may or may
not be possible depending on the type of port.)
The operational(1) status indicates that the port
is enabled (see rptrPortAdminStatus) and working,
even though it might be auto-partitioned (see
rptrPortAutoPartitionState).
, If this object has the value operational(1) and
bits). rptrPortAdminStatus is set to disabled(2), it is
expected that this object's value will soon change
to notOperational(2)."
::= { rptrPortEntry 5 }
A discontinuity may occur in the value rptrPortRptrId OBJECT-TYPE
when the value of object SYNTAX Integer32 (0..2147483647)
rptrMonitorPortLastChange changes. MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the repeater to
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 }
This statistic provides an indicator of the total -- New version of basic information at the repeater level.
data transferred. The approximate minimum time --
for rollover of this counter in a 10Mb/s repeater -- Configuration, status, and control objects for
is 58 minutes. -- each managed repeater in the system.
For ports receiving traffic at a maximum rate in rptrInfoTable OBJECT-TYPE
a 100Mb/s repeater, this counter can roll over SYNTAX SEQUENCE OF RptrInfoEntry
in less than 6 minutes. Since that amount of time MAX-ACCESS not-accessible
could be less than a management station's poll cycle STATUS current
time, in order to avoid a loss of information a DESCRIPTION
management station is advised to also poll the "A table of information about each
rptrMonitorPortUpper32Octets object, or to use the non-trivial repeater. The number of entries
64-bit counter defined by depends on the physical configuration of the
rptrMonitorPortHCReadableOctets instead of the managed system."
two 32-bit counters." ::= { rptrAllRptrInfo 1 }
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets."
::= { rptrMonitorPortEntry 4 }
rptrMonitorPortFCSErrors OBJECT-TYPE rptrInfoEntry OBJECT-TYPE
SYNTAX Counter32 SYNTAX RptrInfoEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter is incremented by one for each frame "An entry in the table, containing information
received on this port with the FCSError signal about a single non-trivial repeater."
asserted and the FramingError and CollisionEvent INDEX { rptrInfoId }
signals deasserted and whose OctetCount is greater ::= { rptrInfoTable 1 }
than or equal to minFrameSize and less than or
equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3
Std).
A discontinuity may occur in the value RptrInfoEntry ::=
when the value of object SEQUENCE {
rptrMonitorPortLastChange changes. rptrInfoId
Integer32,
rptrInfoRptrType
INTEGER,
rptrInfoOperStatus
INTEGER,
rptrInfoReset
INTEGER,
rptrInfoPartitionedPorts
Gauge32,
rptrInfoLastChange
TimeStamp
}
The approximate minimum time for rollover of this rptrInfoId OBJECT-TYPE
counter is 80 hours at 10Mb/s." SYNTAX Integer32 (1..2147483647)
REFERENCE MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the repeater for which
this entry contains information."
::= { rptrInfoEntry 1 }
, rptrInfoRptrType OBJECT-TYPE
"[IEEE 802.3 Mgt], 30.4.3.1.6, SYNTAX INTEGER {
aFrameCheckSequenceErrors." other(1), -- undefined or unknown
::= { rptrMonitorPortEntry 5 } tenMb(2),
onehundredMbClassI(3),
onehundredMbClassII(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The rptrInfoRptrType returns a value that identifies
the CSMA/CD repeater type."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.2, aRepeaterType."
::= { rptrInfoEntry 2 }
rptrMonitorPortAlignmentErrors OBJECT-TYPE rptrInfoOperStatus OBJECT-TYPE
SYNTAX Counter32 SYNTAX INTEGER {
MAX-ACCESS read-only other(1),
STATUS current ok(2),
DESCRIPTION failure(3)
"This counter is incremented by one for each frame }
received on this port with the FCSError and MAX-ACCESS read-only
FramingError signals asserted and CollisionEvent STATUS current
signal deasserted and whose OctetCount is greater DESCRIPTION
than or equal to minFrameSize and less than or "The rptrInfoOperStatus object indicates the
equal to maxFrameSize (Ref: IEEE 802.3 Std, operational state of the repeater."
4.4.2.1). If rptrMonitorPortAlignmentErrors is REFERENCE
incremented then the rptrMonitorPortFCSErrors "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
Counter shall not be incremented for the same ::= { rptrInfoEntry 3 }
frame.
A discontinuity may occur in the value rptrInfoReset OBJECT-TYPE
when the value of object SYNTAX INTEGER {
rptrMonitorPortLastChange changes. 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,
and to the START state of Fig 27-2 in section 27
of that standard for a 100Mb/s repeater.
The approximate minimum time for rollover of this Setting this object to noReset(1) has no effect.
counter is 80 hours at 10Mb/s." The agent will always return the value noReset(1)
REFERENCE when this object is read.
"[IEEE 802.3 Mgt], 30.4.3.1.7, aAlignmentErrors."
::= { rptrMonitorPortEntry 6 }
rptrMonitorPortFrameTooLongs OBJECT-TYPE After receiving a request to set this variable to
SYNTAX Counter32 reset(2), the agent is allowed to delay the reset
MAX-ACCESS read-only for a short period. For example, the implementor
STATUS current may choose to delay the reset long enough to allow
DESCRIPTION the SNMP response to be transmitted. In any
"This counter is incremented by one for each frame event, the SNMP response must be transmitted.
received on this port whose OctetCount is greater
than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std).
If rptrMonitorPortFrameTooLongs is incremented
then neither the rptrMonitorPortAlignmentErrors
nor the rptrMonitorPortFCSErrors counter shall be
incremented for the frame.
A discontinuity may occur in the value This action does not reset the management counters
when the value of object 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.
, After performing this self-test, the agent will
rptrMonitorPortLastChange changes. update the repeater health information (including
rptrInfoOperStatus), and send a rptrInfoResetEvent
notification."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
::= { rptrInfoEntry 4 }
The approximate minimum time for rollover of this rptrInfoPartitionedPorts OBJECT-TYPE
counter is 61 days in a 10Mb/s repeater." SYNTAX Gauge32
REFERENCE MAX-ACCESS read-only
"[IEEE 802.3 Mgt], 30.4.3.1.8, aFramesTooLong." STATUS current
::= { rptrMonitorPortEntry 7 } DESCRIPTION
"This object returns the total number of ports in
the repeater whose current state meets all three
of the following criteria: rptrPortOperStatus
does not have the value notPresent(3),
rptrPortAdminStatus is enabled(1), and
rptrPortAutoPartitionState is autoPartitioned(2)."
::= { rptrInfoEntry 5 }
rptrMonitorPortShortEvents OBJECT-TYPE rptrInfoLastChange OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter is incremented by one for each "The value of sysUpTime when any of the following
CarrierEvent on this port with ActivityDuration conditions occurred:
less than ShortEventMaxTime. ShortEventMaxTime is 1) agent cold- or warm-started;
greater than 74 bit times and less than 82 bit 2) this instance of repeater was created
times. ShortEventMaxTime has tolerances included (such as when a device or module was
to provide for circuit losses between a added to the system);
conformance test point at the AUI and the 3) a change in the value of rptrInfoOperStatus;
measurement point within the state machine. 4) ports were added or removed as members of
the repeater; or
5) any of the counters associated with this
repeater had a discontinuity."
::= { rptrInfoEntry 6 }
Notes: --
-- Old version of statistics at the repeater level.
--
-- Performance monitoring statistics for the repeater
--
-- In a system containing a single managed repeater-unit,
-- the statistics object for the repeater-unit.
ShortEvents may indicate externally -- The objects contained under the rptrMonitorRptrInfo subtree are
generated noise hits which will cause the repeater -- intended for backwards compatibility with implementations of
to transmit Runts to its other ports, or propagate -- RFC 1516 [11]. In newer implementations (both single- and
a collision (which may be late) back to the -- multiple-repeater implementations), the rptrMonitorTable will
transmitting DTE and damaged frames to the rest of -- be implemented. It is the preferred source of this information,
the network. -- as it contains the values for all repeaters managed by the
-- agent. In all cases, the objects in the rptrMonitorRptrInfo
-- subtree are duplicates of the corresponding objects in the
-- first entry of the rptrMonitorTable.
Implementors may wish to consider selecting the rptrMonitorTransmitCollisions OBJECT-TYPE
ShortEventMaxTime towards the lower end of the SYNTAX Counter32
allowed tolerance range to accommodate bit losses MAX-ACCESS read-only
suffered through physical channel devices not STATUS deprecated
budgeted for within this standard. DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
The significance of this attribute is different For a clause 9 (10Mb/s) repeater, this counter
in 10 and 100 Mb/s collision domains. Clause 9 is incremented every time the repeater state
repeaters perform fragment extension of short machine enters the TRANSMIT COLLISION state
events which would be counted as runts on the from any state other than ONE PORT LEFT
interconnect ports of other repeaters. Clause (Ref: Fig 9-2 [IEEE 802.3 Std]).
27 repeaters do not perform fragment extension.
A discontinuity may occur in the value For a clause 27 repeater, this counter is
incremented every time the repeater core state
diagram enters the Jam state as a result of
Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]).
, The approximate minimum time for rollover of this
when the value of object counter is 16 hours in a 10Mb/s repeater and 1.6
rptrMonitorPortLastChange changes. hours in a 100Mb/s repeater."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions."
::= { rptrMonitorRptrInfo 1 }
The approximate minimum time for rollover of this -- Statistics at the group level.
counter is 16 hours in a 10Mb/s repeater." --
REFERENCE -- In a system containing a single managed repeater-unit,
"[IEEE 802.3 Mgt], 30.4.3.1.9, aShortEvents." -- the statistics objects for each group.
::= { rptrMonitorPortEntry 8 }
rptrMonitorPortRunts OBJECT-TYPE rptrMonitorGroupTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF RptrMonitorGroupEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS deprecated
DESCRIPTION DESCRIPTION
"This counter is incremented by one for each "********* THIS OBJECT IS DEPRECATED **********
CarrierEvent on this port that meets one of the
following two conditions. Only one test need be
made. a) The ActivityDuration is greater than
ShortEventMaxTime and less than ValidPacketMinTime
and the CollisionEvent signal is deasserted. b)
The OctetCount is less than 64, the
ActivityDuration is greater than ShortEventMaxTime
and the CollisionEvent signal is deasserted.
ValidPacketMinTime is greater than or equal to 552
bit times and less than 565 bit times.
An event whose length is greater than 74 bit times Table of performance and error statistics for the
but less than 82 bit times shall increment either groups within the repeater. The number of entries
the shortEvents counter or the runts counter but is the same as that in the rptrGroupTable."
not both. A CarrierEvent greater than or equal to ::= { rptrMonitorGroupInfo 1 }
552 bit times but less than 565 bit times may or
may not be counted as a runt.
ValidPacketMinTime has tolerances included to rptrMonitorGroupEntry OBJECT-TYPE
provide for circuit losses between a conformance SYNTAX RptrMonitorGroupEntry
test point at the AUI and the measurement point MAX-ACCESS not-accessible
within the state machine. STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
Runts usually indicate collision fragments, a An entry in the table, containing total
normal network event. In certain situations performance and error statistics for a single
associated with large diameter networks a group. Regular retrieval of the information in
percentage of collision fragments may exceed this table provides a means of tracking the
ValidPacketMinTime. performance and health of the networked devices
attached to this group's ports.
A discontinuity may occur in the value The counters in this table are redundant in the
sense that they are the summations of information
already available through other objects. However,
these sums provide a considerable optimization of
network management traffic over the otherwise
necessary retrieval of the individual counters
included in each sum.
, Note: Group-level counters are
when the value of object deprecated in this MIB. It is recommended
rptrMonitorPortLastChange changes. that management applications instead use
the repeater-level counters contained in
the rptrMonTable."
INDEX { rptrMonitorGroupIndex }
::= { rptrMonitorGroupTable 1 }
The approximate minimum time for rollover of this RptrMonitorGroupEntry ::=
counter is 16 hours in a 10Mb/s repeater." SEQUENCE {
REFERENCE rptrMonitorGroupIndex
"[IEEE 802.3 Mgt], 30.4.3.1.10, aRunts." Integer32,
::= { rptrMonitorPortEntry 9 } rptrMonitorGroupTotalFrames
Counter32,
rptrMonitorGroupTotalOctets
Counter32,
rptrMonitorGroupTotalErrors
Counter32
}
rptrMonitorPortCollisions OBJECT-TYPE rptrMonitorGroupIndex OBJECT-TYPE
SYNTAX Counter32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS deprecated
DESCRIPTION DESCRIPTION
"For a clause 9 repeater, this counter is "********* THIS OBJECT IS DEPRECATED **********
incremented by one for any CarrierEvent signal
on any port for which the CollisionEvent signal
on this port is asserted. For a clause 27
repeater port the counter increments on entering
the Collision Count Increment state of the
partition state diagram (fig 27-8 of
[IEEE 802.3 Std]).
A discontinuity may occur in the value This object identifies the group within the
when the value of object repeater for which this entry contains
rptrMonitorPortLastChange changes. information."
::= { rptrMonitorGroupEntry 1 }
The approximate minimum time for rollover of this rptrMonitorGroupTotalFrames OBJECT-TYPE
counter is 16 hours in a 10Mb/s repeater." SYNTAX Counter32
REFERENCE MAX-ACCESS read-only
"[IEEE 802.3 Mgt], 30.4.3.1.11, aCollisions." STATUS deprecated
::= { rptrMonitorPortEntry 10 } DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
rptrMonitorPortLateEvents OBJECT-TYPE The total number of frames of valid frame length
SYNTAX Counter32 that have been received on the ports in this group
MAX-ACCESS read-only and for which the FCSError and CollisionEvent
STATUS current signals were not asserted. This counter is the
DESCRIPTION summation of the values of the
"For a clause 9 repeater port, this counter is rptrMonitorPortReadableFrames counters for all of
incremented by one for each CarrierEvent the ports in the group.
on this port in which the CollIn(X)
variable transitions to the value SQE (Ref:
9.6.6.2, IEEE 802.3 Std) while the
ActivityDuration is greater than the
LateEventThreshold. For a clause 27 repeater
, This statistic provides one of the parameters
port, this counter is incremented by one on necessary for obtaining the packet error rate.
entering the Collision Count Increment state
of the partition state diagram (fig 27-8)
while the ActivityDuration is greater than
the LateEvent- Threshold. Such a CarrierEvent
is counted twice, as both a collision and as a
lateEvent.
The LateEventThreshold is greater than 480 bit The approximate minimum time for rollover of this
times and less than 565 bit times. counter is 80 hours in a 10Mb/s repeater."
LateEventThreshold has tolerances included to ::= { rptrMonitorGroupEntry 2 }
permit an implementation to build a single
threshold to serve as both the LateEventThreshold
and ValidPacketMinTime threshold.
A discontinuity may occur in the value rptrMonitorGroupTotalOctets OBJECT-TYPE
when the value of object SYNTAX Counter32
rptrMonitorPortLastChange changes. MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
The approximate minimum time for rollover of this The total number of octets contained in the valid
counter is 81 hours in a 10Mb/s repeater." frames that have been received on the ports in
REFERENCE this group. This counter is the summation of the
"[IEEE 802.3 Mgt], 30.4.3.1.12, aLateEvents." values of the rptrMonitorPortReadableOctets
::= { rptrMonitorPortEntry 11 } counters for all of the ports in the group.
rptrMonitorPortVeryLongEvents OBJECT-TYPE This statistic provides an indicator of the total
SYNTAX Counter32 data transferred. The approximate minimum time
MAX-ACCESS read-only for rollover of this counter is 58 minutes in a
STATUS current 10Mb/s repeater."
DESCRIPTION ::= { rptrMonitorGroupEntry 3 }
"For a clause 9 repeater port, this counter
is incremented by one for each CarrierEvent
whose ActivityDuration is greater than the
MAU Jabber Lockup Protection timer TW3
(Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std).
For a clause 27 repeater port, this counter rptrMonitorGroupTotalErrors OBJECT-TYPE
is incremented by one on entry to the SYNTAX Counter32
Rx Jabber state of the receiver timer state MAX-ACCESS read-only
diagram (fig 27-7). Other counters may STATUS deprecated
be incremented as appropriate. DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
A discontinuity may occur in the value The total number of errors which have occurred on
when the value of object all of the ports in this group. This counter is
rptrMonitorPortLastChange changes." the summation of the values of the
rptrMonitorPortTotalErrors counters for all of the
ports in the group."
::= { rptrMonitorGroupEntry 4 }
, -- Statistics at the port level.
--
REFERENCE rptrMonitorPortTable OBJECT-TYPE
"[IEEE 802.3 Mgt], 30.4.3.1.13, aVeryLongEvents." SYNTAX SEQUENCE OF RptrMonitorPortEntry
::= { rptrMonitorPortEntry 12 } MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of performance and error statistics for the
ports. The number of entries is the same as that
in the rptrPortTable.
rptrMonitorPortDataRateMismatches OBJECT-TYPE The columnar object rptrMonitorPortLastChange
SYNTAX Counter32 is used to indicate possible discontinuities
MAX-ACCESS read-only of counter type columnar objects in the table."
STATUS current ::= { rptrMonitorPortInfo 1 }
DESCRIPTION
"This counter is incremented by one for each
frame received by this port that meets all
of the conditions required by only one of the
following two measurement methods:
Measurement method A: 1) The CollisionEvent rptrMonitorPortEntry OBJECT-TYPE
signal is not asserted (10Mb/s operation) or SYNTAX RptrMonitorPortEntry
the Collision Count Increment state of the MAX-ACCESS not-accessible
partition state diagram (fig 27-8 of STATUS current
[IEEE 802.3 Std]) has not been entered DESCRIPTION
(100Mb/s operation). 2) The ActivityDuration "An entry in the table, containing performance and
is greater than ValidPacketMinTime. 3) The error statistics for a single port."
frequency (data rate) is detectably mismatched INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
from the local transmit frequency. ::= { rptrMonitorPortTable 1 }
Measurement method B: 1) The CollisionEvent RptrMonitorPortEntry ::=
signal is not asserted (10Mb/s operation) SEQUENCE {
or the Collision Count Increment state of the rptrMonitorPortGroupIndex
partition state diagram (fig 27-8 of Integer32,
[IEEE 802.3 Std]) has not been entered rptrMonitorPortIndex
(100Mb/s operation). 2) The OctetCount is Integer32,
greater than 63. 3) The frequency (data rptrMonitorPortReadableFrames
rate) is detectably mismatched from the local Counter32,
transmit frequency. The exact degree of rptrMonitorPortReadableOctets
mismatch is vendor specific and is to be Counter32,
defined by the vendor for conformance testing. rptrMonitorPortFCSErrors
Counter32,
rptrMonitorPortAlignmentErrors
Counter32,
rptrMonitorPortFrameTooLongs
Counter32,
rptrMonitorPortShortEvents
Counter32,
rptrMonitorPortRunts
Counter32,
rptrMonitorPortCollisions
Counter32,
rptrMonitorPortLateEvents
Counter32,
rptrMonitorPortVeryLongEvents
Counter32,
rptrMonitorPortDataRateMismatches
Counter32,
rptrMonitorPortAutoPartitions
Counter32,
rptrMonitorPortTotalErrors
Counter32,
rptrMonitorPortLastChange
TimeStamp
}
When this event occurs, other counters whose rptrMonitorPortGroupIndex OBJECT-TYPE
increment conditions were satisfied may or may not SYNTAX Integer32 (1..2147483647)
also be incremented, at the implementor's MAX-ACCESS read-only
discretion. Whether or not the repeater was able STATUS current
to maintain data integrity is beyond the scope of DESCRIPTION
this standard. "This object identifies the group containing the
port for which this entry contains information."
::= { rptrMonitorPortEntry 1 }
A discontinuity may occur in the value rptrMonitorPortIndex OBJECT-TYPE
when the value of object SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the port within the group
for which this entry contains information."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
::= { rptrMonitorPortEntry 2 }
, rptrMonitorPortReadableFrames OBJECT-TYPE
rptrMonitorPortLastChange changes." SYNTAX Counter32
REFERENCE MAX-ACCESS read-only
"[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches." STATUS current
::= { rptrMonitorPortEntry 13 } DESCRIPTION
"This object is the number of frames of valid
frame length that have been received on this port.
This counter is incremented by one for each frame
received on this port whose OctetCount is greater
than or equal to minFrameSize and less than or
equal to maxFrameSize (Ref: IEEE 802.3 Std,
4.4.2.1) and for which the FCSError and
CollisionEvent signals are not asserted.
rptrMonitorPortAutoPartitions OBJECT-TYPE A discontinuity may occur in the value
SYNTAX Counter32 when the value of object
MAX-ACCESS read-only rptrMonitorPortLastChange changes.
STATUS current
DESCRIPTION
"This counter is incremented by one for
each time the repeater has automatically
partitioned this port.
The conditions that cause a clause 9 This statistic provides one of the parameters
repeater port to partition are specified in necessary for obtaining the packet error rate.
the partition state diagram in clause 9 of The approximate minimum time for rollover of this
[IEEE 802.3 Std]. They are not differentiated counter is 80 hours at 10Mb/s."
here. A clause 27 repeater port partitions REFERENCE
on entry to the Partition Wait state of the "[IEEE 802.3 Mgt], 30.4.3.1.4, aReadableFrames."
partition state diagram (fig 27-8 in ::= { rptrMonitorPortEntry 3 }
[IEEE 802.3 Std]).
A discontinuity may occur in the value rptrMonitorPortReadableOctets OBJECT-TYPE
when the value of object SYNTAX Counter32
rptrMonitorPortLastChange changes." MAX-ACCESS read-only
REFERENCE STATUS current
"[IEEE 802.3 Mgt], 30.4.3.1.15, aAutoPartitions." DESCRIPTION
::= { rptrMonitorPortEntry 14 } "This object is the number of octets contained in
valid frames that have been received on this port.
This counter is incremented by OctetCount for each
frame received on this port which has been
determined to be a readable frame (i.e., including
FCS octets but excluding framing bits and dribble
bits).
rptrMonitorPortTotalErrors OBJECT-TYPE A discontinuity may occur in the value
SYNTAX Counter32 when the value of object
MAX-ACCESS read-only rptrMonitorPortLastChange changes.
STATUS current
DESCRIPTION
"The total number of errors which have occurred on
this port. This counter is the summation of the
values of other error counters (for the same
port), namely:
rptrMonitorPortFCSErrors, This statistic provides an indicator of the total
rptrMonitorPortAlignmentErrors, data transferred. The approximate minimum time
rptrMonitorPortFrameTooLongs, for rollover of this counter in a 10Mb/s repeater
rptrMonitorPortShortEvents, is 58 minutes.
rptrMonitorPortLateEvents,
, For ports receiving traffic at a maximum rate in
rptrMonitorPortVeryLongEvents, a 100Mb/s repeater, this counter can roll over
rptrMonitorPortDataRateMismatches, and in less than 6 minutes. Since that amount of time
rptrMonitorPortSymbolErrors. could be less than a management station's poll cycle
time, in order to avoid a loss of information a
management station is advised to also poll the
rptrMonitorPortUpper32Octets object, or to use the
64-bit counter defined by
rptrMonitorPortHCReadableOctets instead of the
two 32-bit counters."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets."
::= { rptrMonitorPortEntry 4 }
This counter is redundant in the sense that it is rptrMonitorPortFCSErrors OBJECT-TYPE
the summation of information already available SYNTAX Counter32
through other objects. However, it is included MAX-ACCESS read-only
specifically because the regular retrieval of this STATUS current
object as a means of tracking the health of a port DESCRIPTION
provides a considerable optimization of network "This counter is incremented by one for each frame
management traffic over the otherwise necessary received on this port with the FCSError signal
retrieval of the summed counters. asserted and the FramingError and CollisionEvent
signals deasserted and whose OctetCount is greater
than or equal to minFrameSize and less than or
equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3
Std).
Note that rptrMonitorPortRunts is not included A discontinuity may occur in the value
in this total; this is because runts usually when the value of object
indicate collision fragments, a normal network rptrMonitorPortLastChange changes.
event.
A discontinuity may occur in the value The approximate minimum time for rollover of this
when the value of object counter is 80 hours at 10Mb/s."
rptrMonitorPortLastChange changes." REFERENCE
::= { rptrMonitorPortEntry 15 } "[IEEE 802.3 Mgt], 30.4.3.1.6,
aFrameCheckSequenceErrors."
::= { rptrMonitorPortEntry 5 }
rptrMonitorPortLastChange OBJECT-TYPE rptrMonitorPortAlignmentErrors OBJECT-TYPE
SYNTAX TimeStamp SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when the last of "This counter is incremented by one for each frame
the following occurred: received on this port with the FCSError and
1) the agent cold- or warm-started; FramingError signals asserted and CollisionEvent
2) the row for the port was created signal deasserted and whose OctetCount is greater
(such as when a device or module was added than or equal to minFrameSize and less than or
to the system); or equal to maxFrameSize (Ref: IEEE 802.3 Std,
3) any condition that would cause one of 4.4.2.1). If rptrMonitorPortAlignmentErrors is
the counters for the row to experience incremented then the rptrMonitorPortFCSErrors
a discontinuity." Counter shall not be incremented for the same
::= { rptrMonitorPortEntry 16 } frame.
rptrMonitor100PortTable OBJECT-TYPE A discontinuity may occur in the value
SYNTAX SEQUENCE OF RptrMonitor100PortEntry when the value of object
MAX-ACCESS not-accessible rptrMonitorPortLastChange changes.
STATUS current
DESCRIPTION
"Table of additional performance and error
, The approximate minimum time for rollover of this
statistics for 100Mb/s ports, above and counter is 80 hours at 10Mb/s."
beyond those parameters that apply to both REFERENCE
10 and 100Mbps ports. Entries exist only for "[IEEE 802.3 Mgt], 30.4.3.1.7, aAlignmentErrors."
ports attached to 100Mbps repeaters. ::= { rptrMonitorPortEntry 6 }
The columnar object rptrMonitorPortLastChange rptrMonitorPortFrameTooLongs OBJECT-TYPE
is used to indicate possible discontinuities SYNTAX Counter32
of counter type columnar objects in this table." MAX-ACCESS read-only
::= { rptrMonitorPortInfo 2 } STATUS current
DESCRIPTION
"This counter is incremented by one for each frame
received on this port whose OctetCount is greater
than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std).
If rptrMonitorPortFrameTooLongs is incremented
then neither the rptrMonitorPortAlignmentErrors
nor the rptrMonitorPortFCSErrors counter shall be
incremented for the frame.
rptrMonitor100PortEntry OBJECT-TYPE A discontinuity may occur in the value
SYNTAX RptrMonitor100PortEntry when the value of object
MAX-ACCESS not-accessible rptrMonitorPortLastChange changes.
STATUS current
DESCRIPTION
"An entry in the table, containing performance
and error statistics for a single 100Mb/s port."
INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
::= { rptrMonitor100PortTable 1 }
RptrMonitor100PortEntry ::= The approximate minimum time for rollover of this
SEQUENCE { counter is 61 days in a 10Mb/s repeater."
rptrMonitorPortIsolates REFERENCE
Counter32, "[IEEE 802.3 Mgt], 30.4.3.1.8, aFramesTooLong."
rptrMonitorPortSymbolErrors ::= { rptrMonitorPortEntry 7 }
Counter32,
rptrMonitorPortUpper32Octets
Counter32,
rptrMonitorPortHCReadableOctets
Counter64
}
rptrMonitorPortIsolates OBJECT-TYPE rptrMonitorPortShortEvents OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter is incremented by one each time that "This counter is incremented by one for each
the repeater port automatically isolates as a CarrierEvent on this port with ActivityDuration
consequence of false carrier events. The conditions less than ShortEventMaxTime. ShortEventMaxTime is
which cause a port to automatically isolate are greater than 74 bit times and less than 82 bit
defined by the transition from the False Carrier times. ShortEventMaxTime has tolerances included
state to the Link Unstable state of the carrier to provide for circuit losses between a
integrity state diagram (figure 27-9) conformance test point at the AUI and the
[IEEE 802.3 Standard]. measurement point within the state machine.
, Notes:
Note: Isolates do not affect the value of
the PortOperStatus object.
A discontinuity may occur in the value ShortEvents may indicate externally
when the value of object generated noise hits which will cause the repeater
rptrMonitorPortLastChange changes." to transmit Runts to its other ports, or propagate
REFERENCE a collision (which may be late) back to the
"[IEEE 802.3 Mgt], 30.4.3.1.16, aIsolates." transmitting DTE and damaged frames to the rest of
::= { rptrMonitor100PortEntry 1 } the network.
rptrMonitorPortSymbolErrors OBJECT-TYPE Implementors may wish to consider selecting the
SYNTAX Counter32 ShortEventMaxTime towards the lower end of the
MAX-ACCESS read-only allowed tolerance range to accommodate bit losses
STATUS current suffered through physical channel devices not
DESCRIPTION budgeted for within this standard.
"This counter is incremented by one each time when
valid length packet was received at the port and
there was at least one occurrence of an invalid
data symbol. This can increment only once per valid
carrier event. A collision presence at any port of
the repeater containing port N, will not cause this
attribute to increment.
A discontinuity may occur in the value The significance of this attribute is different
when the value of object in 10 and 100 Mb/s collision domains. Clause 9
rptrMonitorPortLastChange changes. repeaters perform fragment extension of short
events which would be counted as runts on the
interconnect ports of other repeaters. Clause
27 repeaters do not perform fragment extension.
The approximate minimum time for rollover of this A discontinuity may occur in the value
counter is 7.4 hours at 100Mb/s." when the value of object
REFERENCE rptrMonitorPortLastChange changes.
"[IEEE 802.3 Mgt], 30.4.3.1.17,
aSymbolErrorDuringPacket."
::= { rptrMonitor100PortEntry 2 }
rptrMonitorPortUpper32Octets OBJECT-TYPE The approximate minimum time for rollover of this
SYNTAX Counter32 counter is 16 hours in a 10Mb/s repeater."
MAX-ACCESS read-only REFERENCE
STATUS current "[IEEE 802.3 Mgt], 30.4.3.1.9, aShortEvents."
DESCRIPTION ::= { rptrMonitorPortEntry 8 }
"This object is the number of octets contained in
valid frames that have been received on this port,
modulo 2**32. That is, it contains the upper 32
bits of a 64-bit octets counter, of which the
lower 32 bits are contained in the
rptrMonitorPortReadableOctets object.
, rptrMonitorPortRunts OBJECT-TYPE
This two-counter mechanism is provided for those SYNTAX Counter32
network management protocols that do not support MAX-ACCESS read-only
64-bit counters (e.g. SNMP V1) and are used to STATUS current
manage a repeater type of 100Mb/s. DESCRIPTION
"This counter is incremented by one for each
CarrierEvent on this port that meets one of the
following two conditions. Only one test need be
made. a) The ActivityDuration is greater than
ShortEventMaxTime and less than ValidPacketMinTime
and the CollisionEvent signal is deasserted. b)
The OctetCount is less than 64, the
ActivityDuration is greater than ShortEventMaxTime
and the CollisionEvent signal is deasserted.
ValidPacketMinTime is greater than or equal to 552
bit times and less than 565 bit times.
Conformance clauses for this MIB are defined such An event whose length is greater than 74 bit times
that implementation of this object is not required but less than 82 bit times shall increment either
in a system which does not support 100Mb/s. the shortEvents counter or the runts counter but
However, systems with mixed 10 and 100Mb/s ports not both. A CarrierEvent greater than or equal to
may implement this object across all ports, 552 bit times but less than 565 bit times may or
including 10Mb/s. If this object is implemented, may not be counted as a runt.
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count.
A discontinuity may occur in the value ValidPacketMinTime has tolerances included to
when the value of object provide for circuit losses between a conformance
rptrMonitorPortLastChange changes." test point at the AUI and the measurement point
::= { rptrMonitor100PortEntry 3 } within the state machine.
rptrMonitorPortHCReadableOctets OBJECT-TYPE Runts usually indicate collision fragments, a
SYNTAX Counter64 normal network event. In certain situations
MAX-ACCESS read-only associated with large diameter networks a
STATUS current percentage of collision fragments may exceed
DESCRIPTION ValidPacketMinTime.
"This object is the number of octets contained in
valid frames that have been received on this port.
This counter is incremented by OctetCount for each
frame received on this port which has been
determined to be a readable frame (i.e., including
FCS octets but excluding framing bits and dribble
bits).
This statistic provides an indicator of the total A discontinuity may occur in the value
data transferred. when the value of object
rptrMonitorPortLastChange changes.
This counter is a 64-bit version of rptrMonitor- The approximate minimum time for rollover of this
PortReadableOctets. It should be used by network counter is 16 hours in a 10Mb/s repeater."
management protocols which suppport 64-bit counters REFERENCE
(e.g. SNMPv2). "[IEEE 802.3 Mgt], 30.4.3.1.10, aRunts."
::= { rptrMonitorPortEntry 9 }
Conformance clauses for this MIB are defined such rptrMonitorPortCollisions OBJECT-TYPE
that implementation of this object is not required SYNTAX Counter32
in a system which does not support 100Mb/s. MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For a clause 9 repeater, this counter is
incremented by one for any CarrierEvent signal
on any port for which the CollisionEvent signal
on this port is asserted. For a clause 27
repeater port the counter increments on entering
the Collision Count Increment state of the
partition state diagram (fig 27-8 of
[IEEE 802.3 Std]).
, A discontinuity may occur in the value
However, systems with mixed 10 and 100Mb/s ports when the value of object
may implement this object across all ports, rptrMonitorPortLastChange changes.
including 10Mb/s. If this object is implemented,
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count.
A discontinuity may occur in the value The approximate minimum time for rollover of this
when the value of object counter is 16 hours in a 10Mb/s repeater."
rptrMonitorPortLastChange changes." REFERENCE
REFERENCE "[IEEE 802.3 Mgt], 30.4.3.1.11, aCollisions."
"[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets." ::= { rptrMonitorPortEntry 10 }
::= { rptrMonitor100PortEntry 4 }
-- New version of statistics at the repeater level. rptrMonitorPortLateEvents OBJECT-TYPE
-- SYNTAX Counter32
-- Statistics objects for each managed repeater MAX-ACCESS read-only
-- in the system. STATUS current
DESCRIPTION
"For a clause 9 repeater port, this counter is
incremented by one for each CarrierEvent
on this port in which the CollIn(X)
variable transitions to the value SQE (Ref:
9.6.6.2, IEEE 802.3 Std) while the
ActivityDuration is greater than the
LateEventThreshold. For a clause 27 repeater
port, this counter is incremented by one on
entering the Collision Count Increment state
of the partition state diagram (fig 27-8)
while the ActivityDuration is greater than
the LateEvent- Threshold. Such a CarrierEvent
is counted twice, as both a collision and as a
lateEvent.
rptrMonTable OBJECT-TYPE The LateEventThreshold is greater than 480 bit
SYNTAX SEQUENCE OF RptrMonEntry times and less than 565 bit times.
MAX-ACCESS not-accessible LateEventThreshold has tolerances included to
STATUS current permit an implementation to build a single
DESCRIPTION threshold to serve as both the LateEventThreshold
"A table of information about each and ValidPacketMinTime threshold.
non-trivial repeater. The number of entries
in this table is the same as the number of
entries in the rptrInfoTable.
The columnar object rptrInfoLastChange is A discontinuity may occur in the value
used to indicate possible discontinuities of when the value of object
counter type columnar objects in this table." rptrMonitorPortLastChange changes.
::= { rptrMonitorAllRptrInfo 1 }
rptrMonEntry OBJECT-TYPE The approximate minimum time for rollover of this
SYNTAX RptrMonEntry counter is 81 hours in a 10Mb/s repeater."
MAX-ACCESS not-accessible REFERENCE
STATUS current "[IEEE 802.3 Mgt], 30.4.3.1.12, aLateEvents."
DESCRIPTION ::= { rptrMonitorPortEntry 11 }
"An entry in the table, containing information
about a single non-trivial repeater."
INDEX { rptrInfoId }
::= { rptrMonTable 1 }
, rptrMonitorPortVeryLongEvents OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For a clause 9 repeater port, this counter
is incremented by one for each CarrierEvent
whose ActivityDuration is greater than the
MAU Jabber Lockup Protection timer TW3
(Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std).
RptrMonEntry ::= For a clause 27 repeater port, this counter
SEQUENCE { is incremented by one on entry to the
rptrMonTxCollisions Rx Jabber state of the receiver timer state
Counter32, diagram (fig 27-7). Other counters may
rptrMonTotalFrames be incremented as appropriate.
Counter32,
rptrMonTotalErrors
Counter32,
rptrMonTotalOctets
Counter32
}
rptrMonTxCollisions OBJECT-TYPE A discontinuity may occur in the value
SYNTAX Counter32 when the value of object
MAX-ACCESS read-only rptrMonitorPortLastChange changes."
STATUS current REFERENCE
DESCRIPTION "[IEEE 802.3 Mgt], 30.4.3.1.13, aVeryLongEvents."
"For a clause 9 (10Mb/s) repeater, this counter ::= { rptrMonitorPortEntry 12 }
is incremented every time the repeater state
machine enters the TRANSMIT COLLISION state
from any state other than ONE PORT LEFT
(Ref: Fig 9-2 [IEEE 802.3 Std]).
For a clause 27 repeater, this counter is rptrMonitorPortDataRateMismatches OBJECT-TYPE
incremented every time the repeater core state SYNTAX Counter32
diagram enters the Jam state as a result of MAX-ACCESS read-only
Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). STATUS current
DESCRIPTION
"This counter is incremented by one for each
frame received by this port that meets all
of the conditions required by only one of the
following two measurement methods:
The approximate minimum time for rollover of this Measurement method A: 1) The CollisionEvent
counter is 16 hours in a 10Mb/s repeater and 1.6 signal is not asserted (10Mb/s operation) or
hours in a 100Mb/s repeater." the Collision Count Increment state of the
REFERENCE partition state diagram (fig 27-8 of
"[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions" [IEEE 802.3 Std]) has not been entered
::= { rptrMonEntry 1 } (100Mb/s operation). 2) The ActivityDuration
is greater than ValidPacketMinTime. 3) The
frequency (data rate) is detectably mismatched
from the local transmit frequency.
rptrMonTotalFrames OBJECT-TYPE Measurement method B: 1) The CollisionEvent
SYNTAX Counter32 signal is not asserted (10Mb/s operation)
MAX-ACCESS read-only or the Collision Count Increment state of the
STATUS current partition state diagram (fig 27-8 of
DESCRIPTION [IEEE 802.3 Std]) has not been entered
"The number of frames of valid frame length (100Mb/s operation). 2) The OctetCount is
that have been received on the ports in this repeater greater than 63. 3) The frequency (data
and for which the FCSError and CollisionEvent rate) is detectably mismatched from the local
signals were not asserted. If an implementation transmit frequency. The exact degree of
can not obtain a count of frames as seen by mismatch is vendor specific and is to be
defined by the vendor for conformance testing.
, When this event occurs, other counters whose
the repeater itself, this counter may be increment conditions were satisfied may or may not
implemented as the summation of the values of the also be incremented, at the implementor's
rptrMonitorPortReadableFrames counters for all of discretion. Whether or not the repeater was able
the ports in the repeater. to maintain data integrity is beyond the scope of
this standard.
This statistic provides one of the parameters A discontinuity may occur in the value
necessary for obtaining the packet error rate. when the value of object
The approximate minimum time for rollover of this rptrMonitorPortLastChange changes."
counter is 80 hours in a 10Mb/s repeater." REFERENCE
::= { rptrMonEntry 3 } "[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches."
::= { rptrMonitorPortEntry 13 }
rptrMonTotalErrors OBJECT-TYPE rptrMonitorPortAutoPartitions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of errors which have occurred on "This counter is incremented by one for
all of the ports in this repeater. The errors each time the repeater has automatically
included in this count are the same as those listed partitioned this port.
for the rptrMonitorPortTotalErrors counter. If an
implementation can not obtain a count of these
errors as seen by the repeater itself, this counter
may be implemented as the summation of the values of
the rptrMonitorPortTotalErrors counters for all of
the ports in the repeater."
::= { rptrMonEntry 4 }
rptrMonTotalOctets OBJECT-TYPE The conditions that cause a clause 9
SYNTAX Counter32 repeater port to partition are specified in
MAX-ACCESS read-only the partition state diagram in clause 9 of
STATUS current [IEEE 802.3 Std]. They are not differentiated
DESCRIPTION here. A clause 27 repeater port partitions
"The total number of octets contained in the valid on entry to the Partition Wait state of the
frames that have been received on the ports in partition state diagram (fig 27-8 in
this group. If an implementation can not obtain [IEEE 802.3 Std]).
a count of octets as seen by the repeater itself,
this counter may be the summation of the
values of the rptrMonitorPortReadableOctets
counters for all of the ports in the group.
This statistic provides an indicator of the total A discontinuity may occur in the value
data transferred. The approximate minimum time when the value of object
for rollover of this counter in a 10Mb/s repeater rptrMonitorPortLastChange changes."
is 58 minutes divided by the number of ports in REFERENCE
the repeater. "[IEEE 802.3 Mgt], 30.4.3.1.15, aAutoPartitions."
::= { rptrMonitorPortEntry 14 }
, rptrMonitorPortTotalErrors OBJECT-TYPE
For 100Mb/s repeaters processing traffic at a SYNTAX Counter32
maximum rate, this counter can roll over in less MAX-ACCESS read-only
than 6 minutes divided by the number of ports in STATUS current
the repeater. Since that amount of time could DESCRIPTION
be less than a management station's poll cycle "The total number of errors which have occurred on
time, in order to avoid a loss of information a this port. This counter is the summation of the
management station is advised to also poll the values of other error counters (for the same
rptrMonUpper32TotalOctets object, or to use the port), namely:
64-bit counter defined by rptrMonHCTotalOctets
instead of the two 32-bit counters."
::= { rptrMonEntry 5 }
rptrMon100Table OBJECT-TYPE rptrMonitorPortFCSErrors,
SYNTAX SEQUENCE OF RptrMon100Entry rptrMonitorPortAlignmentErrors,
MAX-ACCESS not-accessible rptrMonitorPortFrameTooLongs,
STATUS current rptrMonitorPortShortEvents,
DESCRIPTION rptrMonitorPortLateEvents,
"A table of additional information about each rptrMonitorPortVeryLongEvents,
100Mb/s repeater, augmenting the entries in rptrMonitorPortDataRateMismatches, and
the rptrMonTable. Entries exist in this table rptrMonitorPortSymbolErrors.
only for 100Mb/s repeaters.
The columnar object rptrInfoLastChange is This counter is redundant in the sense that it is
used to indicate possible discontinuities of the summation of information already available
counter type columnar objects in this table." through other objects. However, it is included
::= { rptrMonitorAllRptrInfo 2 } specifically because the regular retrieval of this
object as a means of tracking the health of a port
provides a considerable optimization of network
management traffic over the otherwise necessary
retrieval of the summed counters.
rptrMon100Entry OBJECT-TYPE Note that rptrMonitorPortRunts is not included
SYNTAX RptrMon100Entry in this total; this is because runts usually
MAX-ACCESS not-accessible indicate collision fragments, a normal network
STATUS current event.
DESCRIPTION
"An entry in the table, containing information
about a single 100Mbps repeater."
INDEX { rptrInfoId }
::= { rptrMon100Table 1 }
RptrMon100Entry ::= A discontinuity may occur in the value
SEQUENCE { when the value of object
rptrMonUpper32TotalOctets rptrMonitorPortLastChange changes."
Counter32, ::= { rptrMonitorPortEntry 15 }
rptrMonHCTotalOctets
Counter64
}
, rptrMonitorPortLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the last of
the following occurred:
1) the agent cold- or warm-started;
2) the row for the port was created
(such as when a device or module was added
to the system); or
3) any condition that would cause one of
the counters for the row to experience
a discontinuity."
::= { rptrMonitorPortEntry 16 }
rptrMonUpper32TotalOctets OBJECT-TYPE rptrMonitor100PortTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF RptrMonitor100PortEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of octets contained in the valid "Table of additional performance and error
frames that have been received on the ports in statistics for 100Mb/s ports, above and
this repeater, modulo 2**32. That is, it contains beyond those parameters that apply to both
the upper 32 bits of a 64-bit counter, of which 10 and 100Mbps ports. Entries exist only for
the lower 32 bits are contained in the ports attached to 100Mbps repeaters.
rptrMonTotalOctets object. If an implementation
can not obtain a count of octets as seen
by the repeater itself, the 64-bit value
may be the summation of the values of the
rptrMonitorPortReadableOctets counters combined
with the corresponding rptrMonitorPortUpper32Octets
counters for all of the ports in the repeater.
This statistic provides an indicator of the total The columnar object rptrMonitorPortLastChange
data transferred within the repeater. is used to indicate possible discontinuities
of counter type columnar objects in this table."
::= { rptrMonitorPortInfo 2 }
This two-counter mechanism is provided for those rptrMonitor100PortEntry OBJECT-TYPE
network management protocols that do not support SYNTAX RptrMonitor100PortEntry
64-bit counters (e.g. SNMP V1) and are used to MAX-ACCESS not-accessible
manage a repeater type of 100Mb/s. STATUS current
DESCRIPTION
"An entry in the table, containing performance
and error statistics for a single 100Mb/s port."
INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
::= { rptrMonitor100PortTable 1 }
Conformance clauses for this MIB are defined such RptrMonitor100PortEntry ::=
that implementation of this object is not required SEQUENCE {
in a system which does not support 100Mb/s. rptrMonitorPortIsolates
However, systems with mixed 10 and 100Mb/s ports Counter32,
may implement this object across all ports, rptrMonitorPortSymbolErrors
including 10Mb/s. If this object is implemented, Counter32,
it must be according to the definition in the first rptrMonitorPortUpper32Octets
paragraph of this description; that is, the value Counter32,
of this object MUST be a valid count." rptrMonitorPortHCReadableOctets
::= { rptrMon100Entry 1 } Counter64
}
rptrMonHCTotalOctets OBJECT-TYPE rptrMonitorPortIsolates OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of octets contained in the valid "This counter is incremented by one each time that
frames that have been received on the ports in the repeater port automatically isolates as a
this group. If a implementation can not obtain consequence of false carrier events. The conditions
which cause a port to automatically isolate are
defined by the transition from the False Carrier
state to the Link Unstable state of the carrier
integrity state diagram (figure 27-9)
[IEEE 802.3 Standard].
, Note: Isolates do not affect the value of
a count of octets as seen by the repeater itself, the PortOperStatus object.
this counter may be the summation of the
values of the rptrMonitorPortReadableOctets
counters for all of the ports in the group.
This statistic provides an indicator of the total A discontinuity may occur in the value
data transferred. when the value of object
rptrMonitorPortLastChange changes."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.16, aIsolates."
::= { rptrMonitor100PortEntry 1 }
This counter is a 64-bit (high-capacity) version rptrMonitorPortSymbolErrors OBJECT-TYPE
of rptrMonUpper32TotalOctets and rptrMonTotalOctets. SYNTAX Counter32
It should be used by network management protocols MAX-ACCESS read-only
which support 64-bit counters (e.g. SNMPv2). STATUS current
DESCRIPTION
"This counter is incremented by one each time when
valid length packet was received at the port and
there was at least one occurrence of an invalid
data symbol. This can increment only once per valid
carrier event. A collision presence at any port of
the repeater containing port N, will not cause this
attribute to increment.
Conformance clauses for this MIB are defined such A discontinuity may occur in the value
that implementation of this object is not required when the value of object
in a system which does not support 100Mb/s. rptrMonitorPortLastChange changes.
However, systems with mixed 10 and 100Mb/s ports
may implement this object across all ports,
including 10Mb/s. If this object is implemented,
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count."
::= { rptrMon100Entry 2 }
-- The approximate minimum time for rollover of this
-- The Repeater Address Search Table counter is 7.4 hours at 100Mb/s."
-- REFERENCE
-- This table provides an active address tracking "[IEEE 802.3 Mgt], 30.4.3.1.17,
-- capability which can be also used to collect the aSymbolErrorDuringPacket."
-- necessary information for mapping the topology ::= { rptrMonitor100PortEntry 2 }
-- of a network. Note that an NMS is required to have
-- read-write access to the table in order to access
-- this function. Section 4, "Topology Mapping",
-- contains a description of an algorithm which can
-- make use of this table, in combination with the
-- forwarding databases of managed bridges/switches
-- in the network, to map network topology.
--
rptrAddrSearchTable OBJECT-TYPE rptrMonitorPortUpper32Octets OBJECT-TYPE
SYNTAX SEQUENCE OF RptrAddrSearchEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is the number of octets contained in
valid frames that have been received on this port,
modulo 2**32. That is, it contains the upper 32
bits of a 64-bit octets counter, of which the
lower 32 bits are contained in the
rptrMonitorPortReadableOctets object.
, This two-counter mechanism is provided for those
"This table contains one entry per repeater in the network management protocols that do not support
system. It defines objects which allow a network 64-bit counters (e.g. SNMP V1) and are used to
management application to instruct an agent to watch manage a repeater type of 100Mb/s.
for a given MAC address and report which port it
was seen on. Only one address search can be in
progress on each repeater at any one time. Before
starting an address search, a management application
should obtain 'ownership' of the entry in
rptrAddrSearchTable for the repeater that is to
perform the search. This is accomplished with the
rptrAddrSearchLock and rptrAddrSearchStatus as
follows:
try_again: Conformance clauses for this MIB are defined such
get(rptrAddrSearchLock, rptrAddrSearchStatus) that implementation of this object is not required
while (rptrAddrSearchStatus != notInUse) in a system which does not support 100Mb/s.
{ However, systems with mixed 10 and 100Mb/s ports
/* Loop waiting for objects to be available*/ may implement this object across all ports,
short delay including 10Mb/s. If this object is implemented,
get(rptrAddrSearchLock, rptrAddrSearchStatus) it must be according to the definition in the first
} paragraph of this description; that is, the value
of this object MUST be a valid count.
/* Try to claim map objects */ A discontinuity may occur in the value
lock_value = rptrAddrSearchLock when the value of object
if ( set(rptrAddrSearchLock = lock_value, rptrMonitorPortLastChange changes."
rptrAddrSearchStatus = inUse,
rptrAddrSearchOwner = 'my-IP-address)
== FAILURE)
/* Another manager got the lock */
goto try_again
/* I have the lock */ ::= { rptrMonitor100PortEntry 3 }
set (rptrAddrSearchAddress = <search target>)
wait for rptrAddrSearchState to change from none rptrMonitorPortHCReadableOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the number of octets contained in
valid frames that have been received on this port.
This counter is incremented by OctetCount for each
frame received on this port which has been
determined to be a readable frame (i.e., including
FCS octets but excluding framing bits and dribble
bits).
if (rptrAddrSearchState == single) This statistic provides an indicator of the total
get (rptrAddrSearchGroup, rptrAddrSearchPort) data transferred.
/* release the lock, making sure not to overwrite This counter is a 64-bit version of rptrMonitor-
anyone else's lock */ PortReadableOctets. It should be used by network
set (rptrAddrSearchLock = lock_value+1, management protocols which suppport 64-bit counters
rptrAddrSearchStatus = notInUse, (e.g. SNMPv2).
rptrAddrSearchOwner = '')
, Conformance clauses for this MIB are defined such
that implementation of this object is not required
in a system which does not support 100Mb/s.
However, systems with mixed 10 and 100Mb/s ports
may implement this object across all ports,
including 10Mb/s. If this object is implemented,
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count.
A management station first retrieves the values of A discontinuity may occur in the value
the appropriate instances of the rptrAddrSearchLock when the value of object
and rptrAddrSearchStatus objects, periodically rptrMonitorPortLastChange changes."
repeating the retrieval if necessary, until the value REFERENCE
of rptrAddrSearchStatus is 'notInUse'. The "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets."
management station then tries to set the same ::= { rptrMonitor100PortEntry 4 }
instance of the rptrAddrSearchLock object to the
value it just retrieved, the same instance of the
rptrAddrSearchStatus object to 'inUse', and the
corresponding instance of rptrAddrSearchOwner to a
value indicating itself. If the set operation
succeeds, then the management station has obtained
ownership of the rptrAddrSearchEntry, and the value
of rptrAddrSearchLock is incremented by the agent (as
per the semantics of TestAndIncr). Failure of the
set operation indicates that some other manager has
obtained ownership of the rptrAddrSearchEntry.
Once ownership is obtained, the management station -- New version of statistics at the repeater level.
can proceed with the search operation. Note that the --
agent will reset rptrAddrSearchStatus to 'notInUse' -- Statistics objects for each managed repeater
if it has been in the 'inUse' state for an abnormally -- in the system.
long period of time, to prevent a misbehaving manager
from permanently locking the entry. It is suggested
that this timeout period be between one and five
minutes.
When the management station has completed its search rptrMonTable OBJECT-TYPE
operation, it should free the entry by setting SYNTAX SEQUENCE OF RptrMonEntry
the instance of the rptrAddrSearchLock object to the MAX-ACCESS not-accessible
previous value + 1, the instance of the STATUS current
rptrAddrSearchStatus to 'notInUse', and the instance DESCRIPTION
of rptrAddrSearchOwner to a zero length string. This "A table of information about each
is done to prevent overwriting another station's non-trivial repeater. The number of entries
lock." in this table is the same as the number of
::= { rptrAddrTrackRptrInfo 1 } entries in the rptrInfoTable.
rptrAddrSearchEntry OBJECT-TYPE The columnar object rptrInfoLastChange is
SYNTAX RptrAddrSearchEntry used to indicate possible discontinuities of
MAX-ACCESS not-accessible counter type columnar objects in this table."
STATUS current ::= { rptrMonitorAllRptrInfo 1 }
DESCRIPTION
"An entry containing objects for invoking an address
search on a repeater."
INDEX { rptrInfoId }
, rptrMonEntry OBJECT-TYPE
::= { rptrAddrSearchTable 1 } SYNTAX RptrMonEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single non-trivial repeater."
INDEX { rptrInfoId }
::= { rptrMonTable 1 }
RptrAddrSearchEntry ::= RptrMonEntry ::=
SEQUENCE { SEQUENCE {
rptrAddrSearchLock TestAndIncr, rptrMonTxCollisions
rptrAddrSearchStatus INTEGER, Counter32,
rptrAddrSearchAddress MacAddress, rptrMonTotalFrames
rptrAddrSearchState INTEGER, Counter32,
rptrAddrSearchGroup Integer32, rptrMonTotalErrors
rptrAddrSearchPort Integer32, Counter32,
rptrAddrSearchOwner OwnerString rptrMonTotalOctets
} Counter32
}
rptrAddrSearchLock OBJECT-TYPE rptrMonTxCollisions OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX Counter32
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used by a management station as an "For a clause 9 (10Mb/s) repeater, this counter
advisory lock for this rptrAddrSearchEntry." is incremented every time the repeater state
::= { rptrAddrSearchEntry 1 } machine enters the TRANSMIT COLLISION state
from any state other than ONE PORT LEFT
(Ref: Fig 9-2 [IEEE 802.3 Std]).
rptrAddrSearchStatus OBJECT-TYPE For a clause 27 repeater, this counter is
SYNTAX INTEGER { incremented every time the repeater core state
notInUse(1), diagram enters the Jam state as a result of
inUse(2) Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]).
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used to indicate that some management
station is currently using this rptrAddrSearchEntry.
Cooperating managers should set this object to
'notInUse' when they are finished using this entry.
The agent will automatically set the value of this
object to 'notInUse' if it has been set to 'inUse'
for an unusually long period of time."
::= { rptrAddrSearchEntry 2 }
rptrAddrSearchAddress OBJECT-TYPE The approximate minimum time for rollover of this
SYNTAX MacAddress counter is 16 hours in a 10Mb/s repeater and 1.6
MAX-ACCESS read-write hours in a 100Mb/s repeater."
STATUS current REFERENCE
DESCRIPTION "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions"
::= { rptrMonEntry 1 }
, rptrMonTotalFrames OBJECT-TYPE
"This object is used to search for a specified MAC SYNTAX Counter32
address. When this object is set, an address search MAX-ACCESS read-only
begins. This automatically sets the corresponding STATUS current
instance of the rptrAddrSearchState object to 'none' DESCRIPTION
and the corresponding instances of the "The number of frames of valid frame length
rptrAddrSearchGroup and rptrAddrSearchPort objects to that have been received on the ports in this repeater
0. and for which the FCSError and CollisionEvent
signals were not asserted. If an implementation
can not obtain a count of frames as seen by
the repeater itself, this counter may be
implemented as the summation of the values of the
rptrMonitorPortReadableFrames counters for all of
the ports in the repeater.
When a valid frame is received by this repeater with This statistic provides one of the parameters
a source MAC address which matches the current value necessary for obtaining the packet error rate.
of rptrAddrSearchAddress, the agent will update the The approximate minimum time for rollover of this
corresponding instances of rptrAddrSearchState, counter is 80 hours in a 10Mb/s repeater."
rptrAddrSearchGroup and rptrAddrSearchPort to reflect ::= { rptrMonEntry 3 }
the current status of the search, and the group and
port on which the frame was seen."
::= { rptrAddrSearchEntry 3 }
rptrAddrSearchState OBJECT-TYPE rptrMonTotalErrors OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Counter32
none(1), MAX-ACCESS read-only
single(2), STATUS current
multiple(3) DESCRIPTION
} "The total number of errors which have occurred on
MAX-ACCESS read-only all of the ports in this repeater. The errors
STATUS current included in this count are the same as those listed
DESCRIPTION for the rptrMonitorPortTotalErrors counter. If an
"The current state of the MAC address search on this implementation can not obtain a count of these
repeater. This object is initialized to 'none' when errors as seen by the repeater itself, this counter
the corresponding instance of rptrAddrSearchAddress may be implemented as the summation of the values of
is set. If the agent detects the address on exactly the rptrMonitorPortTotalErrors counters for all of
one port, it will set this object to 'single', and the ports in the repeater."
set the corresponding instances of ::= { rptrMonEntry 4 }
rptrAddrSearchGroup and rptrAddrSearchPort to reflect
the group and port on which the address was heard.
If the agent detects the address on more than one
port, it will set this object to 'multiple'."
::= { rptrAddrSearchEntry 4 }
rptrAddrSearchGroup OBJECT-TYPE rptrMonTotalOctets OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group from which an error-free frame whose "The total number of octets contained in the valid
source address is equal to the corresponding instance frames that have been received on the ports in
this group. If an implementation can not obtain
a count of octets as seen by the repeater itself,
this counter may be the summation of the
values of the rptrMonitorPortReadableOctets
counters for all of the ports in the group.
, This statistic provides an indicator of the total
of rptrAddrSearchAddress has been received. The data transferred. The approximate minimum time
value of this object is undefined when the for rollover of this counter in a 10Mb/s repeater
corresponding instance of rptrAddrSearchState is is 58 minutes divided by the number of ports in
equal to 'none' or 'multiple'." the repeater.
::= { rptrAddrSearchEntry 5 }
rptrAddrSearchPort OBJECT-TYPE For 100Mb/s repeaters processing traffic at a
SYNTAX Integer32 (0..2147483647) maximum rate, this counter can roll over in less
MAX-ACCESS read-only than 6 minutes divided by the number of ports in
STATUS current the repeater. Since that amount of time could
DESCRIPTION be less than a management station's poll cycle
"The port rom which an error-free frame whose time, in order to avoid a loss of information a
source address is equal to the corresponding instance management station is advised to also poll the
of rptrAddrSearchAddress has been received. The rptrMonUpper32TotalOctets object, or to use the
value of this object is undefined when the 64-bit counter defined by rptrMonHCTotalOctets
corresponding instance of rptrAddrSearchState is instead of the two 32-bit counters."
equal to 'none' or 'multiple'." ::= { rptrMonEntry 5 }
::= { rptrAddrSearchEntry 6 }
rptrAddrSearchOwner OBJECT-TYPE rptrMon100Table OBJECT-TYPE
SYNTAX OwnerString SYNTAX SEQUENCE OF RptrMon100Entry
MAX-ACCESS read-write MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entity which currently has 'ownership' of this "A table of additional information about each
rptrAddrSearchEntry." 100Mb/s repeater, augmenting the entries in
::= { rptrAddrSearchEntry 7 } the rptrMonTable. Entries exist in this table
only for 100Mb/s repeaters.
-- The columnar object rptrInfoLastChange is
-- The Port Address Tracking Table used to indicate possible discontinuities of
-- counter type columnar objects in this table."
-- This table provides a way for a network management ::= { rptrMonitorAllRptrInfo 2 }
-- application to passively gather information (using
-- read-only privileges) about which network addresses
-- are connected to which ports of a repeater.
--
rptrAddrTrackTable OBJECT-TYPE rptrMon100Entry OBJECT-TYPE
SYNTAX SEQUENCE OF RptrAddrTrackEntry SYNTAX RptrMon100Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of address mapping information about the "An entry in the table, containing information
ports." about a single 100Mbps repeater."
INDEX { rptrInfoId }
::= { rptrMon100Table 1 }
, RptrMon100Entry ::=
SEQUENCE {
rptrMonUpper32TotalOctets
Counter32,
rptrMonHCTotalOctets
Counter64
}
::= { rptrAddrTrackPortInfo 1 } rptrMonUpper32TotalOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets contained in the valid
frames that have been received on the ports in
this repeater, modulo 2**32. That is, it contains
the upper 32 bits of a 64-bit counter, of which
the lower 32 bits are contained in the
rptrMonTotalOctets object. If an implementation
can not obtain a count of octets as seen
by the repeater itself, the 64-bit value
may be the summation of the values of the
rptrMonitorPortReadableOctets counters combined
with the corresponding rptrMonitorPortUpper32Octets
counters for all of the ports in the repeater.
rptrAddrTrackEntry OBJECT-TYPE This statistic provides an indicator of the total
SYNTAX RptrAddrTrackEntry data transferred within the repeater.
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing address mapping
information about a single port."
INDEX { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex }
::= { rptrAddrTrackTable 1 }
RptrAddrTrackEntry ::= This two-counter mechanism is provided for those
SEQUENCE { network management protocols that do not support
rptrAddrTrackGroupIndex 64-bit counters (e.g. SNMP V1) and are used to
INTEGER, manage a repeater type of 100Mb/s.
rptrAddrTrackPortIndex
INTEGER,
rptrAddrTrackLastSourceAddress -- DEPRECATED OBJECT
MacAddress,
rptrAddrTrackSourceAddrChanges
Counter32,
rptrAddrTrackNewLastSrcAddress
OptMacAddr,
rptrAddrTrackCapacity
Integer32
}
rptrAddrTrackGroupIndex OBJECT-TYPE Conformance clauses for this MIB are defined such
SYNTAX INTEGER (1..2147483647) that implementation of this object is not required
MAX-ACCESS read-only in a system which does not support 100Mb/s.
STATUS current However, systems with mixed 10 and 100Mb/s ports
DESCRIPTION may implement this object across all ports,
"This object identifies the group containing the including 10Mb/s. If this object is implemented,
port for which this entry contains information." it must be according to the definition in the first
::= { rptrAddrTrackEntry 1 } paragraph of this description; that is, the value
of this object MUST be a valid count."
::= { rptrMon100Entry 1 }
rptrAddrTrackPortIndex OBJECT-TYPE rptrMonHCTotalOctets OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the port within the group "The total number of octets contained in the valid
for which this entry contains information." frames that have been received on the ports in
REFERENCE this group. If a implementation can not obtain
a count of octets as seen by the repeater itself,
this counter may be the summation of the
values of the rptrMonitorPortReadableOctets
counters for all of the ports in the group.
, This statistic provides an indicator of the total
"[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID." data transferred.
::= { rptrAddrTrackEntry 2 }
rptrAddrTrackLastSourceAddress OBJECT-TYPE This counter is a 64-bit (high-capacity) version
SYNTAX MacAddress of rptrMonUpper32TotalOctets and rptrMonTotalOctets.
MAX-ACCESS read-only It should be used by network management protocols
STATUS deprecated which support 64-bit counters (e.g. SNMPv2).
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
This object is the SourceAddress of the last Conformance clauses for this MIB are defined such
readable frame (i.e., counted by that implementation of this object is not required
rptrMonitorPortReadableFrames) received by this in a system which does not support 100Mb/s.
port. However, systems with mixed 10 and 100Mb/s ports
may implement this object across all ports,
including 10Mb/s. If this object is implemented,
it must be according to the definition in the first
paragraph of this description; that is, the value
of this object MUST be a valid count."
::= { rptrMon100Entry 2 }
This object has been deprecated because its value --
is undefined when no frames have been observed on -- The Repeater Address Search Table
this port. The replacement object is --
rptrAddrTrackNewLastSrcAddress." -- This table provides an active address tracking
REFERENCE -- capability which can be also used to collect the
"[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress." -- necessary information for mapping the topology
::= { rptrAddrTrackEntry 3 } -- of a network. Note that an NMS is required to have
-- read-write access to the table in order to access
-- this function. Section 4, "Topology Mapping",
-- contains a description of an algorithm which can
-- make use of this table, in combination with the
-- forwarding databases of managed bridges/switches
-- in the network, to map network topology.
--
rptrAddrTrackSourceAddrChanges OBJECT-TYPE rptrAddrSearchTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF RptrAddrSearchEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter is incremented by one for each time "This table contains one entry per repeater in the
that the rptrAddrTrackLastSourceAddress attribute system. It defines objects which allow a network
for this port has changed. management application to instruct an agent to watch
for a given MAC address and report which port it
was seen on. Only one address search can be in
progress on each repeater at any one time. Before
starting an address search, a management application
should obtain 'ownership' of the entry in
rptrAddrSearchTable for the repeater that is to
perform the search. This is accomplished with the
rptrAddrSearchLock and rptrAddrSearchStatus as
follows:
This may indicate whether a link is connected to a try_again:
single DTE or another multi-user segment. get(rptrAddrSearchLock, rptrAddrSearchStatus)
while (rptrAddrSearchStatus != notInUse)
{
/* Loop waiting for objects to be available*/
short delay
get(rptrAddrSearchLock, rptrAddrSearchStatus)
}
A discontinuity may occur in the value when the /* Try to claim map objects */
value of object rptrMonitorPortLastChange changes. lock_value = rptrAddrSearchLock
if ( set(rptrAddrSearchLock = lock_value,
rptrAddrSearchStatus = inUse,
rptrAddrSearchOwner = 'my-IP-address)
== FAILURE)
/* Another manager got the lock */
goto try_again
The approximate minimum time for rollover of this /* I have the lock */
counter is 81 hours in a 10Mb/s repeater." set (rptrAddrSearchAddress = <search target>)
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.19, aSourceAddressChanges."
::= { rptrAddrTrackEntry 4 }
rptrAddrTrackNewLastSrcAddress OBJECT-TYPE wait for rptrAddrSearchState to change from none
, if (rptrAddrSearchState == single)
SYNTAX OptMacAddr get (rptrAddrSearchGroup, rptrAddrSearchPort)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the SourceAddress of the last
readable frame (i.e., counted by
rptrMonitorPortReadableFrames) received by this
port. If no frames have been received by this
port since the agent began monitoring the port
activity, the agent shall return a string of
length zero."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress."
::= { rptrAddrTrackEntry 5 }
rptrAddrTrackCapacity OBJECT-TYPE /* release the lock, making sure not to overwrite
SYNTAX Integer32 anyone else's lock */
MAX-ACCESS read-only set (rptrAddrSearchLock = lock_value+1,
STATUS current rptrAddrSearchStatus = notInUse,
DESCRIPTION rptrAddrSearchOwner = '')
"The maximum number of addresses that can be
detected on this port. This value indicates
to the maximum number of entries in the
rptrExtAddrTrackTable relative to this port.
If this object has the value of 1, the agent A management station first retrieves the values of
implements only the LastSourceAddress mechanism the appropriate instances of the rptrAddrSearchLock
described by RFC 1368 or RFC 1516." and rptrAddrSearchStatus objects, periodically
::= { rptrAddrTrackEntry 6 } repeating the retrieval if necessary, until the value
of rptrAddrSearchStatus is 'notInUse'. The
management station then tries to set the same
instance of the rptrAddrSearchLock object to the
value it just retrieved, the same instance of the
rptrAddrSearchStatus object to 'inUse', and the
corresponding instance of rptrAddrSearchOwner to a
value indicating itself. If the set operation
succeeds, then the management station has obtained
ownership of the rptrAddrSearchEntry, and the value
of rptrAddrSearchLock is incremented by the agent (as
per the semantics of TestAndIncr). Failure of the
set operation indicates that some other manager has
obtained ownership of the rptrAddrSearchEntry.
-- Table for multiple addresses per port Once ownership is obtained, the management station
can proceed with the search operation. Note that the
agent will reset rptrAddrSearchStatus to 'notInUse'
if it has been in the 'inUse' state for an abnormally
long period of time, to prevent a misbehaving manager
from permanently locking the entry. It is suggested
that this timeout period be between one and five
minutes.
rptrExtAddrTrackTable OBJECT-TYPE When the management station has completed its search
SYNTAX SEQUENCE OF RptrExtAddrTrackEntry operation, it should free the entry by setting
MAX-ACCESS not-accessible the instance of the rptrAddrSearchLock object to the
STATUS current previous value + 1, the instance of the
DESCRIPTION rptrAddrSearchStatus to 'notInUse', and the instance
"A table to extend the address tracking table (i.e., of rptrAddrSearchOwner to a zero length string. This
rptrAddrTrackTable) with a list of source MAC is done to prevent overwriting another station's
addresses that were recently received on each port. lock."
The number of ports is the same as the number ::= { rptrAddrTrackRptrInfo 1 }
of entries in table rptrPortTable. The number of
entries in this table depends on the agent/repeater
implementation and the number of different
, rptrAddrSearchEntry OBJECT-TYPE
addresses received on each port. SYNTAX RptrAddrSearchEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing objects for invoking an address
search on a repeater."
INDEX { rptrInfoId }
::= { rptrAddrSearchTable 1 }
The first entry for each port contains RptrAddrSearchEntry ::=
the same MAC address that is given by the SEQUENCE {
rptrAddrTrackNewLastSrcAddress for that port. rptrAddrSearchLock TestAndIncr,
rptrAddrSearchStatus INTEGER,
rptrAddrSearchAddress MacAddress,
rptrAddrSearchState INTEGER,
rptrAddrSearchGroup Integer32,
rptrAddrSearchPort Integer32,
rptrAddrSearchOwner OwnerString
}
Entries in this table for a particular port are rptrAddrSearchLock OBJECT-TYPE
retained when that port is switched from one SYNTAX TestAndIncr
repeater to another. MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used by a management station as an
advisory lock for this rptrAddrSearchEntry."
::= { rptrAddrSearchEntry 1 }
The ordering of MAC addresses listed for a rptrAddrSearchStatus OBJECT-TYPE
particular port is implementation dependent." SYNTAX INTEGER {
::= { rptrAddrTrackPortInfo 2 } notInUse(1),
inUse(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used to indicate that some management
station is currently using this rptrAddrSearchEntry.
Cooperating managers should set this object to
'notInUse' when they are finished using this entry.
The agent will automatically set the value of this
object to 'notInUse' if it has been set to 'inUse'
for an unusually long period of time."
::= { rptrAddrSearchEntry 2 }
rptrExtAddrTrackEntry OBJECT-TYPE rptrAddrSearchAddress OBJECT-TYPE
SYNTAX RptrExtAddrTrackEntry SYNTAX MacAddress
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A row in the table of extended address tracking "This object is used to search for a specified MAC
information for ports. Entries can not be directly address. When this object is set, an address search
created or deleted via SNMP operations." begins. This automatically sets the corresponding
INDEX { rptrAddrTrackGroupIndex, instance of the rptrAddrSearchState object to 'none'
rptrAddrTrackPortIndex, and the corresponding instances of the
rptrExtAddrTrackMacIndex } rptrAddrSearchGroup and rptrAddrSearchPort objects to
::= { rptrExtAddrTrackTable 1 } 0.
RptrExtAddrTrackEntry ::= SEQUENCE { When a valid frame is received by this repeater with
rptrExtAddrTrackMacIndex Integer32, a source MAC address which matches the current value
rptrExtAddrTrackSourceAddress MacAddress of rptrAddrSearchAddress, the agent will update the
} corresponding instances of rptrAddrSearchState,
rptrAddrSearchGroup and rptrAddrSearchPort to reflect
the current status of the search, and the group and
port on which the frame was seen."
::= { rptrAddrSearchEntry 3 }
rptrExtAddrTrackMacIndex OBJECT-TYPE rptrAddrSearchState OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX INTEGER {
MAX-ACCESS read-only none(1),
STATUS current single(2),
DESCRIPTION multiple(3)
"The index of a source MAC address seen on }
the port. MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current state of the MAC address search on this
repeater. This object is initialized to 'none' when
the corresponding instance of rptrAddrSearchAddress
is set. If the agent detects the address on exactly
one port, it will set this object to 'single', and
set the corresponding instances of
rptrAddrSearchGroup and rptrAddrSearchPort to reflect
the group and port on which the address was heard.
If the agent detects the address on more than one
port, it will set this object to 'multiple'."
::= { rptrAddrSearchEntry 4 }
The ordering of MAC addresses listed for a rptrAddrSearchGroup OBJECT-TYPE
particular port is implementation dependent. SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The group from which an error-free frame whose
source address is equal to the corresponding instance
of rptrAddrSearchAddress has been received. The
value of this object is undefined when the
corresponding instance of rptrAddrSearchState is
equal to 'none' or 'multiple'."
::= { rptrAddrSearchEntry 5 }
There is no implied relationship between a rptrAddrSearchPort OBJECT-TYPE
particular index and a particular MAC SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The port rom which an error-free frame whose
source address is equal to the corresponding instance
of rptrAddrSearchAddress has been received. The
value of this object is undefined when the
corresponding instance of rptrAddrSearchState is
equal to 'none' or 'multiple'."
::= { rptrAddrSearchEntry 6 }
, rptrAddrSearchOwner OBJECT-TYPE
address. The index for a particular MAC SYNTAX OwnerString
address may change without notice." MAX-ACCESS read-write
::= { rptrExtAddrTrackEntry 1 } STATUS current
DESCRIPTION
"The entity which currently has 'ownership' of this
rptrAddrSearchEntry."
::= { rptrAddrSearchEntry 7 }
rptrExtAddrTrackSourceAddress OBJECT-TYPE --
SYNTAX MacAddress -- The Port Address Tracking Table
MAX-ACCESS read-only --
STATUS current -- This table provides a way for a network management
DESCRIPTION -- application to passively gather information (using
"The source MAC address from a readable frame -- read-only privileges) about which network addresses
(i.e., counted by rptrMonitorPortReadableFrames) -- are connected to which ports of a repeater.
recently received by the port." --
REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress."
::= { rptrExtAddrTrackEntry 2 }
-- The Repeater Top "N" Port Group rptrAddrTrackTable OBJECT-TYPE
SYNTAX SEQUENCE OF RptrAddrTrackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of address mapping information about the
ports."
::= { rptrAddrTrackPortInfo 1 }
-- The Repeater Top N Port group is used to prepare reports that rptrAddrTrackEntry OBJECT-TYPE
-- describe a list of ports ordered by one of the statistics in the SYNTAX RptrAddrTrackEntry
-- Repeater Monitor Port Table. The statistic chosen by the MAX-ACCESS not-accessible
-- management station is sampled over a management STATUS current
-- station-specified time interval, making the report rate based. DESCRIPTION
-- The management station also specifies the number of ports that "An entry in the table, containing address mapping
-- are reported. information about a single port."
-- INDEX { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex }
-- The rptrTopNPortControlTable is used to initiate the generation ::= { rptrAddrTrackTable 1 }
-- 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 RptrAddrTrackEntry ::=
-- implementations if ports' assignment to repeaters changes SEQUENCE {
-- during the collection of data for a Top "N" report. rptrAddrTrackGroupIndex
-- A management application could read the corresponding INTEGER,
-- rptrMonitorPortLastChange timestamp in order to check rptrAddrTrackPortIndex
-- whether a discontinuity occurred. INTEGER,
rptrAddrTrackLastSourceAddress -- DEPRECATED OBJECT
MacAddress,
rptrAddrTrackSourceAddrChanges
Counter32,
rptrAddrTrackNewLastSrcAddress
OptMacAddr,
rptrAddrTrackCapacity
Integer32
}
rptrTopNPortControlTable OBJECT-TYPE rptrAddrTrackGroupIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the group containing the
port for which this entry contains information."
::= { rptrAddrTrackEntry 1 }
, rptrAddrTrackPortIndex OBJECT-TYPE
SYNTAX SEQUENCE OF RptrTopNPortControlEntry SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of control records for reports on the top `N' "This object identifies the port within the group
ports for the rate of a selected counter. The number for which this entry contains information."
of entries depends on the configuration of the agent. REFERENCE
The maximum number of entries is implementation "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
dependent." ::= { rptrAddrTrackEntry 2 }
::= { rptrTopNPortInfo 1 }
rptrTopNPortControlEntry OBJECT-TYPE rptrAddrTrackLastSourceAddress OBJECT-TYPE
SYNTAX RptrTopNPortControlEntry SYNTAX MacAddress
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS deprecated
DESCRIPTION DESCRIPTION
"A set of parameters that control the creation of a "********* THIS OBJECT IS DEPRECATED **********
report of the top N ports according to several metrics." This object is the SourceAddress of the last
INDEX { rptrTopNPortControlIndex } readable frame (i.e., counted by
::= { rptrTopNPortControlTable 1 } rptrMonitorPortReadableFrames) received by this
port.
RptrTopNPortControlEntry ::= SEQUENCE { This object has been deprecated because its value
rptrTopNPortControlIndex is undefined when no frames have been observed on
Integer32, this port. The replacement object is
rptrTopNPortRepeaterId rptrAddrTrackNewLastSrcAddress."
Integer32, REFERENCE
rptrTopNPortRateBase "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress."
INTEGER, ::= { rptrAddrTrackEntry 3 }
rptrTopNPortTimeRemaining
Integer32,
rptrTopNPortDuration
Integer32,
rptrTopNPortRequestedSize
Integer32,
rptrTopNPortGrantedSize
Integer32,
rptrTopNPortStartTime
TimeStamp,
rptrTopNPortOwner
OwnerString,
rptrTopNPortRowStatus
RowStatus
}
rptrTopNPortControlIndex OBJECT-TYPE rptrAddrTrackSourceAddrChanges OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This counter is incremented by one for each time
that the rptrAddrTrackLastSourceAddress attribute
for this port has changed.
, This may indicate whether a link is connected to a
SYNTAX Integer32 (1 .. 65535) single DTE or another multi-user segment.
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 A discontinuity may occur in the value when the
SYNTAX Integer32 (0..2147483647) value of object rptrMonitorPortLastChange changes.
MAX-ACCESS read-create
STATUS current
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 The approximate minimum time for rollover of this
associated rptrTopNPortRowStatus object is equal to counter is 81 hours in a 10Mb/s repeater."
active(1). REFERENCE
"[IEEE 802.3 Mgt], 30.4.3.1.19, aSourceAddressChanges."
::= { rptrAddrTrackEntry 4 }
If, for a particular row in this table, the repeater rptrAddrTrackNewLastSrcAddress OBJECT-TYPE
specified by the value of this object goes away (is SYNTAX OptMacAddr
removed from the rptrInfoTable) while the associated MAX-ACCESS read-only
rptrTopNPortRowStatus object is equal to active(1), STATUS current
the row in this table is preserved by the agent but DESCRIPTION
the value of rptrTopNPortRowStatus is changed to "This object is the SourceAddress of the last
notInService(2), and the agent may time out the row readable frame (i.e., counted by
if appropriate. If the specified repeater comes rptrMonitorPortReadableFrames) received by this
back (reappears in the rptrInfoTable) before the row port. If no frames have been received by this
has been timed out, the management station must set port since the agent began monitoring the port
the value of the rptrTopNPortRowStatus object back activity, the agent shall return a string of
to active(1) if desired (the agent doesn't do this length zero."
automatically)." REFERENCE
::= { rptrTopNPortControlEntry 2 } "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress."
rptrTopNPortRateBase OBJECT-TYPE ::= { rptrAddrTrackEntry 5 }
SYNTAX INTEGER {
readableFrames(1),
readableOctets(2),
fcsErrors(3),
, rptrAddrTrackCapacity OBJECT-TYPE
alignmentErrors(4), SYNTAX Integer32
frameTooLongs(5), MAX-ACCESS read-only
shortEvents(6), STATUS current
runts(7), DESCRIPTION
collisions(8), "The maximum number of addresses that can be
lateEvents(9), detected on this port. This value indicates
veryLongEvents(10), to the maximum number of entries in the
dataRateMismatches(11), rptrExtAddrTrackTable relative to this port.
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 If this object has the value of 1, the agent
the associated rptrTopNPortRowStatus object has implements only the LastSourceAddress mechanism
a value of active(1)." described by RFC 1368 or RFC 1516."
::= { rptrTopNPortControlEntry 3 } ::= { rptrAddrTrackEntry 6 }
rptrTopNPortTimeRemaining OBJECT-TYPE -- Table for multiple addresses per port
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of seconds left in the report
currently being collected. When this object
is modified by the management station, a new
collection is started, possibly aborting a
currently running report. The new value is
used as the requested duration of this report,
which is loaded into the associated
rptrTopNPortDuration object.
When this object is set to a non-zero value, rptrExtAddrTrackTable OBJECT-TYPE
any associated rptrTopNPortEntries shall be SYNTAX SEQUENCE OF RptrExtAddrTrackEntry
made inaccessible by the agent. While the value MAX-ACCESS not-accessible
of this object is non-zero, it decrements by one STATUS current
per second until it reaches zero. During this DESCRIPTION
time, all associated rptrTopNPortEntries shall "A table to extend the address tracking table (i.e.,
remain inaccessible. At the time that this object rptrAddrTrackTable) with a list of source MAC
addresses that were recently received on each port.
The number of ports is the same as the number
of entries in table rptrPortTable. The number of
entries in this table depends on the agent/repeater
implementation and the number of different
addresses received on each port.
, The first entry for each port contains
decrements to zero, the report is made accessible the same MAC address that is given by the
in the rptrTopNPortTable. Thus, the rptrTopNPort rptrAddrTrackNewLastSrcAddress for that port.
table needs to be created only at the end of the
collection interval.
If the value of this object is set to zero Entries in this table for a particular port are
while the associated report is running, the retained when that port is switched from one
running report is aborted and no associated repeater to another.
rptrTopNPortEntries are created."
DEFVAL { 0 }
::= { rptrTopNPortControlEntry 4 }
rptrTopNPortDuration OBJECT-TYPE The ordering of MAC addresses listed for a
SYNTAX Integer32 (0..2147483647) particular port is implementation dependent."
MAX-ACCESS read-only ::= { rptrAddrTrackPortInfo 2 }
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,
the number of seconds that this report is being
collected during this sampling interval.
When the associated rptrTopNPortTimeRemaining rptrExtAddrTrackEntry OBJECT-TYPE
object is set, this object shall be set by the SYNTAX RptrExtAddrTrackEntry
agent to the same value and shall not be modified MAX-ACCESS not-accessible
until the next time the rptrTopNPortTimeRemaining STATUS current
is set. DESCRIPTION
"A row in the table of extended address tracking
information for ports. Entries can not be directly
created or deleted via SNMP operations."
INDEX { rptrAddrTrackGroupIndex,
rptrAddrTrackPortIndex,
rptrExtAddrTrackMacIndex }
::= { rptrExtAddrTrackTable 1 }
This value shall be zero if no reports have been RptrExtAddrTrackEntry ::= SEQUENCE {
requested for this rptrTopNPortControlEntry." rptrExtAddrTrackMacIndex Integer32,
::= { rptrTopNPortControlEntry 5 } rptrExtAddrTrackSourceAddress MacAddress
}
rptrTopNPortRequestedSize OBJECT-TYPE rptrExtAddrTrackMacIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of repeater ports requested "The index of a source MAC address seen on
for the Top N Table. the port.
When this object is created or modified, the The ordering of MAC addresses listed for a
agent should set rptrTopNPortGrantedSize as close particular port is implementation dependent.
to this object as is possible for the particular
implementation and available resources."
, 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 }
DEFVAL { 10 } rptrExtAddrTrackSourceAddress OBJECT-TYPE
::= { rptrTopNPortControlEntry 6 } 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 }
rptrTopNPortGrantedSize OBJECT-TYPE -- The Repeater Top "N" Port Group
SYNTAX Integer32 (0..65535) -- The Repeater Top N Port group is used to prepare reports that
MAX-ACCESS read-only -- describe a list of ports ordered by one of the statistics in the
STATUS current -- Repeater Monitor Port Table. The statistic chosen by the
DESCRIPTION -- management station is sampled over a management
"The maximum number of repeater ports in the -- station-specified time interval, making the report rate based.
top N table. -- 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.
When the associated rptrTopNPortRequestedSize object is -- Note that counter discontinuities may appear in some
created or modified, the agent should set this object as -- implementations if ports' assignment to repeaters changes
closely to the requested value as is possible for the -- during the collection of data for a Top "N" report.
particular implementation and available resources. The -- A management application could read the corresponding
agent must not lower this value except as a result of a -- rptrMonitorPortLastChange timestamp in order to check
set to the associated rptrTopNPortRequestedSize object." -- whether a discontinuity occurred.
::= { rptrTopNPortControlEntry 7 }
rptrTopNPortStartTime OBJECT-TYPE rptrTopNPortControlTable OBJECT-TYPE
SYNTAX TimeStamp SYNTAX SEQUENCE OF RptrTopNPortControlEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this top N report was "A table of control records for reports on the top `N'
last started. In other words, this is the time that ports for the rate of a selected counter. The number
the associated rptrTopNPortTimeRemaining object was of entries depends on the configuration of the agent.
modified to start the requested report. The maximum number of entries is implementation
dependent."
::= { rptrTopNPortInfo 1 }
If the report has not yet been started, the value rptrTopNPortControlEntry OBJECT-TYPE
of this object is zero." SYNTAX RptrTopNPortControlEntry
::= { rptrTopNPortControlEntry 8 } MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of parameters that control the creation of a
report of the top N ports according to several metrics."
INDEX { rptrTopNPortControlIndex }
::= { rptrTopNPortControlTable 1 }
rptrTopNPortOwner OBJECT-TYPE RptrTopNPortControlEntry ::= SEQUENCE {
SYNTAX OwnerString rptrTopNPortControlIndex
MAX-ACCESS read-create Integer32,
STATUS current rptrTopNPortRepeaterId
DESCRIPTION Integer32,
"The entity that configured this entry and is rptrTopNPortRateBase
using the resources assigned to it." INTEGER,
::= { rptrTopNPortControlEntry 9 } rptrTopNPortTimeRemaining
Integer32,
rptrTopNPortDuration
Integer32,
rptrTopNPortRequestedSize
Integer32,
rptrTopNPortGrantedSize
Integer32,
rptrTopNPortStartTime
TimeStamp,
rptrTopNPortOwner
OwnerString,
rptrTopNPortRowStatus
RowStatus
}
rptrTopNPortRowStatus OBJECT-TYPE rptrTopNPortControlIndex OBJECT-TYPE
SYNTAX RowStatus SYNTAX Integer32 (1 .. 65535)
MAX-ACCESS read-create 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
STATUS current SYNTAX Integer32 (0..2147483647)
DESCRIPTION MAX-ACCESS read-create
"The status of this row. STATUS current
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.
If the value of this object is not equal to The value of this object may not be modified if the
active(1), all associated entries in the associated rptrTopNPortRowStatus object is equal to
rptrTopNPortTable shall be deleted by the active(1).
agent."
::= { rptrTopNPortControlEntry 10 }
-- Top "N" reports 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 }
rptrTopNPortTable OBJECT-TYPE rptrTopNPortRateBase OBJECT-TYPE
SYNTAX SEQUENCE OF RptrTopNPortEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible readableFrames(1),
STATUS current readableOctets(2),
DESCRIPTION fcsErrors(3),
"A table of reports for the top `N' ports based on alignmentErrors(4),
setting of associated control table entries. The frameTooLongs(5),
maximum number of entries depends on the number shortEvents(6),
of entries in table rptrTopNPortControlTable and runts(7),
the value of object rptrTopNPortGrantedSize for collisions(8),
each entry. 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.
For each entry in the rptrTopNPortControlTable, The value of this object may not be modified if
repeater ports with the highest value of the associated rptrTopNPortRowStatus object has
rptrTopNPortRate shall be placed in this table a value of active(1)."
in decreasing order of that rate until there is ::= { rptrTopNPortControlEntry 3 }
no more room or until there are no more ports."
::= { rptrTopNPortInfo 2 }
rptrTopNPortEntry OBJECT-TYPE rptrTopNPortTimeRemaining OBJECT-TYPE
SYNTAX RptrTopNPortEntry SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of statistics for a repeater port that is "The number of seconds left in the report
part of a top N report." currently being collected. When this object
INDEX { rptrTopNPortControlIndex, is modified by the management station, a new
rptrTopNPortIndex } collection is started, possibly aborting a
::= { rptrTopNPortTable 1 } currently running report. The new value is
used as the requested duration of this report,
which is loaded into the associated
rptrTopNPortDuration object.
RptrTopNPortEntry ::= SEQUENCE { When this object is set to a non-zero value,
rptrTopNPortIndex 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.
, If the value of this object is set to zero
Integer32, while the associated report is running, the
rptrTopNPortGroupIndex running report is aborted and no associated
Integer32, rptrTopNPortEntries are created."
rptrTopNPortPortIndex DEFVAL { 0 }
Integer32, ::= { rptrTopNPortControlEntry 4 }
rptrTopNPortRate
Gauge32
}
rptrTopNPortIndex OBJECT-TYPE rptrTopNPortDuration OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that uniquely identifies an entry in "The number of seconds that this report has
the rptrTopNPort table among those in the same collected during the last sampling interval,
report. This index is between 1 and N, where N or if this report is currently being collected,
is the number of entries in this report. Increasing the number of seconds that this report is being
values of rptrTopNPortIndex shall be assigned to collected during this sampling interval.
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 When the associated rptrTopNPortTimeRemaining
value of rptrTopNPortRate would be zero." object is set, this object shall be set by the
::= { rptrTopNPortEntry 1 } agent to the same value and shall not be modified
until the next time the rptrTopNPortTimeRemaining
is set.
rptrTopNPortGroupIndex OBJECT-TYPE This value shall be zero if no reports have been
SYNTAX Integer32 (1..2147483647) requested for this rptrTopNPortControlEntry."
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifes the group containing
the port for this entry. (See also object
type rptrGroupIndex.)"
::= { rptrTopNPortEntry 2 }
rptrTopNPortPortIndex OBJECT-TYPE ::= { rptrTopNPortControlEntry 5 }
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index of the repeater port.
(See object type rptrPortIndex.)"
, rptrTopNPortRequestedSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum number of repeater ports requested
for the Top N Table.
::= { rptrTopNPortEntry 3 } 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 }
rptrTopNPortRate OBJECT-TYPE rptrTopNPortGrantedSize OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of change in the selected variable "The maximum number of repeater ports in the
during this sampling interval for the identified top N table.
port. The selected variable is that port's
instance of the object selected by
rptrTopNPortRateBase."
::= { rptrTopNPortEntry 4 }
-- Notifications for use by Repeaters 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 }
rptrHealth NOTIFICATION-TYPE rptrTopNPortStartTime OBJECT-TYPE
OBJECTS { rptrOperStatus } SYNTAX TimeStamp
STATUS deprecated MAX-ACCESS read-only
DESCRIPTION STATUS current
"********* THIS OBJECT IS DEPRECATED ********** 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.
In a system containing a single managed repeater, If the report has not yet been started, the value
the rptrHealth notification conveys information of this object is zero."
related to the operational status of the repeater. ::= { rptrTopNPortControlEntry 8 }
It is sent either when the value of
rptrOperStatus changes, or upon completion of a
non-disruptive test.
The rptrHealth notification must contain the rptrTopNPortOwner OBJECT-TYPE
rptrOperStatus object. The agent may optionally SYNTAX OwnerString
include the rptrHealthText object in the varBind MAX-ACCESS read-create
list. See the rptrOperStatus and rptrHealthText STATUS current
objects for descriptions of the information that DESCRIPTION
is sent. "The entity that configured this entry and is
using the resources assigned to it."
::= { rptrTopNPortControlEntry 9 }
The agent must throttle the generation of rptrTopNPortRowStatus OBJECT-TYPE
consecutive rptrHealth traps so that there is at SYNTAX RowStatus
least a five-second gap between traps of this MAX-ACCESS read-create
type. When traps are throttled, they are dropped, STATUS current
not queued for sending at a future time. (Note DESCRIPTION
that 'generating' a trap means sending to all "The status of this row.
configured recipients.)"
, 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 }
REFERENCE -- Top "N" reports
"[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth
notification."
::= { snmpDot3RptrMgt 0 1 }
rptrGroupChange NOTIFICATION-TYPE rptrTopNPortTable OBJECT-TYPE
OBJECTS { rptrGroupIndex } SYNTAX SEQUENCE OF RptrTopNPortEntry
STATUS deprecated MAX-ACCESS not-accessible
DESCRIPTION STATUS current
"********* THIS OBJECT IS DEPRECATED ********** 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.
In a system containing a single managed repeater, For each entry in the rptrTopNPortControlTable,
this notification is sent when a change occurs in the repeater ports with the highest value of
group structure of the repeater. This occurs only rptrTopNPortRate shall be placed in this table
when a group is logically or physically removed in decreasing order of that rate until there is
from or added to a repeater. The varBind list no more room or until there are no more ports."
contains the identifier of the group that was ::= { rptrTopNPortInfo 2 }
removed or added.
The agent must throttle the generation of rptrTopNPortEntry OBJECT-TYPE
consecutive rptrGroupChange traps for the same SYNTAX RptrTopNPortEntry
group so that there is at least a five-second gap MAX-ACCESS not-accessible
between traps of this type. When traps are STATUS current
throttled, they are dropped, not queued for DESCRIPTION
sending at a future time. (Note that 'generating' "A set of statistics for a repeater port that is
a trap means sending to all configured part of a top N report."
recipients.)" INDEX { rptrTopNPortControlIndex,
REFERENCE rptrTopNPortIndex }
"[IEEE 802.3 Mgt], 30.4.1.3.3, nGroupMapChange ::= { rptrTopNPortTable 1 }
notification."
::= { snmpDot3RptrMgt 0 2 }
rptrResetEvent NOTIFICATION-TYPE RptrTopNPortEntry ::= SEQUENCE {
OBJECTS { rptrOperStatus } rptrTopNPortIndex
STATUS deprecated Integer32,
DESCRIPTION rptrTopNPortGroupIndex
"********* THIS OBJECT IS DEPRECATED ********** Integer32,
rptrTopNPortPortIndex
Integer32,
rptrTopNPortRate
Gauge32
}
In a system containing a single managed repeater-unit, rptrTopNPortIndex OBJECT-TYPE
the rptrResetEvent notification conveys information SYNTAX Integer32 (1..65535)
related to the operational status of the repeater. MAX-ACCESS read-only
This trap is sent on completion of a repeater STATUS current
reset action. A repeater reset action is defined DESCRIPTION
as an a transition