SNMP-REPEATER-MIB

        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.
        
System interconnect segment - An internal
segment allowing interconnection of ports
belonging to different physical entities
into the same logical manageable repeater.
Examples of implementation might be
backplane busses in modular hubs, or
chaining cables in stacks of hubs.
        
Stack - A scalable system that may include
managed repeaters, in which modularity is
achieved by interconnecting a number of
different chassis.
        
Module - A building block in a modular
chassis.  It typically maps into one 'slot';
however, the range of configurations may be
very large, with several modules entering
one slot, or one module covering several
slots.
    
Source file
SNMP-REPEATER-MIB
Last revised
Identity
snmpRptrMod
Base OID
1.3.6.1.2.1.22.5
Imported Objects
IF-MIB OwnerString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Counter64 Gauge32 Integer32 mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) TimeTicks
SNMPv2-TC DisplayString MacAddress RowStatus TestAndIncr TEXTUAL-CONVENTION (no object page) TimeStamp
Net-SNMP examples using the rfc MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'SNMP-REPEATER-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'SNMP-REPEATER-MIB::snmpRptrMod'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'SNMP-REPEATER-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SNMP-REPEATER-MIB::snmpRptrMod'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (134)
.1.3.6.1.2.1.22
.1.3.6.1.2.1.22.1
.1.3.6.1.2.1.22.1.1
rptrGroupCapacity deprecated
Integer32
.1.3.6.1.2.1.22.1.1.1
rptrOperStatus deprecated
Enumeration
.1.3.6.1.2.1.22.1.1.2
rptrHealthText deprecated
OctetString
.1.3.6.1.2.1.22.1.1.3
rptrReset deprecated r/w
Enumeration
.1.3.6.1.2.1.22.1.1.4
rptrNonDisruptTest deprecated r/w
Enumeration
.1.3.6.1.2.1.22.1.1.5
.1.3.6.1.2.1.22.1.1.6
.1.3.6.1.2.1.22.1.2
.1.3.6.1.2.1.22.1.2.1
.1.3.6.1.2.1.22.1.2.1.1
Integer32
.1.3.6.1.2.1.22.1.2.1.1.1
rptrGroupDescr deprecated
OctetString
.1.3.6.1.2.1.22.1.2.1.1.2
ObjectIdentifier
.1.3.6.1.2.1.22.1.2.1.1.3
Enumeration
.1.3.6.1.2.1.22.1.2.1.1.4
.1.3.6.1.2.1.22.1.2.1.1.5
Integer32
.1.3.6.1.2.1.22.1.2.1.1.6
.1.3.6.1.2.1.22.1.3
.1.3.6.1.2.1.22.1.3.1
.1.3.6.1.2.1.22.1.3.1.1
Integer32
.1.3.6.1.2.1.22.1.3.1.1.1
Integer32
.1.3.6.1.2.1.22.1.3.1.1.2
Enumeration
.1.3.6.1.2.1.22.1.3.1.1.3
Enumeration
.1.3.6.1.2.1.22.1.3.1.1.4
Enumeration
.1.3.6.1.2.1.22.1.3.1.1.5
Integer32
.1.3.6.1.2.1.22.1.3.1.1.6
.1.3.6.1.2.1.22.1.4
.1.3.6.1.2.1.22.1.4.1
.1.3.6.1.2.1.22.1.4.1.1
Integer32
.1.3.6.1.2.1.22.1.4.1.1.1
Enumeration
.1.3.6.1.2.1.22.1.4.1.1.2
Enumeration
.1.3.6.1.2.1.22.1.4.1.1.3
Enumeration
.1.3.6.1.2.1.22.1.4.1.1.4
.1.3.6.1.2.1.22.1.4.1.1.5
.1.3.6.1.2.1.22.1.4.1.1.6
.1.3.6.1.2.1.22.2
.1.3.6.1.2.1.22.2.1
.1.3.6.1.2.1.22.2.1.1
.1.3.6.1.2.1.22.2.2
.1.3.6.1.2.1.22.2.2.1
.1.3.6.1.2.1.22.2.2.1.1
Integer32
.1.3.6.1.2.1.22.2.2.1.1.1
.1.3.6.1.2.1.22.2.2.1.1.2
.1.3.6.1.2.1.22.2.2.1.1.3
.1.3.6.1.2.1.22.2.2.1.1.4
.1.3.6.1.2.1.22.2.3
.1.3.6.1.2.1.22.2.3.1
.1.3.6.1.2.1.22.2.3.1.1
Integer32
.1.3.6.1.2.1.22.2.3.1.1.1
.1.3.6.1.2.1.22.2.3.1.1.10
.1.3.6.1.2.1.22.2.3.1.1.11
.1.3.6.1.2.1.22.2.3.1.1.12
.1.3.6.1.2.1.22.2.3.1.1.13
.1.3.6.1.2.1.22.2.3.1.1.14
.1.3.6.1.2.1.22.2.3.1.1.15
.1.3.6.1.2.1.22.2.3.1.1.16
Integer32
.1.3.6.1.2.1.22.2.3.1.1.2
.1.3.6.1.2.1.22.2.3.1.1.3
.1.3.6.1.2.1.22.2.3.1.1.4
.1.3.6.1.2.1.22.2.3.1.1.5
.1.3.6.1.2.1.22.2.3.1.1.6
.1.3.6.1.2.1.22.2.3.1.1.7
.1.3.6.1.2.1.22.2.3.1.1.8
.1.3.6.1.2.1.22.2.3.1.1.9
.1.3.6.1.2.1.22.2.3.2
.1.3.6.1.2.1.22.2.3.2.1
.1.3.6.1.2.1.22.2.3.2.1.1
.1.3.6.1.2.1.22.2.3.2.1.2
.1.3.6.1.2.1.22.2.3.2.1.3
.1.3.6.1.2.1.22.2.3.2.1.4
.1.3.6.1.2.1.22.2.4
.1.3.6.1.2.1.22.2.4.1
.1.3.6.1.2.1.22.2.4.1.1
.1.3.6.1.2.1.22.2.4.1.1.1
.1.3.6.1.2.1.22.2.4.1.1.3
.1.3.6.1.2.1.22.2.4.1.1.4
.1.3.6.1.2.1.22.2.4.1.1.5
.1.3.6.1.2.1.22.2.4.2
.1.3.6.1.2.1.22.2.4.2.1
.1.3.6.1.2.1.22.2.4.2.1.1
.1.3.6.1.2.1.22.2.4.2.1.2
.1.3.6.1.2.1.22.3
.1.3.6.1.2.1.22.3.1
.1.3.6.1.2.1.22.3.1.1
.1.3.6.1.2.1.22.3.1.1.1
.1.3.6.1.2.1.22.3.1.1.1.1
Enumeration
.1.3.6.1.2.1.22.3.1.1.1.2
.1.3.6.1.2.1.22.3.1.1.1.3
Enumeration
.1.3.6.1.2.1.22.3.1.1.1.4
Integer32
.1.3.6.1.2.1.22.3.1.1.1.5
Integer32
.1.3.6.1.2.1.22.3.1.1.1.6
.1.3.6.1.2.1.22.3.1.1.1.7
.1.3.6.1.2.1.22.3.2
.1.3.6.1.2.1.22.3.3
.1.3.6.1.2.1.22.3.3.1
.1.3.6.1.2.1.22.3.3.1.1
Integer32
.1.3.6.1.2.1.22.3.3.1.1.1
Integer32
.1.3.6.1.2.1.22.3.3.1.1.2
.1.3.6.1.2.1.22.3.3.1.1.3
.1.3.6.1.2.1.22.3.3.1.1.4
.1.3.6.1.2.1.22.3.3.1.1.5
.1.3.6.1.2.1.22.3.3.1.1.6
.1.3.6.1.2.1.22.3.3.2
.1.3.6.1.2.1.22.3.3.2.1
Integer32
.1.3.6.1.2.1.22.3.3.2.1.1
.1.3.6.1.2.1.22.3.3.2.1.2
.1.3.6.1.2.1.22.4
.1.3.6.1.2.1.22.4.1
.1.3.6.1.2.1.22.4.2
.1.3.6.1.2.1.22.4.3
.1.3.6.1.2.1.22.4.3.1
.1.3.6.1.2.1.22.4.3.1.1
Integer32
.1.3.6.1.2.1.22.4.3.1.1.1
.1.3.6.1.2.1.22.4.3.1.1.10
Integer32
.1.3.6.1.2.1.22.4.3.1.1.2
Enumeration
.1.3.6.1.2.1.22.4.3.1.1.3
Integer32
.1.3.6.1.2.1.22.4.3.1.1.4
Integer32
.1.3.6.1.2.1.22.4.3.1.1.5
.1.3.6.1.2.1.22.4.3.1.1.6
Integer32
.1.3.6.1.2.1.22.4.3.1.1.7
.1.3.6.1.2.1.22.4.3.1.1.8
.1.3.6.1.2.1.22.4.3.1.1.9
.1.3.6.1.2.1.22.4.3.2
.1.3.6.1.2.1.22.4.3.2.1
Integer32
.1.3.6.1.2.1.22.4.3.2.1.1
Integer32
.1.3.6.1.2.1.22.4.3.2.1.2
Integer32
.1.3.6.1.2.1.22.4.3.2.1.3
.1.3.6.1.2.1.22.4.3.2.1.4
.1.3.6.1.2.1.22.5
.1.3.6.1.2.1.22.5.1
.1.3.6.1.2.1.22.5.1.1
.1.3.6.1.2.1.22.5.1.2
.1.3.6.1.2.1.22.5.1.3
Dependencies (6) 4 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. IANAifType-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMPv2-MIBrfc
  6. IF-MIBrfc
  7. SNMP-REPEATER-MIBrfcselected
