NTP-PROXY-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NTP-PROXY-MIB

Organization: University of Delaware

Last Updated: 1997-07-25

Description: University of Delaware MIB for monitoring and controlling multiple NTP servers through a single SNMP proxy agent on any NTP-capable host

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is NTP-PROXY-MIB?

NTP-PROXY-MIB is a University of Delaware standards-track MIB that lets a single SNMP agent act as a proxy for monitoring and controlling multiple NTP (Network Time Protocol) servers on other hosts, rather than modeling the local system's own clock. It defines a control table listing each remote NTP server's IP address and control status, plus a system-status table reporting each remote server's leap indicator, stratum, precision, root delay, root dispersion, and reference identifier, the standard NTP association-quality metrics. Its monitoring role is fundamentally software/service status for time synchronization: stratum and root-dispersion/delay values reveal how accurate and well-synchronized each proxied NTP server is, and a high stratum or large root dispersion signals a server that has lost a good upstream time reference. This proxy design lets one management station substitute this MIB for needing SNMP agents directly on every NTP server, though it depends conceptually on the base NTP protocol and the related IETF NTP MIB for its stratum/leap/precision semantics. It is deployed in environments with many NTP servers, such as campus or carrier networks, where centralizing NTP health monitoring through one proxy agent is more practical than instrumenting every server, and administrators consult the NTP-PROXY-MIB reference to identify the exact objects to poll for each proxied host.

IPNetwork Monitor allows you to monitor SNMP objects defined in NTP-PROXY-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, not tied to a specific manufacturer
  • any host running an NTP proxy agent monitoring remote NTP servers

Monitoring Examples

A monitoring station polls ntpProxyServerSystemTable, indexed by ntpProxyServerIPAddr, to read ntpProxyServerSysStratum and ntpProxyServerSysRootDispersion for each proxied server, and checks ntpProxyControlStatus in ntpProxyControlTable to confirm the proxy is actively tracking that server; a server whose sysStratum jumps upward or whose sysLeap indicates an alarm condition signals it has lost synchronization to its reference clock.

What Can Be Monitored

  • remote NTP server address and control status
  • NTP stratum level
  • root delay and root dispersion
  • leap indicator
  • clock precision and reference ID
Imported Objects

From NTP-MIB

NTPLeapIndicator
NTPTimeStamp

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
enterprises

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using ntpProxyServerSysStratum OID:

Select an NTP proxy host 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 ntpProxyServerSysStratum 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 NTP stratum level of the system this proxy represents. 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 an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the value drifts significantly from its normal baseline, since an unexpected change often points to a real underlying issue. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Provides centralized monitoring and control of multiple NTP servers through a proxy agent, enabling remote management of distributed time synchronization.

Start monitoring NTP proxy hosts 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 NTP-PROXY-MIB