---
oid: "1.3.6.1.2.1.22.0.1"
short-description: "rptrHealth NOTIFICATION-TYPE"
last-modified: "2020-01-07"
parent-oid: "1.3.6.1.2.1.22.0"
---

## OID: `1.3.6.1.2.1.22.0.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) snmpDot3RptrMgt(22) 0 rptrHealth(1)}
```

### Description

```asn1
rptrHealth NOTIFICATION-TYPE
OBJECTS { rptrOperStatus }
STATUS deprecated
DESCRIPTION
"********* 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.)"
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth
notification."
```

**Classification:** Deprecated or obsolete OID; MIB object for network management

### Supplementary information

Automatically extracted from IETF [RFC 2108](https://www.rfc-editor.org/rfc/rfc2108.html).

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.