OID reference
1.3.6.1.4.1.3902.1015.65.1.1.4
The network clock source status. 'valid' indicates the selected network clock source is valid, 'invalid' indicates the selected network clock source is invalid due to clock frequency offset exceeded limit or other factors.
Identification
{1 3 6 1 4 1 3902 1015 65 1 1 4}
| Value | Name |
|---|---|
| 1 | valid |
| 2 | invalid |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.3902.1015.65.1.1.4.0
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.
zxAnSyncEClockSourceStatus OBJECT-TYPE
SYNTAX INTEGER
{
valid (1),
invalid (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The network clock source status.
'valid' indicates the selected network clock source is
valid, 'invalid' indicates the selected network clock
source is invalid due to clock frequency offset
exceeded limit or other factors."
::= { zxAnSyncEGlobalObjects 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The network clock source status. 'valid' indicates the selected network clock source is valid, 'invalid' indicates the selected network clock source is invalid due to clock frequency offset exceeded limit or other factors.
ZTE MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: zxAnSyncEClockSourceStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxAnSyncEClockSourceStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"valid",
"(",
"1",
")",
",",
"invalid",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The network clock source status. 'valid' indicates the selected network clock source is valid, 'invalid' indicates the selected network clock source is invalid due to clock frequency offset exceeded limit or other factors.\"",
"::=",
"{",
"zxAnSyncEGlobalObjects",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"valid",
1
],
[
"invalid",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The network clock source status. 'valid' indicates the selected network clock source is valid, 'invalid' indicates the selected network clock source is invalid due to clock frequency offset exceeded limit or other factors."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. ZTE support.
Module: ZTE-AN-SYNCE-MIB
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY'], 'ZTE-AN-TC-MIB': ['zxAn', 'ZxAnIfindex']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3902.1015.65.1.1.1 | zxAnSyncEClockSourceType | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.65.1.1.2 | zxAnSyncEClockRecoveryPort | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.65.1.1.3 | zxAnSyncEUniPortSyncEnable | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.65.1.1.5 | zxAnSyncEClockOperationStatus | 0 | 0 |