OID reference
1.3.6.1.4.1.3902.15.2.11.14.3
the format of this item is xx.xx.xx.xx-x. Among this string, the first segment represents ntp server ipAddress, the value 0.0.0.0 is invalid; the second segment represents ntp version , only 1 or 2 or 3 valid. eg: 192.168.2.8-3.
Identification
{1 3 6 1 4 1 3902 15 2 11 14 3}
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.15.2.11.14.3.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.
srvIpAddrAndVersion OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-write
STATUS current
DESCRIPTION "the format of this item is xx.xx.xx.xx-x.
Among this string, the first segment
represents ntp server ipAddress, the value 0.0.0.0
is invalid; the second segment represents ntp
version , only 1 or 2 or 3 valid.
eg: 192.168.2.8-3."
::= { ntp 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
the format of this item is xx.xx.xx.xx-x. Among this string, the first segment represents ntp server ipAddress, the value 0.0.0.0 is invalid; the second segment represents ntp version , only 1 or 2 or 3 valid. eg: 192.168.2.8-3.
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: srvIpAddrAndVersion
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"srvIpAddrAndVersion",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"the format of this item is xx.xx.xx.xx-x. Among this string, the first segment represents ntp server ipAddress, the value 0.0.0.0 is invalid; the second segment represents ntp version , only 1 or 2 or 3 valid. eg: 192.168.2.8-3.\"",
"::=",
"{",
"ntp",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"the format of this item is xx.xx.xx.xx-x. Among this string, the first segment represents ntp server ipAddress, the value 0.0.0.0 is invalid; the second segment represents ntp version , only 1 or 2 or 3 valid. eg: 192.168.2.8-3."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. ZTE support.
Module: Es2952-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'Integer32', 'Unsigned32', 'IpAddress', 'enterprises']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3902.15.2.11.14.1 | synchronizeStatus | 0 | 0 | |
| 1.3.6.1.4.1.3902.15.2.11.14.2 | protocolStatus | 0 | 0 | |
| 1.3.6.1.4.1.3902.15.2.11.14.4 | sourceIpAddr | 0 | 0 |