Type Definitions (1)
OctetString range: 0range: 6
Conformance Groups (12)
********* THIS GROUP IS DEPRECATED **********

Basic group from RFCs 1368 and 1516.

NOTE: this object group is DEPRECATED and replaced
with snmpRptrGrpBasic.
.1.3.6.1.2.1.22.5.1.2.1
********* THIS GROUP IS DEPRECATED **********

Monitor group from RFCs 1368 and 1516.

NOTE: this object group is DEPRECATED and replaced
with snmpRptrGrpMonitor.
.1.3.6.1.2.1.22.5.1.2.2
Address tracking group from RFC 1368.

NOTE: this object group is OBSOLETE and replaced
with snmpRptrGrpAddrTrack1516.
.1.3.6.1.2.1.22.5.1.2.3
********* THIS GROUP IS DEPRECATED **********

Address tracking group from RFC 1516.

NOTE: this object group is DEPRECATED and
replaced with snmpRptrGrpAddrTrack.
.1.3.6.1.2.1.22.5.1.2.4
Basic group for a system with one or more
repeater-units in multi-segment (post-RFC 1516)
version of the MIB module.
.1.3.6.1.2.1.22.5.1.2.5
Monitor group for a system with one or more
repeater-units in multi-segment (post-RFC 1516)
version of the MIB module.
.1.3.6.1.2.1.22.5.1.2.6
Monitor group for 100Mb/s ports and repeaters
in a system with one or more repeater-units in
multi-segment (post-RFC 1516) version of the MIB
module. Systems which support Counter64 should
also implement snmpRptrGrpMonitor100w64.
.1.3.6.1.2.1.22.5.1.2.7
Monitor group for 100Mb/s ports and repeaters in a
system with one or more repeater-units and support
for Counter64.
.1.3.6.1.2.1.22.5.1.2.8
Passive address tracking group for post-RFC 1516
version of the MIB module.
.1.3.6.1.2.1.22.5.1.2.9
Extended passive address tracking group for
a system with one or more repeater-units in
post-RFC 1516 version of the MIB module.
.1.3.6.1.2.1.22.5.1.2.10
Active MAC address search group and topology
mapping support for repeaters.
.1.3.6.1.2.1.22.5.1.2.11
Top `N' group for repeater ports.
.1.3.6.1.2.1.22.5.1.2.12
Compliance Statements (3)

OID .1.3.6.1.2.1.22.5.1.1.1
Compliance for RFC 1368.

NOTE: this module compliance is OBSOLETE and
replaced by snmpRptrModComplRFC1516.
Required groups
mandatory snmpRptrGrpBasic1516
optional snmpRptrGrpMonitor1516 Implementation of this optional group is
recommended for systems which have the
instrumentation to do performance monitoring.
optional snmpRptrGrpAddrTrack1368 Implementation of this group is
recommended for systems which have
the necessary instrumentation.

OID .1.3.6.1.2.1.22.5.1.1.2
********* THIS COMPLIANCE IS DEPRECATED **********

Compliance for RFC 1516 and for backwards
compatibility with single-repeater,
10Mb/s-only implementations.
Required groups
mandatory snmpRptrGrpBasic1516
optional snmpRptrGrpMonitor1516 Implementation of this optional group is
recommended for systems which have the
instrumentation to do performance monitoring.
optional snmpRptrGrpAddrTrack1516 Implementation of this group is
recommended for systems which have
the necessary instrumentation.

OID .1.3.6.1.2.1.22.5.1.1.3
Compliance for the multi-segment version of the
MIB module for a system with one or more
repeater-units.
Required groups
mandatory snmpRptrGrpBasic
mandatory snmpRptrGrpMonitor
mandatory snmpRptrGrpAddrTrack
optional snmpRptrGrpMonitor100 Implementation of this group is
mandatory for managed systems which
contain 100Mb/s repeaters.
optional snmpRptrGrpMonitor100w64 Implementation of this group is
mandatory for managed systems which
contain 100Mb/s repeaters and which
can support Counter64.
optional snmpRptrGrpExtAddrTrack Implementation of this group is
recommended for systems which have
the necessary instrumentation to track
MAC addresses of multiple DTEs attached
to a single repeater port.
optional snmpRptrGrpRptrAddrSearch Implementation of this group is
recommended for systems which allow
read-write access and which have
the necessary instrumentation to
search all incoming data streams
for a particular MAC address.
optional snmpRptrGrpTopNPort Implementation of this group is
recommended for systems which have

the necessary resources to support
TopN statistics reporting.
Notifications / Traps (5)
NameOIDDescription
rptrHealth deprecated
.1.3.6.1.2.1.22.0.1
********* THIS OBJECT IS DEPRECATED **********

In a system containing a single managed repeater,
the rptrHealth notification conveys information
related to the operational status of the repeater.
It is sent either when the value of
rptrOperStatus changes, or upon completion of a
non-disruptive test.

The rptrHealth notification must contain the
rptrOperStatus object. The agent may optionally
include the rptrHealthText object in the varBind
list. See the rptrOperStatus and rptrHealthText
objects for descriptions of the information that
is sent.

The agent must throttle the generation of
consecutive rptrHealth traps so that there is at
least a five-second gap between traps of this
type. When traps are throttled, they are dropped,
not queued for sending at a future time. (Note

that 'generating' a trap means sending to all
configured recipients.)
.1.3.6.1.2.1.22.0.2
********* THIS OBJECT IS DEPRECATED **********

In a system containing a single managed repeater,
this notification is sent when a change occurs in the
group structure of the repeater. This occurs only
when a group is logically or physically removed
from or added to a repeater. The varBind list
contains the identifier of the group that was
removed or added.

The agent must throttle the generation of
consecutive rptrGroupChange traps for the same
group so that there is at least a five-second gap
between traps of this type. When traps are
throttled, they are dropped, not queued for
sending at a future time. (Note that 'generating'
a trap means sending to all configured
recipients.)
rptrResetEvent deprecated
.1.3.6.1.2.1.22.0.3
********* THIS OBJECT IS DEPRECATED **********

In a system containing a single managed repeater-unit,
the rptrResetEvent notification conveys information
related to the operational status of the repeater.
This trap is sent on completion of a repeater
reset action. A repeater reset action is defined
as an a transition to the START state of Fig 9-2
in section 9 [IEEE 802.3 Std], when triggered by a
management command (e.g., an SNMP Set on the

rptrReset object).

The agent must throttle the generation of
consecutive rptrResetEvent traps so that there is
at least a five-second gap between traps of this
type. When traps are throttled, they are dropped,
not queued for sending at a future time. (Note
that 'generating' a trap means sending to all
configured recipients.)

The rptrResetEvent trap is not sent when the agent
restarts and sends an SNMP coldStart or warmStart
trap. However, it is recommended that a repeater
agent send the rptrOperStatus object as an
optional object with its coldStart and warmStart
trap PDUs.

The rptrOperStatus object must be included in the
varbind list sent with this trap. The agent may
optionally include the rptrHealthText object as
well.
.1.3.6.1.2.1.22.0.4
In a system containing multiple managed repeaters,
the rptrInfoHealth notification conveys information
related to the operational status of a repeater.
It is sent either when the value of rptrInfoOperStatus
changes, or upon completion of a non-disruptive test.

The agent must throttle the generation of
consecutive rptrInfoHealth notifications for
the same repeater so that there is at least
a five-second gap between notifications of this type.
When notifications are throttled, they are dropped,
not queued for sending at a future time. (Note

that 'generating' a notification means sending
to all configured recipients.)
.1.3.6.1.2.1.22.0.5
In a system containing multiple managed
repeaters, the rptrInfoResetEvent notification
conveys information related to the operational
status of a repeater. This notification is sent
on completion of a repeater reset action. A
repeater reset action is defined as a transition
to the START state of Fig 9-2 in section 9 of
[IEEE 802.3 Std], when triggered by a management
command (e.g., an SNMP Set on the rptrInfoReset
object).

The agent must throttle the generation of
consecutive rptrInfoResetEvent notifications for
a single repeater so that there is at least
a five-second gap between notifications of
this type. When notifications are throttled,
they are dropped, not queued for sending at
a future time. (Note that 'generating' a
notification means sending to all configured
recipients.)

The rptrInfoResetEvent is not sent when the
agent restarts and sends an SNMP coldStart or
warmStart trap. However, it is recommended that
a repeater agent send the rptrInfoOperStatus
object as an optional object with its coldStart
and warmStart trap PDUs.