NETI-DTM-MIB :: dtmTimeScaleStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsNETI-DTM-MIBdtmTimeScaleStatus

dtmTimeScaleStatus

Module: NETI-DTM-MIB

OID (symbolic): NETI-DTM-MIB::dtmTimeScaleStatus

OID (numeric): 1.3.6.1.4.1.2928.6.2.4.1.7.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The time scale status of the synchronization clock of this node.

notSupported(1) Time Transfer is not supported or not enabled.

uninitiated(2) The initial state which indicates that the time of the time scale is not initiated and may not be used for any time keeping. The time scale is however running, so it may be used for relative measures such as those used in round-trip estimates. During the uninitiated state the Time Transfer Control Processing attempts to initiate the TAI/UTC time from either another DTM node in state compensated, or some local UTC source. When the such a source is available, it reassigns the time scale and enters the reassigned state.

reassigned(3) When the time scale of this node have a degenerated time-offset from neighbor nodes being compensated, or a local TAI/UTC source, the node reassigns the time scale and enters the reassigned state, during which the time scale may not be used for precision time-keeping. During the reassigned state the Time Transfer Control Processing attempts to retrace the TAI/UTC time from either another DTM node in state compensated, or some local TAI/UTC source. When the retracing have reduced the time error to within defined limits (1 us), it enters the compensated state.

compensated(4) When the time scale of the node has been initiated to TAI/UTC, it can be used for time keeping, but the time error of the time scale is too high (and thus stability and precision is limited). During the compensated state the Time Transfer Control Processing will use the TLL to maintain the TAI/UTC time scale from any neighboring nodes in the compensated state.

What is dtmTimeScaleStatus?

This reports the time-scale status of this node's synchronization clock: notSupported (Time Transfer disabled), uninitiated (time scale running but not yet set to TAI/UTC), reassigned (time scale just re-derived from a neighbor or local source and not yet precise), or compensated (TAI/UTC-traceable but time error still above 1 microsecond). Admins use this to judge whether the node's clock is currently trustworthy enough for precision time-keeping applications.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2928.6.2.4.1.7.4
snmpwalk -v2c -c public <target> NETI-DTM-MIB::dtmTimeScaleStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2928.6.2.4.1.7.4.1
snmpget -v2c -c public <target> NETI-DTM-MIB::dtmTimeScaleStatus.1

Start monitoring Net Insight DTM network elements with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NETI-DTM-MIB::dtmTimeScaleStatus OID value, configure state conditions and alerts, and monitor any Net Insight DTM network elements from a single console.

OID Breakdown

Upper-level ancestors (9 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.2928netinsightNETI-COMMON-MIB
1.3.6.1.4.1.2928.6netiExperimentalNETI-COMMON-MIB
1.3.6.1.4.1.2928.6.2netiExperimentalGenericNETI-COMMON-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2928.6.2.4netiDTMMIBNETI-DTM-MIB
1.3.6.1.4.1.2928.6.2.4.1netiDTMMIBObjectsNETI-DTM-MIB
1.3.6.1.4.1.2928.6.2.4.1.7dtmSyncGroupNETI-DTM-MIB
1.3.6.1.4.1.2928.6.2.4.1.7.4dtmTimeScaleStatusNETI-DTM-MIB