Juniper-SLEP-MIB :: juniSlepKeepAliveFailures

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Juniper-SLEP-MIB › juniSlepKeepAliveFailures

juniSlepKeepAliveFailures

Module: Juniper-SLEP-MIB

OID (symbolic): Juniper-SLEP-MIB::juniSlepKeepAliveFailures

OID (numeric): 1.3.6.1.4.1.4874.2.2.15.1.1.3.1.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of link drops due to keep-alive failures.

What is juniSlepKeepAliveFailures?

This read-only counter tracks the number of times a SLEP link has dropped because keep-alive messages failed. Admins monitor this to detect an unstable link between SLEP peers; a rapidly climbing counter points to connectivity or timing problems, possibly related to the juniSlepKeepAliveTimer setting, between the local and remote entities. For example, if juniSlepKeepAliveFailures jumps from 3 to 15 over a short period, that signals the SLEP link is repeatedly losing its keep-alive exchange and dropping.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.15.1.1.3.1.2
snmpwalk -v2c -c public <target> Juniper-SLEP-MIB::juniSlepKeepAliveFailures

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.15.1.1.3.1.2.1
snmpget -v2c -c public <target> Juniper-SLEP-MIB::juniSlepKeepAliveFailures.1

Start monitoring Juniper Networks E-series router (Serial Line Encapsulation Protocol WAN links) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Juniper-SLEP-MIB::juniSlepKeepAliveFailures OID value, configure state conditions and alerts, and monitor any Juniper Networks E-series router (Serial Line Encapsulation Protocol WAN links) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper Networks E-series router (Serial Line Encapsulation Protocol WAN links) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type juniSlepKeepAliveFailures into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of link drops due to keep-alive failures. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
1.3.6.1.4.1.4874.2.2.15juniSlepMIBSJuniper-MIBs
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.15.1juniSlepObjectsJuniper-SLEP-MIB
1.3.6.1.4.1.4874.2.2.15.1.1juniSlepIfLayerJuniper-SLEP-MIB
1.3.6.1.4.1.4874.2.2.15.1.1.3juniSlepIfStatisticsTableJuniper-SLEP-MIB
1.3.6.1.4.1.4874.2.2.15.1.1.3.1juniSlepIfStatisticsEntryJuniper-SLEP-MIB
1.3.6.1.4.1.4874.2.2.15.1.1.3.1.2juniSlepKeepAliveFailuresJuniper-SLEP-MIB