DIRECTORY-SERVER-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DIRECTORY-SERVER-MIB

Organization: IETF Mail and Directory Management Working Group

Last Updated: 1999-06-07

Category: Web and Application Servers

Description: Defines managed objects for monitoring directory server operations (LDAP, X.500, etc.).

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring DIRECTORY-SERVER-MIB with a free 30-day trial of IPNetwork Monitor.

What Is DIRECTORY-SERVER-MIB?

DIRECTORY-SERVER-MIB (dsMIB) is an IETF standards-track MIB published as RFC 2605 by the IETF Mail and Directory Management Working Group, obsoleting the earlier RFC 1567 dsaMIB. It models generic directory server operations — LDAP, CLDAP, and X.500 DAP/DSP front-ends and back-ends — exposing per-application-instance data in the dsTable (dsServerType, dsMasterEntries, dsCopyEntries, dsCacheEntries, dsCacheHits, dsSlaveHits, indexed via applIndex from the companion NETWORK-SERVICES-MIB), per-protocol operation counters in dsApplIfOpsTable (binds, reads, searches, referrals, chainings, replication updates, and traffic bytes), and peer-interaction history in dsIntTable (dsIntEntFailures/dsIntEntSuccesses, dsIntEntURL). It is useful for monitoring both the health of a directory service itself — cache hit ratios, entry counts, error rates — and its relationships with replication partners and referral targets. It depends on the NETWORK-SERVICES-MIB applTable for the base application description and on SNMPv2-TC/RMON2-MIB textual conventions for counters, and anyone deploying an LDAP or X.500 directory server that supports SNMP instrumentation can consult the DIRECTORY-SERVER-MIB RFC to see exactly which objects are mandatory for compliance.

IPNetwork Monitor allows you to monitor SNMP objects defined in DIRECTORY-SERVER-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • vendor-neutral, standards-based MIB (RFC 2605), not tied to a specific manufacturer — applies to LDAP/X.500 directory server software

Monitoring Examples

An operator polls dsApplIfInOps and dsApplIfErrors in dsApplIfOpsTable to track request volume and failure rate per protocol interface, and watches dsIntEntFailuresSinceLastSuccess in dsIntTable for a specific peer server; a rising failure count alongside a stale dsIntEntTimeOfLastSuccess would indicate that replication or referral connectivity to that peer has broken.

What Can Be Monitored

  • directory entry counts (master/copy/cache)
  • cache hit counters
  • bind and search operation counters per protocol interface
  • referral and chaining counters
  • replication update counters
  • peer directory server interaction history
Imported Objects

From NETWORK-SERVICES-MIB

DistinguishedName
URLString
applIndexOBJECT-TYPE

From RFC1213-MIB

mib-2

From RMON2-MIB

ZeroBasedCounter32

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TimeStamp

How to Use in IPNetwork Monitor

Example using dsCacheHits OID:

Select an LDAP/X.500 directory server software (vendor-neutral, RFC 2605) 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 dsCacheHits 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. It reports the number of operations that were serviced from the locally held cache. 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 sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Monitors Directory Services including LDAP servers and related statistics from RFC 2605.

Start monitoring LDAP/X.500 directory server software (vendor-neutral, RFC 2605) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download DIRECTORY-SERVER-MIB