All MIBs › Juniper-System-MIB › juniSystemUtilizationHoldDownTime
juniSystemUtilizationHoldDownTime
Module: Juniper-System-MIB
OID (symbolic): Juniper-System-MIB::juniSystemUtilizationHoldDownTime
OID (numeric): 1.3.6.1.4.1.4874.2.2.2.1.10.1.1.9
Node type: OBJECT-TYPE
Type: Gauge32
Access: read-write
Description: The hold-down time (holdTime) used in conjunction with juniSystemUtilizationThresholdRising (risingVal) and juniSystemUtilizationThresholdFalling (fallingVal) to decide when to trigger an event indicating that the resource utilization, juniSystemUtilizationCurrentValue (currentVal), has reached or surpassed one of the thresholds.
This object provides one element in the formula used to determine when to send a utilization notification. If the resource utilization increases to the rising threshold value but a prior rising or falling utilization event has been triggered within this hold-down time then no rising threshold utilization notification may be sent at that time. If the resource utilization decreases to the falling threshold value but a prior rising or falling utilization event has been triggered within this hold-down time then no falling threshold utilization notification may be sent at that time. However, if the end of a hold-down period for a rising threshold utilization notification is reached and the current value is at or below the falling threshold value, then a falling threshold notification is sent and the hold-down timer is restarted. Likewise, if the end of a hold-down period for a falling threshold utilization notification is reached and the current value is at or above the rising threshold value, then a rising threshold notification is sent and the hold-down timer is restarted.
The pseudo-code in the juniSystemUtilizationThresholdRising DESCRIPTION states the algorithm more precisely.
What is juniSystemUtilizationHoldDownTime?
This sets, in seconds, the minimum time between resource-utilization notifications for a given resource, preventing a flood of rising/falling alarms when usage hovers right at a threshold. It works together with the rising and falling threshold objects to pace notifications.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.2.1.10.1.1.9 snmpwalk -v2c -c public <target> Juniper-System-MIB::juniSystemUtilizationHoldDownTime
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.2.1.10.1.1.9.1 snmpget -v2c -c public <target> Juniper-System-MIB::juniSystemUtilizationHoldDownTime.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.4874.2.2.2.1.10.1.1.9.1 i <value>
Start monitoring Juniper E-series router, ERX/ES2, JUNOSe (system inventory/software/memory health) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Juniper-System-MIB::juniSystemUtilizationHoldDownTime OID value, configure state conditions and alerts, and monitor any Juniper E-series router, ERX/ES2, JUNOSe (system inventory/software/memory health) from a single console.
OID Breakdown
Upper-level ancestors (10 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.4874 | juniperUni | Juniper-UNI-SMI |
| 1.3.6.1.4.1.4874.2 | juniperUniMibs | Juniper-UNI-SMI |
| 1.3.6.1.4.1.4874.2.2 | juniMibs | Juniper-MIBs |
| 1.3.6.1.4.1.4874.2.2.2 | juniSystemMIB | Juniper-MIBs |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.4874.2.2.2.1 | juniSystemObjects | Juniper-System-MIB |
| 1.3.6.1.4.1.4874.2.2.2.1.10 | juniSystemUtilization | Juniper-System-MIB |
| 1.3.6.1.4.1.4874.2.2.2.1.10.1 | juniSystemUtilizationTable | Juniper-System-MIB |
| 1.3.6.1.4.1.4874.2.2.2.1.10.1.1 | juniSystemUtilizationEntry | Juniper-System-MIB |
| 1.3.6.1.4.1.4874.2.2.2.1.10.1.1.9 | juniSystemUtilizationHoldDownTime | Juniper-System-MIB |