OID reference
1.3.6.1.4.1.32050.3.4.1.1.21
This counter counts the total number of seconds where the 1PPS signal seems to have failed. This counter does not increment upon every missed pulse, but instead only counts those periods where the 1PPS signal appears to be missing for an extended period.
Identification
{1 3 6 1 4 1 32050 3 4 1 1 21}
A counter is cumulative. To estimate a rate, subtract two readings and divide by the elapsed time; use the units stated in the MIB.
Counter values can wrap or reset. A decrease alone does not distinguish a wrap from a reset, and multiple wraps between readings cannot be recovered reliably. Check the device's discontinuity indicators when available.
Published counter width: 32 bits. SMIv2: Counter32 · Counter64
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index: gnssReceiverSlot, gnssReceiverPort.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.32050.3.4.1.1.21
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
gnss1PPSFailedSeconds OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This counter counts the total number of seconds where the 1PPS
signal seems to have failed. This counter does not increment
upon every missed pulse, but instead only counts those periods
where the 1PPS signal appears to be missing for an extended
period."
::= { gnssReceiverEntry 21 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This counter counts the total number of seconds where the 1PPS signal seems to have failed. This counter does not increment upon every missed pulse, but instead only counts those periods where the 1PPS signal appears to be missing for an extended period.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: gnss1PPSFailedSeconds
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"gnss1PPSFailedSeconds",
"OBJECT-TYPE",
"SYNTAX",
"Counter32",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"This counter counts the total number of seconds where the 1PPS signal seems to have failed. This counter does not increment upon every missed pulse, but instead only counts those periods where the 1PPS signal appears to be missing for an extended period.\"",
"::=",
"{",
"gnssReceiverEntry",
"21",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Counter32"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This counter counts the total number of seconds where the 1PPS signal seems to have failed. This counter does not increment upon every missed pulse, but instead only counts those periods where the 1PPS signal appears to be missing for an extended period."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: PACKETFLUX-GNSS-MIB
See published definition above
{'SNMPv2-TC': ['DateAndTime', 'TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Gauge32', 'MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'PACKETFLUX-TC': ['Fixed2DecimalDigits', 'Fixed6DecimalDigits'], 'PACKETFLUX-SMI': ['packetfluxFeatureSpecific']}Related source files and packages:
Registration