Descriptions
Descriptions may differ between sources. The primary description is shown first.
Primary description: OID Repository
rptrResetEvent NOTIFICATION-TYPE
OBJECTS { rptrOperStatus }
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
In a system containing a single managed repeater-unit,
the rptrResetEvent notification conveys information
related to the operational status of the repeater.
This trap is sent on completion of a repeater
reset action. A repeater reset action is defined
as an a transition to the START state of Fig 9-2
in section 9 [IEEE 802.3 Std], when triggered by a
management command (e.g., an SNMP Set on the
rptrReset object).
The agent must throttle the generation of
consecutive rptrResetEvent traps so that there is
at least a five-second gap between traps of this
type. When traps are throttled, they are dropped,
not queued for sending at a future time. (Note
that \generating\ a trap means sending to all
configured recipients.)
The rptrResetEvent trap is not sent when the agent
restarts and sends an SNMP coldStart or warmStart
trap. However, it is recommended that a repeater
agent send the rptrOperStatus object as an
optional object with its coldStart and warmStart
trap PDUs.
The rptrOperStatus object must be included in the
varbind list sent with this trap. The agent may
optionally include the rptrHealthtext object as
well."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset
notification."
View at oid-base.com
Alternative description: Circitor
********* 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.
Parsed from file
SNMP-REPEATER-MIB.mib
Module: SNMP-REPEATER-MIB
Source file: Download SNMP-REPEATER-MIB.txt
· Publisher's file
Copy from Netdisco; File: rfc/SNMP-REPEATER-MIB.txt; 122,655 bytes
Vendor MIB copy from the Netdisco archive.
Related source files and packages:
Source file: Download SNMP-REPEATER-MIB
· Publisher's file
Copy from Observium Community; File: rfc/SNMP-REPEATER-MIB; 122,655 bytes
Vendor MIB copy from the Observium Community archive.
Related source files and packages:
Source file: Download RFC 2108
· Publisher's file
· RFC errata
File: rfc/rfc2108.txt; 166,336 bytes
Source file: Download SNMP-REPEATER-MIB.mib
Publisher path: Mibs; 134,592 bytes
Source file: Download rfc2108-IEEE-802.3-Repeater-Devices.mib.txt
File: ietf_rfcs/rfc2108-IEEE-802.3-Repeater-Devices.mib.txt; 134,581 bytes
Alternative description: MIBdepot
********* 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.
Source file: Download rfc2108.mib.txt
File: hp/rfc2108.mib.txt; 135,271 bytes
rptrResetEvent — MIBdepot
The rptrReset trap conveys information related to the operational state 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 [11], when triggered by a management command (e.g., an SNMP Set on the rptrReset object). The agent must throttle the generation of consecutive rptrReset traps so that there is at least a five-second gap between them. The rptrReset 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 rptrHealth variables as optional variables with its coldStart and warmStart trap PDUs. The rptrOperStatus variable must be included in the varbind list sent with this trap. The agent may optionally include the rptrHealthText variable as well.
rptrResetEvent — Circitor, MIBdepot, RFC Editor
The rptrResetEvent trap 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 them. 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.
rptrResetEvent — D-Link official switch MIBs, HPE Instant On official MIBs, NETGEAR official product and EOL MIB downloads
********* 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.
rptrResetEvent — Circitor, Cisco SMIv1, MIBdepot, Common and standard MIB copies (LibreNMS/Observium Community), RFC Editor
The rptrResetEvent trap 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.