BEGEMOT-NTP-MIB :: begemotNtpJitter

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BEGEMOT-NTP-MIB › begemotNtpJitter

begemotNtpJitter

Module: BEGEMOT-NTP-MIB

OID (symbolic): BEGEMOT-NTP-MIB::begemotNtpJitter

OID (numeric): 1.3.6.1.4.1.12325.1.201.1.5

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Current jitter in seconds multiplied by 2^32.

What is begemotNtpJitter?

Reports the current NTP clock jitter in seconds, scaled by 2^32 for precision. High jitter values indicate unstable or noisy time synchronization with the upstream NTP source.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.12325.1.201.1.5
snmpwalk -v2c -c public <target> BEGEMOT-NTP-MIB::begemotNtpJitter

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.12325.1.201.1.5.1
snmpget -v2c -c public <target> BEGEMOT-NTP-MIB::begemotNtpJitter.1

Start monitoring FreeBSD hosts/appliances running the Begemot bsnmpd SNMP agent with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BEGEMOT-NTP-MIB::begemotNtpJitter OID value, configure state conditions and alerts, and monitor any FreeBSD hosts/appliances running the Begemot bsnmpd SNMP agent from a single console.

How to Use in IPNetwork Monitor

Select a FreeBSD hosts/appliances running the Begemot bsnmpd SNMP agent 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 begemotNtpJitter into the Find box to locate it in the OID tree, then select it and click OK. It reports the current jitter in seconds multiplied by 2^32. 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 Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the jitter climbs well above its normal baseline, since rising jitter often signals network congestion or a degrading path. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 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.12325fokusFOKUS-MIB
1.3.6.1.4.1.12325.1begemotBEGEMOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.12325.1.201begemotNtpBEGEMOT-NTP-MIB
1.3.6.1.4.1.12325.1.201.1begemotNtpObjectsBEGEMOT-NTP-MIB
1.3.6.1.4.1.12325.1.201.1.5begemotNtpJitterBEGEMOT-NTP-MIB