All MIBs › Unisphere-Data-System-Clock-MIB › usdNtpSysClockFrequencyError
usdNtpSysClockFrequencyError
Module: Unisphere-Data-System-Clock-MIB
OID (symbolic): Unisphere-Data-System-Clock-MIB::usdNtpSysClockFrequencyError
OID (numeric): 1.3.6.1.4.1.4874.2.2.56.2.1.3
Node type: OBJECT-TYPE
Type: Integer32
Access: read-only
Description: Displays the system clock frequency error in parts per million (ppm). It will always be a positive value. This error adjustment happens when the system reboots or the NTP is enabled for the first time and it may take up to fifteen minutes to complete.
Each system clock oscillator interrupts to update its clock. If for example, it interrupts one million time per second then it has resolution of microseconds. This is also frequency of the clock update. Frequency error represents failed to update by parts per millionth of a second.
For example, if we have frequency error of 1ppm, it means clock is ahead by 0.864 second in a day and that much has to be corrected in a day for clock to be accurate. Frequency error varies with temperature. Due to this system clock has to be corrected when system boots based on temperature it has to operate.
What is usdNtpSysClockFrequencyError?
The system clock's oscillator frequency error in parts per million (ppm), always reported as a positive value; a 1ppm error corresponds to the clock drifting about 0.864 seconds per day. This calibration runs after a reboot or when NTP is first enabled and can take up to fifteen minutes to complete, and it varies with the device's operating temperature.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.56.2.1.3 snmpwalk -v2c -c public <target> Unisphere-Data-System-Clock-MIB::usdNtpSysClockFrequencyError
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.56.2.1.3.1 snmpget -v2c -c public <target> Unisphere-Data-System-Clock-MIB::usdNtpSysClockFrequencyError.1
Start monitoring Unisphere Networks (Juniper E-series/ERX) routing switches (system clock/NTP sync-state status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Unisphere-Data-System-Clock-MIB::usdNtpSysClockFrequencyError OID value, configure state conditions and alerts, and monitor any Unisphere Networks (Juniper E-series/ERX) routing switches (system clock/NTP sync-state status) from a single console.
OID Breakdown
Upper-level ancestors (12 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.4874 | juniperUni | Juniper-UNI-SMI |
| 1.3.6.1.4.1.4874.2 | juniperUniMibs | Juniper-UNI-SMI |
| 1.3.6.1.4.1.4874.2.2 | juniMibs | Juniper-MIBs |
| 1.3.6.1.4.1.4874.2.2.56 | juniSysClockMIB | Juniper-MIBs |
| 1.3.6.1.4.1.4874.2.2.56.2 | juniNtpObjects | Juniper-System-Clock-MIB |
| 1.3.6.1.4.1.4874.2.2.56.2.1 | juniNtpSysClock | Juniper-System-Clock-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.4874.2.2.56.2.1.3 | usdNtpSysClockFrequencyError | Unisphere-Data-System-Clock-MIB |