As per Relevance of the word february, we have this rfc below:
Network Working Group K. de
Request for Comments: 2108 3Com
Obsoletes: 1516 D.
Category: Standards Track Madge Networks (Israel) Ltd
D.
Coloma
K.
Cisco Systems Inc
February 1997
Definitions of Managed
for IEEE 802.3 Repeater
using SMIv
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
This memo defines a 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.
Table of
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
de Graaf, et. al. Standards Track [Page 1]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
4. Topology Mapping......................................... 75
5. Acknowledgements......................................... 79
6. References............................................... 80
7. Security Considerations.................................. 81
8. Authors' Addresses....................................... 81
1. The SNMP Network Management
The SNMP Network Management Framework presently consists of
major components. They are
o the SMI, described in RFC 1902 [6] - the mechanisms
for describing and naming objects for the purpose
management
o the MIB-II, STD 17, RFC 1213 [5] - the core set
managed objects for the Internet suite of protocols
o the protocol, STD 15, RFC 1157 [10] and/or RFC 1905
[9] - the protocol used for accessing managed information
Textual conventions are defined in RFC 1903 [7], and
statements are defined in RFC 1904 [8].
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
1.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation one (ASN.1)
defined in the SMI. In particular, each object type is named by
OBJECT IDENTIFIER, an administratively assigned name. The
type together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience,
often use a textual string, termed the descriptor, to refer to
object type
2.
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
objects contained in that MIB, plus several new ones which
de Graaf, et. al. Standards Track [Page 2]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
for significant additional capabilities. Implementors are
to support all applicable conformance groups in order to make
best use of the new functionality provided by this MIB. The
objects provide support for
o multiple
o 100BASE-T
o port TopN
o address search and topology
Certain objects have been deprecated; in particular, those
objects used for managing a single repeater are now of minimal
since they are duplicated in the new multiple- repeater definitions
Additional objects have been deprecated based on
experience with RFC 1516.
2.2. Repeater
Instances of the object types defined in this memo
attributes of an IEEE 802.3 (Ethernet-like) repeater, as defined
Section 9, "Repeater Unit for 10 Mb/s Baseband Networks" in the
802.3/ISO 8802-3 CSMA/CD standard [1], and Section 27, "Repeater
100 Mb/s Baseband Networks" in the IEEE Standard 802.3u-1995 [2].
These Repeater MIB objects may be used to manage non-
repeater-like devices, but defining objects to
implementation-specific properties of non-standard repeater-
devices is outside the scope of this memo
The definitions presented here are based on Section 30.4, "
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]
describes when, where, and how various repeater attributes
measured. The IEEE document also describes the effects of
actions that may be invoked by manipulating instances of the
objects defined here
The counters in this document are defined to be the same as
counters in [3], with the intention that the same instrumentation
be used to implement both the IEEE and IETF management standards
de Graaf, et. al. Standards Track [Page 3]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
2.3. Structure of the
Objects in this MIB are arranged into packages, each of
contains a set of related objects within a broad functional category
Objects within a package are generally defined under the same
subtree. These packages are intended for organizational
ONLY, and have no relation to the conformance groups defined later
the document
2.3.1. Basic
The basic definitions include objects which are applicable to
repeaters: status, parameter and control objects for each
within the managed system, for the port groups within the system,
for the individual ports themselves
2.3.2. Monitor
The monitor definitions include monitoring statistics for
repeater within the system and for individual ports
2.3.3. Address Tracking
This collection includes objects for tracking the MAC addresses
the DTEs attached to the ports within the system and for mapping
topology of a network
Note: These definitions are based on a technology which has
patented by Hewlett-Packard Company. HP has granted rights to
technology to implementors of this MIB. See [12] and [13]
details
2.3.4. Top N
These objects may be used for tracking the ports with the
activity within the system or within particular repeaters
2.4. Relationship to Other
2.4.1. Relationship to MIB-
It is assumed that a repeater implementing this MIB will
implement (at least) the 'system' group defined in MIB-II [5].
de Graaf, et. al. Standards Track [Page 4]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
2.4.1.1. Relationship to the 'system'
In MIB-II, the 'system' group is defined as being mandatory for
systems such that each managed entity contains one instance of
object in the 'system' group. Thus, those objects apply to
entity even if the entity's sole functionality is management
repeaters
2.4.1.2. Relationship to the 'interfaces'
In MIB-II, the 'interfaces' group is defined as being mandatory
all systems and contains information on an entity's interfaces,
each interface is thought of as being attached to a 'subnetwork'.
(Note that this term is not to be confused with 'subnet' which
to an addressing partitioning scheme used in the Internet suite
protocols.)
This Repeater MIB uses the notion of ports on a repeater.
concept of a MIB-II interface has NO specific relationship to
repeater's port. Therefore, the 'interfaces' group applies only
the one (or more) network interfaces on which the entity managing
repeater sends and receives management protocol operations, and
not apply to the repeater's ports
This is consistent with the physical-layer nature of a repeater.
repeater is a bitwise store-and-forward device. It
activity and bits, but does not process incoming data based on
packet-related information (such as checksum or addresses).
repeater has no MAC address, no MAC implementation, and does not
packets up to higher-level protocol entities for processing
(When a network management entity is observing a repeater, it
appear as though the repeater is passing packets to a higher-
protocol entity. However, this is only a means of
management, and this passing of management information is not part
the repeater functionality.)
de Graaf, et. al. Standards Track [Page 5]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
3.
SNMP-REPEATER-MIB DEFINITIONS ::=
Counter32, Counter64, Integer32, Gauge32, TimeTicks
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2
FROM SNMPv2-
TimeStamp, DisplayString, MacAddress, TEXTUAL-CONVENTION
RowStatus,
FROM SNMPv2-
OBJECT-GROUP, MODULE-
FROM SNMPv2-
FROM IF-MIB
snmpRptrMod MODULE-
LAST-UPDATED "9609140000Z
ORGANIZATION "IETF HUB MIB Working Group
CONTACT-
"WG E-mail: hubmib@hprnd.rose.hp.
Chair: Dan
Postal: Madge Networks (Israel) Ltd
Atidim Technology Park, Bldg. 3
Tel Aviv 61131,
Tel: 972-3-6458414, 6458458
Fax: 972-3-6487146
E-mail: dromasca@madge.
Editor: Kathryn de
Postal: 3Com
118 Turnpike Rd
Southborough, MA 01772
Tel: (508)229-1627
Fax: (508)490-5882
E-mail: kdegraaf@isd.3com.com
"Management information for 802.3 repeaters
The following references are used
this MIB module
[IEEE 802.3 Std
refers to IEEE 802.3/ISO 8802-3
processing systems - Local area networks -
Part 3: Carrier sense multiple access
de Graaf, et. al. Standards Track [Page 6]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
collision detection (CSMA/CD) access
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
MIB module. For complete formal definitions
the IEEE 802.3 standards should be
wherever possible
System - A managed entity compliant with
MIB, and incorporating at least one
802.3 repeater
Chassis - An enclosure for one managed repeater
part of a managed repeater, or several
repeaters. It typically contains an
power supply and a variable number of
module slots
Repeater-unit - The portion of the repeater
that is inboard of the physical media interfaces
The physical media interfaces (MAUs, AUIs) may
physically separated from the repeater-unit,
they may be integrated into the same
package
Trivial repeater-unit - An isolated port that
gather statistics
Group - A recommended, but optional,
defined by the IEEE 802.3 management standard
in order to support a modular numbering scheme
The classical example allows an implementor
represent field-replaceable units as groups
ports, with the port numbering matching
modular hardware implementation
System interconnect segment - An
segment allowing interconnection of
belonging to different physical
into the same logical manageable repeater
Examples of implementation might
backplane busses in modular hubs,
chaining cables in stacks of hubs
de Graaf, et. al. Standards Track [Page 7]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
Stack - A scalable system that may
managed repeaters, in which modularity
achieved by interconnecting a number
different chassis
Module - A building block in a
chassis. It typically maps into one 'slot';
however, the range of configurations may
very large, with several modules
one slot, or one module covering
slots
"
REVISION "9309010000Z
"Published as RFC 1516"
REVISION "9210010000Z
"Published as RFC 1368"
::= { snmpDot3RptrMgt 5 }
snmpDot3RptrMgt OBJECT IDENTIFIER ::= { mib-2 22 }
OptMacAddr ::= TEXTUAL-
DISPLAY-HINT "1x:"
STATUS
"Either a 6 octet address in the `canonical
order defined by IEEE 802.1a, i.e., as if
were transmitted least significant bit
if a value is available or a zero length string."
"See MacAddress in SNMPv2-TC. The only
is that a zero length string is allowed as a
for OptMacAddr and not for MacAddress."
SYNTAX OCTET STRING (SIZE (0 | 6))
-- Basic information at the repeater, group, and port level
OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 1 }
OBJECT IDENTIFIER ::= { rptrBasicPackage 1 }
de Graaf, et. al. Standards Track [Page 8]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
OBJECT IDENTIFIER ::= { rptrBasicPackage 2 }
OBJECT IDENTIFIER ::= { rptrBasicPackage 3 }
OBJECT IDENTIFIER ::= { rptrBasicPackage 4 }
-- Monitoring information at the repeater, group, and port level
OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 2 }
OBJECT IDENTIFIER ::= { rptrMonitorPackage 1 }
OBJECT IDENTIFIER ::= { rptrMonitorPackage 2 }
OBJECT IDENTIFIER ::= { rptrMonitorPackage 3 }
OBJECT IDENTIFIER ::= { rptrMonitorPackage 4 }
-- Address tracking information at the repeater, group
-- and port level
OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 3 }
OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 1 }
-- this subtree is currently
OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 2 }
OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 3 }
-- TopN information
OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 4 }
-- this subtree is currently
OBJECT IDENTIFIER ::= { rptrTopNPackage 1 }
-- this subtree is currently
OBJECT IDENTIFIER ::= { rptrTopNPackage 2 }
OBJECT IDENTIFIER ::= { rptrTopNPackage 3 }
-- Old version of basic information at the repeater level
--
-- In a system containing a single managed repeater
-- configuration, status, and control objects for the
-- repeater
de Graaf, et. al. Standards Track [Page 9]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
--
-- The objects contained under the rptrRptrInfo subtree
-- intended for backwards compatibility with implementations
-- RFC 1516 [11]. In newer implementations (both single-
-- multiple-repeater implementations) the rptrInfoTable
-- be implemented. It is the preferred source of this information
-- as it contains the values for all repeaters managed by
-- agent. In all cases, the objects in the rptrRptrInfo
-- are duplicates of the corresponding objects in the first
-- of the rptrInfoTable
rptrGroupCapacity OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
The rptrGroupCapacity is the number of
that can be contained within the repeater.
each managed repeater, the groups are
numbered in the range from 1 to rptrGroupCapacity
Some groups may not be present in the repeater,
which case the actual number of groups
will be less than rptrGroupCapacity. The
of groups present will never be greater
rptrGroupCapacity
Note: In practice, this will generally be
number of field-replaceable units (i.e., modules
cards, or boards) that can fit in the
repeater enclosure, and the group numbers
correspond to numbers marked on the
enclosure."
"[IEEE 802.3 Mgt], 30.4.1.1.3,
aRepeaterGroupCapacity."
::= { rptrRptrInfo 1 }
rptrOperStatus OBJECT-
SYNTAX INTEGER {
other(1), -- undefined or
ok(2), -- no known
rptrFailure(3), -- repeater-related
groupFailure(4), -- group-related
portFailure(5), -- port-related
generalFailure(6) -- failure, unspecified
de Graaf, et. al. Standards Track [Page 10]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
}
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
The rptrOperStatus object indicates
operational state of the repeater.
rptrHealthText object may be consulted for
specific information about the state of
repeater's health
In the case of multiple kinds of failures (e.g.,
repeater failure and port failure), the value
this attribute shall reflect the highest
failure in the following order, listed
priority first
rptrFailure(3)
groupFailure(4)
portFailure(5)
generalFailure(6)."
"[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
::= { rptrRptrInfo 2 }
rptrHealthText OBJECT-
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
The health text object is a text string
provides information relevant to the
state of the repeater. Agents may use this
to provide detailed information on
failures, including how they were detected, and/
instructions for problem resolution. The
are agent-specific."
"[IEEE 802.3 Mgt], 30.4.1.1.6, aRepeaterHealthText."
::= { rptrRptrInfo 3 }
rptrReset OBJECT-
SYNTAX INTEGER {
noReset(1),
reset(2)
de Graaf, et. al. Standards Track [Page 11]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
}
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
Setting this object to reset(2) causes
transition to the START state of Fig 9-2
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
Setting this object to noReset(1) has no effect
The agent will always return the value noReset(1)
when this object is read
After receiving a request to set this variable
reset(2), the agent is allowed to delay the
for a short period. For example, the
may choose to delay the reset long enough to
the SNMP response to be transmitted. In
event, the SNMP response must be transmitted
This action does not reset the management
defined in this document nor does it affect
portAdminStatus parameters. Included in
action is the execution of a disruptive Self-
with the following characteristics: a) The
of the tests is not specified. b) The test
the repeater but without affecting
information about the repeater. c) The test
not inject packets onto any segment. d)
received during the test may or may not
transferred. e) The test does not interfere
management functions
After performing this self-test, the agent
update the repeater health information (
rptrOperStatus and rptrHealthText), and send
rptrHealth trap."
"[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
::= { rptrRptrInfo 4 }
rptrNonDisruptTest OBJECT-
SYNTAX INTEGER {
noSelfTest(1),
selfTest(2)
de Graaf, et. al. Standards Track [Page 12]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
}
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
Setting this object to selfTest(2) causes
repeater to perform a agent-specific, non
disruptive self-test that has the
characteristics: a) The nature of the tests
not specified. b) The test does not change
state of the repeater or management
about the repeater. c) The test does not
packets onto any segment. d) The test does
prevent the relay of any packets. e) The
does not interfere with management functions
After performing this test, the agent will
the repeater health information (
rptrOperStatus and rptrHealthText) and send
rptrHealth trap
Note that this definition allows returning
'okay' result after doing a trivial test
Setting this object to noSelfTest(1) has
effect. The agent will always return the
noSelfTest(1) when this object is read."
"[IEEE 802.3 Mgt], 30.4.1.2.2,
acExecuteNonDisruptiveSelfTest."
::= { rptrRptrInfo 5 }
rptrTotalPartitionedPorts OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
This object returns the total number of ports
the repeater whose current state meets all
of the following criteria:
does not have the value notPresent(3),
rptrPortAdminStatus is enabled(1),
rptrPortAutoPartitionState is autoPartitioned(2)."
::= { rptrRptrInfo 6 }
de Graaf, et. al. Standards Track [Page 13]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
-- Basic information at the group level
--
-- Configuration and status objects for
-- managed group in the system,
-- of whether there is one or more
-- repeater-units in the system
rptrGroupTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Table of descriptive and status information
the groups of ports."
::= { rptrGroupInfo 1 }
rptrGroupEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the table, containing
about a single group of ports."
INDEX { rptrGroupIndex }
::= { rptrGroupTable 1 }
RptrGroupEntry ::=
SEQUENCE {
Integer32,
DisplayString
OBJECT IDENTIFIER
INTEGER
TimeTicks
Integer32
}
rptrGroupIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This object identifies the group within
de Graaf, et. al. Standards Track [Page 14]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
system for which this entry
information."
"[IEEE 802.3 Mgt], 30.4.2.1.1, aGroupID."
::= { rptrGroupEntry 1 }
rptrGroupDescr OBJECT-
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
A textual description of the group. This
should include the full name and
identification of the group's hardware type
indicate how the group is differentiated
other types of groups in the repeater. Plug-
Module, Rev A' or 'Barney Rubble 10BASE-T 4-
SIMM socket Version 2.1' are examples of
group descriptions
It is mandatory that this only contain
ASCII characters."
::= { rptrGroupEntry 2 }
rptrGroupObjectID OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"The vendor's authoritative identification of
group. This value may be allocated within the
enterprises subtree (1.3.6.1.4.1) and provides
straight-forward and unambiguous means
determining what kind of group is being managed
For example, this object could take the
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
1.3.6.1.4.1.4242.1.2.14 to its 'Wilma
6-Port FOIRL Plug-in Module.'"
::= { rptrGroupEntry 3 }
rptrGroupOperStatus OBJECT-
SYNTAX INTEGER {
other(1),
de Graaf, et. al. Standards Track [Page 15]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
operational(2),
malfunctioning(3),
notPresent(4),
underTest(5),
resetInProgress(6)
}
MAX-ACCESS read-
STATUS
"An object that indicates the operational
of the group
A status of notPresent(4) indicates that the
is temporarily or permanently physically and/
logically not a part of the repeater. It is
implementation-specific matter as to whether
agent effectively removes notPresent entries
the table
A status of operational(2) indicates that
group is functioning, and a status
malfunctioning(3) indicates that the group
malfunctioning in some way."
::= { rptrGroupEntry 4 }
rptrGroupLastOperStatusChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
An object that contains the value of sysUpTime
the time when the last of the following occurred
1) the agent cold- or warm-started
2) the row for the group was created (
as when the group was added to the system);
3) the value of rptrGroupOperStatus for
group changed
A value of zero indicates that the group'
operational status has not changed since the
last restarted."
::= { rptrGroupEntry 5 }
rptrGroupPortCapacity OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
de Graaf, et. al. Standards Track [Page 16]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
STATUS
"The rptrGroupPortCapacity is the number of
that can be contained within the group.
range is 1-2147483647. Within each group,
ports are uniquely numbered in the range from 1
rptrGroupPortCapacity
Some ports may not be present in the system,
which case the actual number of ports
will be less than the value of rptrGroupPortCapacity
The number of ports present in the group will
be greater than the value of rptrGroupPortCapacity
Note: In practice, this will generally be
number of ports on a module, card, or board,
the port numbers will correspond to numbers
on the physical embodiment."
"IEEE 802.3 Mgt, 30.4.2.1.2, aGroupPortCapacity."
::= { rptrGroupEntry 6 }
-- Basic information at the port level
--
-- Configuration and status objects
-- each managed repeater port in the system
-- independent of whether there is one or
-- managed repeater-units in the system
rptrPortTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Table of descriptive and status information
the repeater ports in the system. The number
entries is independent of the number of
in the managed system."
::= { rptrPortInfo 1 }
rptrPortEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the table, containing
about a single port."
de Graaf, et. al. Standards Track [Page 17]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
INDEX { rptrPortGroupIndex, rptrPortIndex }
::= { rptrPortTable 1 }
RptrPortEntry ::=
SEQUENCE {
Integer32,
Integer32,
INTEGER
INTEGER
INTEGER
Integer32
}
rptrPortGroupIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This object identifies the group containing
port for which this entry contains information."
::= { rptrPortEntry 1 }
rptrPortIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This object identifies the port within the
for which this entry contains information.
identifies the port independently from the
it may be attached to. The numbering scheme
ports is implementation specific; however,
value can never be greater
rptrGroupPortCapacity for the associated group."
"[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
::= { rptrPortEntry 2 }
rptrPortAdminStatus OBJECT-
SYNTAX INTEGER {
enabled(1),
disabled(2)
de Graaf, et. al. Standards Track [Page 18]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
}
MAX-ACCESS read-
STATUS
"Setting this object to disabled(2) disables
port. A disabled port neither transmits
receives. Once disabled, a port must
explicitly enabled to restore operation. A
which is disabled when power is lost or when
reset is exerted shall remain disabled when
operation resumes
The admin status takes precedence over auto
partition and functionally operates between
auto-partition mechanism and the AUI/PMA
Setting this object to enabled(1) enables the
and exerts a BEGIN on the port's auto-
state machine
(In effect, when a port is disabled, the value
rptrPortAutoPartitionState for that port is
until the port is next enabled. When the
becomes enabled, the
becomes notAutoPartitioned(1), regardless of
pre-disabling state.)"
"[IEEE 802.3 Mgt], 30.4.3.1.2,
and 30.4.3.2.1, acPortAdminControl."
::= { rptrPortEntry 3 }
rptrPortAutoPartitionState OBJECT-
SYNTAX INTEGER {
notAutoPartitioned(1),
autoPartitioned(2)
}
MAX-ACCESS read-
STATUS
"The autoPartitionState flag indicates whether
port is currently partitioned by the repeater'
auto-partition protection
The conditions that cause port partitioning
specified in partition state machine in
9 and 27 of [IEEE 802.3 Std]. They are
differentiated here."
de Graaf, et. al. Standards Track [Page 19]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
"[IEEE 802.3 Mgt], 30.4.3.1.3, aAutoPartitionState."
::= { rptrPortEntry 4 }
rptrPortOperStatus OBJECT-
SYNTAX INTEGER {
operational(1),
notOperational(2),
notPresent(3)
}
MAX-ACCESS read-
STATUS
"This object indicates the port's
status. The notPresent(3) status indicates
port is physically removed (note this may or
not be possible depending on the type of port.)
The operational(1) status indicates that the
is enabled (see rptrPortAdminStatus) and working
even though it might be auto-partitioned (
rptrPortAutoPartitionState).
If this object has the value operational(1)
rptrPortAdminStatus is set to disabled(2), it
expected that this object's value will soon
to notOperational(2)."
::= { rptrPortEntry 5 }
rptrPortRptrId OBJECT-
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-
STATUS
"This object identifies the repeater
which this port belongs. The
identified by a particular value of this
is the same as that identified by the
value of rptrInfoId. A value of
indicates that this port currently is
a member of any repeater."
::= { rptrPortEntry 6 }
-- New version of basic information at the repeater level
--
-- Configuration, status, and control objects
-- each managed repeater in the system
rptrInfoTable OBJECT-
de Graaf, et. al. Standards Track [Page 20]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table of information about
non-trivial repeater. The number of
depends on the physical configuration of
managed system."
::= { rptrAllRptrInfo 1 }
rptrInfoEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the table, containing
about a single non-trivial repeater."
INDEX { rptrInfoId }
::= { rptrInfoTable 1 }
RptrInfoEntry ::=
SEQUENCE {
Integer32,
INTEGER
INTEGER
INTEGER
Gauge32,
}
rptrInfoId OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This object identifies the repeater for
this entry contains information."
::= { rptrInfoEntry 1 }
rptrInfoRptrType OBJECT-
SYNTAX INTEGER {
other(1), -- undefined or
de Graaf, et. al. Standards Track [Page 21]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
tenMb(2),
onehundredMbClassI(3),
onehundredMbClassII(4)
}
MAX-ACCESS read-
STATUS
"The rptrInfoRptrType returns a value that
the CSMA/CD repeater type."
"[IEEE 802.3 Mgt], 30.4.1.1.2, aRepeaterType."
::= { rptrInfoEntry 2 }
rptrInfoOperStatus OBJECT-
SYNTAX INTEGER {
other(1),
ok(2),
failure(3)
}
MAX-ACCESS read-
STATUS
"The rptrInfoOperStatus object indicates
operational state of the repeater."
"[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
::= { rptrInfoEntry 3 }
rptrInfoReset OBJECT-
SYNTAX INTEGER {
noReset(1),
reset(2)
}
MAX-ACCESS read-
STATUS
"Setting this object to reset(2) causes
transition to the START state of Fig 9-2
section 9 [IEEE 802.3 Std] for a 10Mb/s repeater
and to the START state of Fig 27-2 in section 27
of that standard for a 100Mb/s repeater
Setting this object to noReset(1) has no effect
The agent will always return the value noReset(1)
when this object is read
After receiving a request to set this variable
reset(2), the agent is allowed to delay the
de Graaf, et. al. Standards Track [Page 22]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
for a short period. For example, the
may choose to delay the reset long enough to
the SNMP response to be transmitted. In
event, the SNMP response must be transmitted
This action does not reset the management
defined in this document nor does it affect
portAdminStatus parameters. Included in
action is the execution of a disruptive Self-
with the following characteristics: a) The
of the tests is not specified. b) The test
the repeater but without affecting
information about the repeater. c) The test
not inject packets onto any segment. d)
received during the test may or may not
transferred. e) The test does not interfere
management functions
After performing this self-test, the agent
update the repeater health information (
rptrInfoOperStatus), and send a
notification."
"[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
::= { rptrInfoEntry 4 }
rptrInfoPartitionedPorts OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"This object returns the total number of ports
the repeater whose current state meets all
of the following criteria:
does not have the value notPresent(3),
rptrPortAdminStatus is enabled(1),
rptrPortAutoPartitionState is autoPartitioned(2)."
::= { rptrInfoEntry 5 }
rptrInfoLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime when any of the
conditions occurred
1) agent cold- or warm-started
2) this instance of repeater was
de Graaf, et. al. Standards Track [Page 23]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
(such as when a device or module
added to the system);
3) a change in the value of rptrInfoOperStatus
4) ports were added or removed as members
the repeater;
5) any of the counters associated with
repeater had a discontinuity."
::= { rptrInfoEntry 6 }
--
-- Old version of statistics at the repeater level
--
-- Performance monitoring statistics for the
--
-- In a system containing a single managed repeater-unit
-- the statistics object for the repeater-unit
-- The objects contained under the rptrMonitorRptrInfo subtree
-- intended for backwards compatibility with implementations
-- RFC 1516 [11]. In newer implementations (both single-
-- multiple-repeater implementations), the rptrMonitorTable
-- be implemented. It is the preferred source of this information
-- as it contains the values for all repeaters managed by
-- agent. In all cases, the objects in the
-- subtree are duplicates of the corresponding objects in
-- first entry of the rptrMonitorTable
rptrMonitorTransmitCollisions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
For a clause 9 (10Mb/s) repeater, this
is incremented every time the repeater
machine enters the TRANSMIT COLLISION
from any state other than ONE PORT
(Ref: Fig 9-2 [IEEE 802.3 Std]).
For a clause 27 repeater, this counter
incremented every time the repeater core
diagram enters the Jam state as a result
Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]).
de Graaf, et. al. Standards Track [Page 24]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
The approximate minimum time for rollover of
counter is 16 hours in a 10Mb/s repeater and 1.6
hours in a 100Mb/s repeater."
"[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions."
::= { rptrMonitorRptrInfo 1 }
-- Statistics at the group level
--
-- In a system containing a single managed repeater-unit
-- the statistics objects for each group
rptrMonitorGroupTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
Table of performance and error statistics for
groups within the repeater. The number of
is the same as that in the rptrGroupTable."
::= { rptrMonitorGroupInfo 1 }
rptrMonitorGroupEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
An entry in the table, containing
performance and error statistics for a
group. Regular retrieval of the information
this table provides a means of tracking
performance and health of the networked
attached to this group's ports
The counters in this table are redundant in
sense that they are the summations of
already available through other objects. However
these sums provide a considerable optimization
network management traffic over the
necessary retrieval of the individual
included in each sum
Note: Group-level counters
de Graaf, et. al. Standards Track [Page 25]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
deprecated in this MIB. It is
that management applications instead
the repeater-level counters contained
the rptrMonTable."
INDEX { rptrMonitorGroupIndex }
::= { rptrMonitorGroupTable 1 }
RptrMonitorGroupEntry ::=
SEQUENCE {
Integer32,
Counter32,
Counter32,
Counter32
}
rptrMonitorGroupIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
This object identifies the group within
repeater for which this entry
information."
::= { rptrMonitorGroupEntry 1 }
rptrMonitorGroupTotalFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
The total number of frames of valid frame
that have been received on the ports in this
and for which the FCSError and
signals were not asserted. This counter is
summation of the values of
rptrMonitorPortReadableFrames counters for all
the ports in the group
This statistic provides one of the
necessary for obtaining the packet error rate
de Graaf, et. al. Standards Track [Page 26]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
The approximate minimum time for rollover of
counter is 80 hours in a 10Mb/s repeater."
::= { rptrMonitorGroupEntry 2 }
rptrMonitorGroupTotalOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
The total number of octets contained in the
frames that have been received on the ports
this group. This counter is the summation of
values of the
counters for all of the ports in the group
This statistic provides an indicator of the
data transferred. The approximate minimum
for rollover of this counter is 58 minutes in
10Mb/s repeater."
::= { rptrMonitorGroupEntry 3 }
rptrMonitorGroupTotalErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"********* THIS OBJECT IS DEPRECATED **********
The total number of errors which have occurred
all of the ports in this group. This counter
the summation of the values of
rptrMonitorPortTotalErrors counters for all of
ports in the group."
::= { rptrMonitorGroupEntry 4 }
-- Statistics at the port level
--
rptrMonitorPortTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Table of performance and error statistics for
ports. The number of entries is the same as
de Graaf, et. al. Standards Track [Page 27]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
in the rptrPortTable
The columnar object
is used to indicate possible
of counter type columnar objects in the table."
::= { rptrMonitorPortInfo 1 }
rptrMonitorPortEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the table, containing performance
error statistics for a single port."
INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
::= { rptrMonitorPortTable 1 }
RptrMonitorPortEntry ::=
SEQUENCE {
Integer32,
Integer32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
de Graaf, et. al. Standards Track [Page 28]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
Counter32,
}
rptrMonitorPortGroupIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This object identifies the group containing
port for which this entry contains information."
::= { rptrMonitorPortEntry 1 }
rptrMonitorPortIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This object identifies the port within the
for which this entry contains information."
"[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
::= { rptrMonitorPortEntry 2 }
rptrMonitorPortReadableFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This object is the number of frames of
frame length that have been received on this port
This counter is incremented by one for each
received on this port whose OctetCount is
than or equal to minFrameSize and less than
equal to maxFrameSize (Ref: IEEE 802.3 Std
4.4.2.1) and for which the FCSError
CollisionEvent signals are not asserted
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
This statistic provides one of the
necessary for obtaining the packet error rate
The approximate minimum time for rollover of
counter is 80 hours at 10Mb/s."
de Graaf, et. al. Standards Track [Page 29]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
"[IEEE 802.3 Mgt], 30.4.3.1.4, aReadableFrames."
::= { rptrMonitorPortEntry 3 }
rptrMonitorPortReadableOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This object is the number of octets contained
valid frames that have been received on this port
This counter is incremented by OctetCount for
frame received on this port which has
determined to be a readable frame (i.e.,
FCS octets but excluding framing bits and
bits).
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
This statistic provides an indicator of the
data transferred. The approximate minimum
for rollover of this counter in a 10Mb/s
is 58 minutes
For ports receiving traffic at a maximum rate
a 100Mb/s repeater, this counter can roll
in less than 6 minutes. Since that amount of
could be less than a management station's poll
time, in order to avoid a loss of information
management station is advised to also poll
rptrMonitorPortUpper32Octets object, or to use
64-bit counter defined
rptrMonitorPortHCReadableOctets instead of
two 32-bit counters."
"[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets."
::= { rptrMonitorPortEntry 4 }
rptrMonitorPortFCSErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This counter is incremented by one for each
received on this port with the FCSError
asserted and the FramingError and
signals deasserted and whose OctetCount is
de Graaf, et. al. Standards Track [Page 30]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
than or equal to minFrameSize and less than
equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3
Std).
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
The approximate minimum time for rollover of
counter is 80 hours at 10Mb/s."
"[IEEE 802.3 Mgt], 30.4.3.1.6,
aFrameCheckSequenceErrors."
::= { rptrMonitorPortEntry 5 }
rptrMonitorPortAlignmentErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This counter is incremented by one for each
received on this port with the FCSError
FramingError signals asserted and
signal deasserted and whose OctetCount is
than or equal to minFrameSize and less than
equal to maxFrameSize (Ref: IEEE 802.3 Std
4.4.2.1). If rptrMonitorPortAlignmentErrors
incremented then the
Counter shall not be incremented for the
frame
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
The approximate minimum time for rollover of
counter is 80 hours at 10Mb/s."
"[IEEE 802.3 Mgt], 30.4.3.1.7, aAlignmentErrors."
::= { rptrMonitorPortEntry 6 }
rptrMonitorPortFrameTooLongs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This counter is incremented by one for each
received on this port whose OctetCount is
de Graaf, et. al. Standards Track [Page 31]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std).
If rptrMonitorPortFrameTooLongs is
then neither the
nor the rptrMonitorPortFCSErrors counter shall
incremented for the frame
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
The approximate minimum time for rollover of
counter is 61 days in a 10Mb/s repeater."
"[IEEE 802.3 Mgt], 30.4.3.1.8, aFramesTooLong."
::= { rptrMonitorPortEntry 7 }
rptrMonitorPortShortEvents OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This counter is incremented by one for
CarrierEvent on this port with
less than ShortEventMaxTime. ShortEventMaxTime
greater than 74 bit times and less than 82
times. ShortEventMaxTime has tolerances
to provide for circuit losses between
conformance test point at the AUI and
measurement point within the state machine
Notes
ShortEvents may indicate
generated noise hits which will cause the
to transmit Runts to its other ports, or
a collision (which may be late) back to
transmitting DTE and damaged frames to the rest
the network
Implementors may wish to consider selecting
ShortEventMaxTime towards the lower end of
allowed tolerance range to accommodate bit
suffered through physical channel devices
budgeted for within this standard
The significance of this attribute is
in 10 and 100 Mb/s collision domains. Clause 9
repeaters perform fragment extension of
de Graaf, et. al. Standards Track [Page 32]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
events which would be counted as runts on
interconnect ports of other repeaters.
27 repeaters do not perform fragment extension
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
The approximate minimum time for rollover of
counter is 16 hours in a 10Mb/s repeater."
"[IEEE 802.3 Mgt], 30.4.3.1.9, aShortEvents."
::= { rptrMonitorPortEntry 8 }
rptrMonitorPortRunts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This counter is incremented by one for
CarrierEvent on this port that meets one of
following two conditions. Only one test need
made. a) The ActivityDuration is greater
ShortEventMaxTime and less than
and the CollisionEvent signal is deasserted. b
The OctetCount is less than 64,
ActivityDuration is greater than
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
but less than 82 bit times shall increment
the shortEvents counter or the runts counter
not both. A CarrierEvent greater than or equal
552 bit times but less than 565 bit times may
may not be counted as a runt
ValidPacketMinTime has tolerances included
provide for circuit losses between a
test point at the AUI and the measurement
within the state machine
Runts usually indicate collision fragments,
normal network event. In certain
associated with large diameter networks
percentage of collision fragments may
ValidPacketMinTime
de Graaf, et. al. Standards Track [Page 33]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
The approximate minimum time for rollover of
counter is 16 hours in a 10Mb/s repeater."
"[IEEE 802.3 Mgt], 30.4.3.1.10, aRunts."
::= { rptrMonitorPortEntry 9 }
rptrMonitorPortCollisions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"For a clause 9 repeater, this counter
incremented by one for any CarrierEvent
on any port for which the CollisionEvent
on this port is asserted. For a clause 27
repeater port the counter increments on
the Collision Count Increment state of
partition state diagram (fig 27-8
[IEEE 802.3 Std]).
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
The approximate minimum time for rollover of
counter is 16 hours in a 10Mb/s repeater."
"[IEEE 802.3 Mgt], 30.4.3.1.11, aCollisions."
::= { rptrMonitorPortEntry 10 }
rptrMonitorPortLateEvents OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"For a clause 9 repeater port, this counter
incremented by one for each
on this port in which the CollIn(X
variable transitions to the value SQE (Ref
9.6.6.2, IEEE 802.3 Std) while
ActivityDuration is greater than
LateEventThreshold. For a clause 27
port, this counter is incremented by one
entering the Collision Count Increment
de Graaf, et. al. Standards Track [Page 34]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
of the partition state diagram (fig 27-8)
while the ActivityDuration is greater
the LateEvent- Threshold. Such a
is counted twice, as both a collision and as
lateEvent
The LateEventThreshold is greater than 480
times and less than 565 bit times
LateEventThreshold has tolerances included
permit an implementation to build a
threshold to serve as both the
and ValidPacketMinTime threshold
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
The approximate minimum time for rollover of
counter is 81 hours in a 10Mb/s repeater."
"[IEEE 802.3 Mgt], 30.4.3.1.12, aLateEvents."
::= { rptrMonitorPortEntry 11 }
rptrMonitorPortVeryLongEvents OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"For a clause 9 repeater port, this
is incremented by one for each
whose ActivityDuration is greater than
MAU Jabber Lockup Protection timer TW
(Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std).
For a clause 27 repeater port, this
is incremented by one on entry to
Rx Jabber state of the receiver timer
diagram (fig 27-7). Other counters
be incremented as appropriate
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes."
"[IEEE 802.3 Mgt], 30.4.3.1.13, aVeryLongEvents."
::= { rptrMonitorPortEntry 12 }
rptrMonitorPortDataRateMismatches OBJECT-
de Graaf, et. al. Standards Track [Page 35]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This counter is incremented by one for
frame received by this port that meets
of the conditions required by only one of
following two measurement methods
Measurement method A: 1) The
signal is not asserted (10Mb/s operation)
the Collision Count Increment state of
partition state diagram (fig 27-8
[IEEE 802.3 Std]) has not been
(100Mb/s operation). 2) The
is greater than ValidPacketMinTime. 3)
frequency (data rate) is detectably
from the local transmit frequency
Measurement method B: 1) The
signal is not asserted (10Mb/s operation
or the Collision Count Increment state of
partition state diagram (fig 27-8
[IEEE 802.3 Std]) has not been
(100Mb/s operation). 2) The OctetCount
greater than 63. 3) The frequency (
rate) is detectably mismatched from the
transmit frequency. The exact degree
mismatch is vendor specific and is to
defined by the vendor for conformance testing
When this event occurs, other counters
increment conditions were satisfied may or may
also be incremented, at the implementor'
discretion. Whether or not the repeater was
to maintain data integrity is beyond the scope
this standard
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes."
"[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches."
::= { rptrMonitorPortEntry 13 }
rptrMonitorPortAutoPartitions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
de Graaf, et. al. Standards Track [Page 36]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
STATUS
"This counter is incremented by one
each time the repeater has
partitioned this port
The conditions that cause a clause 9
repeater port to partition are specified
the partition state diagram in clause 9
[IEEE 802.3 Std]. They are not
here. A clause 27 repeater port
on entry to the Partition Wait state of
partition state diagram (fig 27-8
[IEEE 802.3 Std]).
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes."
"[IEEE 802.3 Mgt], 30.4.3.1.15, aAutoPartitions."
::= { rptrMonitorPortEntry 14 }
rptrMonitorPortTotalErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of errors which have occurred
this port. This counter is the summation of
values of other error counters (for the
port), namely
rptrMonitorPortFCSErrors
rptrMonitorPortAlignmentErrors
rptrMonitorPortFrameTooLongs
rptrMonitorPortShortEvents
rptrMonitorPortLateEvents
rptrMonitorPortVeryLongEvents
rptrMonitorPortDataRateMismatches,
rptrMonitorPortSymbolErrors
This counter is redundant in the sense that it
the summation of information already
through other objects. However, it is
specifically because the regular retrieval of
object as a means of tracking the health of a
provides a considerable optimization of
management traffic over the otherwise
de Graaf, et. al. Standards Track [Page 37]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
retrieval of the summed counters
Note that rptrMonitorPortRunts is not
in this total; this is because runts
indicate collision fragments, a normal
event
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes."
::= { rptrMonitorPortEntry 15 }
rptrMonitorPortLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime when the last
the following occurred
1) the agent cold- or warm-started
2) the row for the port was
(such as when a device or module was
to the system);
3) any condition that would cause one
the counters for the row to
a discontinuity."
::= { rptrMonitorPortEntry 16 }
rptrMonitor100PortTable OBJECT-
SYNTAX SEQUENCE OF RptrMonitor100
MAX-ACCESS not-
STATUS
"Table of additional performance and
statistics for 100Mb/s ports, above
beyond those parameters that apply to
10 and 100Mbps ports. Entries exist only
ports attached to 100Mbps repeaters
The columnar object
is used to indicate possible
of counter type columnar objects in this table."
::= { rptrMonitorPortInfo 2 }
rptrMonitor100PortEntry OBJECT-
SYNTAX RptrMonitor100
MAX-ACCESS not-
STATUS
de Graaf, et. al. Standards Track [Page 38]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
"An entry in the table, containing
and error statistics for a single 100Mb/s port."
INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
::= { rptrMonitor100PortTable 1 }
RptrMonitor100PortEntry ::=
SEQUENCE {
Counter32,
Counter32,
rptrMonitorPortUpper32
Counter32,
Counter64
}
rptrMonitorPortIsolates OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This counter is incremented by one each time
the repeater port automatically isolates as
consequence of false carrier events. The
which cause a port to automatically isolate
defined by the transition from the False
state to the Link Unstable state of the
integrity state diagram (figure 27-9)
[IEEE 802.3 Standard].
Note: Isolates do not affect the value
the PortOperStatus object
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes."
"[IEEE 802.3 Mgt], 30.4.3.1.16, aIsolates."
::= { rptrMonitor100PortEntry 1 }
rptrMonitorPortSymbolErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This counter is incremented by one each time
de Graaf, et. al. Standards Track [Page 39]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
valid length packet was received at the port
there was at least one occurrence of an
data symbol. This can increment only once per
carrier event. A collision presence at any port
the repeater containing port N, will not cause
attribute to increment
A discontinuity may occur in the
when the value of
rptrMonitorPortLastChange changes
The approximate minimum time for rollover of
counter is 7.4 hours at 100Mb/s."
"[IEEE 802.3 Mgt], 30.4.3.1.17,
aSymbolErrorDuringPacket."
::= { rptrMonitor100PortEntry 2 }
rptrMonitorPortUpper32Octets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"This object is the number of octets contained
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
lower 32 bits are contained in
rptrMonitorPortReadableOctets object
This two-counter mechanism is provided for
network management protocols that do not
