F3-SYNC-MIB :: f3TimeClockTimeInHoldover

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsF3-SYNC-MIBf3TimeClockTimeInHoldover

f3TimeClockTimeInHoldover

Module: F3-SYNC-MIB

OID (symbolic): F3-SYNC-MIB::f3TimeClockTimeInHoldover

OID (numeric): 1.3.6.1.4.1.2544.1.12.12.1.3.1.28

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: Time (seconds) in Holdover.

What is f3TimeClockTimeInHoldover?

This object measures the elapsed time in seconds that the timing clock has been operating in holdover mode, which occurs when the primary timing source (like GPS or external sync input) is lost and the clock relies on its internal oscillator to maintain timing accuracy. Time in holdover indicates reduced clock accuracy and helps predict when the clock will exceed its stability limits. Telecom operators monitor this metric to ensure timing systems remain within specification and to schedule maintenance before clock drift becomes critical.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2544.1.12.12.1.3.1.28
snmpwalk -v2c -c public <target> F3-SYNC-MIB::f3TimeClockTimeInHoldover

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2544.1.12.12.1.3.1.28.1
snmpget -v2c -c public <target> F3-SYNC-MIB::f3TimeClockTimeInHoldover.1

Start monitoring ADVA Optical Networking FSP150CM/CC (F3 platform) carrier Ethernet device (SyncE/timing synchronization) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the F3-SYNC-MIB::f3TimeClockTimeInHoldover OID value, configure state conditions and alerts, and monitor any ADVA Optical Networking FSP150CM/CC (F3 platform) carrier Ethernet device (SyncE/timing synchronization) from a single console.

How to Use in IPNetwork Monitor

Select an ADVA (Adtran) FSP 3000 R8 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 f3TimeClockTimeInHoldover 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 how many seconds the network element's timing clock has been running in holdover — i.e. free-running without a valid external reference. 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 holdover duration exceeds a few minutes (e.g. 300 seconds), since prolonged holdover risks clock drift affecting synchronization-dependent services. Click Finish to create the monitor; you can adjust any parameter later.

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.2544advaMIBADVA-MIB
1.3.6.1.4.1.2544.1productsADVA-MIB
1.3.6.1.4.1.2544.1.12fsp150cmADVA-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2544.1.12.12f3SyncMIBF3-SYNC-MIB
1.3.6.1.4.1.2544.1.12.12.1f3SyncObjectsF3-SYNC-MIB
1.3.6.1.4.1.2544.1.12.12.1.3f3TimeClockTableF3-SYNC-MIB
1.3.6.1.4.1.2544.1.12.12.1.3.1f3TimeClockEntryF3-SYNC-MIB
1.3.6.1.4.1.2544.1.12.12.1.3.1.28f3TimeClockTimeInHoldoverF3-SYNC-MIB