MIB Discovery

Recherche :

1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 69 (docsDev). 1 (docsDevMIBObjects). 5 (docsDevEvent). 3 (docsDevEvThrottleAdminStatus)
OID : 1.3.6.1.2.1.69.1.5.3
TXT : iso. org. dod. internet. mgmt. mib-2. docsDev. docsDevMIBObjects. docsDevEvent. docsDevEvThrottleAdminStatus
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.2.1.69.1.5.3
Module DOCS-CABLE-DEVICE-MIB (CISCO)
NomdocsDevEvThrottleAdminStatus
Accesreadwrite
Statuscurrent
DescriptionControls the transmission of traps and syslog messages with respect to the trap pacing threshold. unconstrained(1) causes traps and syslog messages to be transmitted without regard to the threshold settings. maintainBelowThreshold(2) causes trap transmission and syslog messages to be suppressed if the number of traps would otherwise exceed the threshold. stopAtThreshold(3) causes trap transmission to cease at the threshold and not to resume until directed to do so. inhibited(4) causes all trap transmission and syslog messages to be suppressed. A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event. Writing to this object resets the thresholding state.
SyntaxeEnumeration (1-unconstrained, 2-maintainBelowThreshold, 3-stopAtThreshold, 4-inhibited)
Module DOCS-CABLE-DEVICE-MIB (ietf)
NomdocsDevEvThrottleAdminStatus
Accesreadwrite
Statuscurrent
DescriptionControls the transmission of traps and syslog messages with respect to the trap pacing threshold. unconstrained(1) causes traps and syslog messages to be transmitted without regard to the threshold settings. maintainBelowThreshold(2) causes trap transmission and syslog messages to be suppressed if the number of traps would otherwise exceed the threshold. stopAtThreshold(3) causes trap transmission to cease at the threshold and not to resume until directed to do so. inhibited(4) causes all trap transmission and syslog messages to be suppressed. A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event. Writing to this object resets the thresholding state.
SyntaxeEnumeration (1-unconstrained, 2-maintainBelowThreshold, 3-stopAtThreshold, 4-inhibited)
D. Fournier - 2024