TIMETRA-SATELLITE-MIB :: tmnxSatSyncIfTimingFreqOffset

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-SATELLITE-MIB › tmnxSatSyncIfTimingFreqOffset

tmnxSatSyncIfTimingFreqOffset

Module: TIMETRA-SATELLITE-MIB

OID (symbolic): TIMETRA-SATELLITE-MIB::tmnxSatSyncIfTimingFreqOffset

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.103.3.3.1.15

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: The value of tmnxSatSyncIfTimingFreqOffset indicates the frequency offset of the current selected timing reference for the satellite, in parts per million (ppm).

What is tmnxSatSyncIfTimingFreqOffset?

Reports, in parts per million, the frequency offset of the satellite's currently selected timing reference, a precision metric an admin checks when validating clock quality for synchronous Ethernet.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.103.3.3.1.15
snmpwalk -v2c -c public <target> TIMETRA-SATELLITE-MIB::tmnxSatSyncIfTimingFreqOffset

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.103.3.3.1.15.1
snmpget -v2c -c public <target> TIMETRA-SATELLITE-MIB::tmnxSatSyncIfTimingFreqOffset.1

Start monitoring Nokia/Alcatel-Lucent 7750 SR / 7950 XRS with satellite access nodes (satellite hardware/firmware status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-SATELLITE-MIB::tmnxSatSyncIfTimingFreqOffset OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7750 SR / 7950 XRS with satellite access nodes (satellite hardware/firmware status) from a single console.

How to Use in IPNetwork Monitor

Select a Nokia/Alcatel-Lucent 7750 SR / 7950 XRS with satellite access node (satellite hardware/firmware status) 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 tmnxSatSyncIfTimingFreqOffset 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 frequency offset of the currently selected timing reference for this satellite, in parts per million (ppm). 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 offset drifts away from zero beyond the tolerance your timing plan allows, since a growing frequency offset indicates a synchronization problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (10 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.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.103tmnxSatelliteObjsTIMETRA-SATELLITE-MIB
1.3.6.1.4.1.6527.3.1.2.103.3tmnxSatelliteStatusTIMETRA-SATELLITE-MIB
1.3.6.1.4.1.6527.3.1.2.103.3.3tmnxSatelliteSyncIfTimingTableTIMETRA-SATELLITE-MIB
1.3.6.1.4.1.6527.3.1.2.103.3.3.1tmnxSatelliteSyncIfTimingEntryTIMETRA-SATELLITE-MIB
1.3.6.1.4.1.6527.3.1.2.103.3.3.1.15tmnxSatSyncIfTimingFreqOffsetTIMETRA-SATELLITE-MIB