BLACKBERRYSERVER-MIB :: besSysHealthMdsConnectionFailure

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBLACKBERRYSERVER-MIBbesSysHealthMdsConnectionFailure

besSysHealthMdsConnectionFailure

Module: BLACKBERRYSERVER-MIB

OID (symbolic): BLACKBERRYSERVER-MIB::besSysHealthMdsConnectionFailure

OID (numeric): 1.3.6.1.4.1.3530.5.25.1.71

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Number of failed connections initiated by MDS to another address/service.

What is besSysHealthMdsConnectionFailure?

Reports the number of connections MDS attempted to establish to another address or service that failed, the counterpart to besSysHealthMdsConnectionSuccess.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3530.5.25.1.71
snmpwalk -v2c -c public <target> BLACKBERRYSERVER-MIB::besSysHealthMdsConnectionFailure

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3530.5.25.1.71.1
snmpget -v2c -c public <target> BLACKBERRYSERVER-MIB::besSysHealthMdsConnectionFailure.1

Start monitoring Windows servers running BlackBerry Enterprise Server (BES) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BLACKBERRYSERVER-MIB::besSysHealthMdsConnectionFailure OID value, configure state conditions and alerts, and monitor any Windows servers running BlackBerry Enterprise Server (BES) from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.3530rimBLACKBERRYSERVER-MIB
1.3.6.1.4.1.3530.5blackBerryServerBLACKBERRYSERVER-MIB
1.3.6.1.4.1.3530.5.25besSysHealthTableBLACKBERRYSERVER-MIB
1.3.6.1.4.1.3530.5.25.1besSysHealthEntryBLACKBERRYSERVER-MIB
1.3.6.1.4.1.3530.5.25.1.71besSysHealthMdsConnectionFailureBLACKBERRYSERVER-MIB