OID reference
1.3.6.1.4.1.1966.12.1.25.5
The path and file name (do not use a drive letter), relative to the default path of your TFTP server software, of the new configuration file for the Device Server that will be loaded when the Device Server is rebooted.
Identification
{1 3 6 1 4 1 1966 12 1 25 5}
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.1966.12.1.25.5.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.
fileConfigurationName OBJECT-TYPE
SYNTAX DisplayString(SIZE(0..64))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The path and file name (do not use a drive letter), relative to the default
path of your TFTP server software, of the new configuration file for the Device
Server that will be loaded when the Device Server is rebooted."
::= { fileInfo 5}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The path and file name (do not use a drive letter), relative to the default path of your TFTP server software, of the new configuration file for the Device Server that will be loaded when the Device Server is rebooted.
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: fileConfigurationName
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fileConfigurationName",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"(",
"SIZE",
"(",
"0",
".",
".",
"64",
")",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The path and file name (do not use a drive letter), relative to the default path of your TFTP server software, of the new configuration file for the Device Server that will be loaded when the Device Server is rebooted.\"",
"::=",
"{",
"fileInfo",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"DisplayString",
[
"octetStringSubType",
[
[
0,
64
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The path and file name (do not use a drive letter), relative to the default path of your TFTP server software, of the new configuration file for the Device Server that will be loaded when the Device Server is rebooted."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: PERLE-IOLAN-SDS-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'IpAddress', 'Counter32', 'Unsigned32', 'Integer32', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Related source files and packages:
Vendor MIB copy from the Observium Community archive.
Module: PERLE-IOLAN-SDS-MIB
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'IpAddress', 'Counter32', 'Unsigned32', 'Integer32', 'enterprises'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1966.12.1.25.1 | fileStatus | 0 | 0 | |
| 1.3.6.1.4.1.1966.12.1.25.2 | fileFirmwareHost | 0 | 0 | |
| 1.3.6.1.4.1.1966.12.1.25.3 | fileFirmwareName | 0 | 0 | |
| 1.3.6.1.4.1.1966.12.1.25.4 | fileConfigurationHost | 0 | 0 | |
| 1.3.6.1.4.1.1966.12.1.25.6 | fileMOTDHost | 0 | 0 | |
| 1.3.6.1.4.1.1966.12.1.25.7 | fileMOTDName | 0 | 0 | |
| 1.3.6.1.4.1.1966.12.1.25.8 | fileMOTDTunnel | 0 | 0 |