OID reference
1.3.6.1.4.1.4935.15.11.50.100
The path of the configuration files (configFileFetchingFileName) location. The path is relative to the root of the transfer server (configFileFetchingHost). Use '/' to separate subdirectories.
Identification
{1 3 6 1 4 1 4935 15 11 50 100}
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.4935.15.11.50.100.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.
configFileFetchingFileLocation OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..63))
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The path of the configuration files (configFileFetchingFileName)
location. The path is relative to the root of the transfer server
(configFileFetchingHost).
Use '/' to separate subdirectories."
DEFVAL { "" }
::= { configFileFetchingMIBObjects 100 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The path of the configuration files (configFileFetchingFileName) location. The path is relative to the root of the transfer server (configFileFetchingHost). Use '/' to separate subdirectories.
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: configFileFetchingFileLocation
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"configFileFetchingFileLocation",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"0",
".",
".",
"63",
")",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The path of the configuration files (configFileFetchingFileName) location. The path is relative to the root of the transfer server (configFileFetchingHost). Use '/' to separate subdirectories.\"",
"DEFVAL",
"{",
[
"literal",
"2222"
],
"}",
"::=",
"{",
"configFileFetchingMIBObjects",
"100",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
0,
63
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The path of the configuration files (configFileFetchingFileName) location. The path is relative to the root of the transfer server (configFileFetchingHost). Use '/' to separate subdirectories."
],
null,
null,
null,
[
"DEFVAL",
"\"\""
]
]
}Vendor MIB copy from the Observium Community archive.
Module: MX-CONFIG-FILE-FETCHING-MIB
See published definition above
{'MX-TC': ['MxIpHostName', 'MxIpConfigSource', 'MxIpPort', 'MxEnableState', 'MxIpSelectConfigSource', 'MxIpDhcpSiteSpecificCode'], 'MX-SMI': ['ipAddressStatus', 'ipAddressConfig', 'mediatrixConfig'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Integer32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4935.15.11.50.50 | configFileFetchingFileName | 0 | 0 | |
| 1.3.6.1.4.1.4935.15.11.50.60 | configFileFetchingSpecificFileName | 0 | 0 | |
| 1.3.6.1.4.1.4935.15.11.50.150 | configFileTransfer | 3 | 3 | |
| 1.3.6.1.4.1.4935.15.11.50.200 | configFileAutomaticUpdate | 6 | 6 | |
| 1.3.6.1.4.1.4935.15.11.50.250 | configFilePrivacy | 3 | 3 |