OID reference
1.3.6.1.4.1.3955.1000.203.2.2.5
File to be uploaded onto the server. Default filename is 'config.xml'. Only XML files are supported for upgrade. The filename cannot contain the full path to the directory where the file will be placed. When all the objects are set correctly, the upload string is formed as such: <TFTP>://<ipAddress>[:<port>]/<fullpath…
Identification
{1 3 6 1 4 1 3955 1000 203 2 2 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.3955.1000.203.2.2.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.
apFileUploadFilename OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..64))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"File to be uploaded onto the server. Default filename is
'config.xml'. Only XML files are supported for upgrade.
The filename cannot contain the full path to the directory
where the file will be placed. When all the objects are set
correctly, the upload string is formed as such:
<TFTP>://<ipAddress>[:<port>]/<fullpath>/<filename.ext>"
::= { apFileUpload 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
File to be uploaded onto the server. Default filename is 'config.xml'. Only XML files are supported for upgrade. The filename cannot contain the full path to the directory where the file will be placed. When all the objects are set correctly, the upload string is formed as such: <TFTP>://<ipAddress>[:<port>]/<fullpath>/<filename.ext>
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: apFileUploadFilename
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"apFileUploadFilename",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"(",
"SIZE",
"(",
"0",
".",
".",
"64",
")",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"File to be uploaded onto the server. Default filename is 'config.xml'. Only XML files are supported for upgrade. The filename cannot contain the full path to the directory where the file will be placed. When all the objects are set correctly, the upload string is formed as such: <TFTP>://<ipAddress>[:<port>]/<fullpath>/<filename.ext>\"",
"::=",
"{",
"apFileUpload",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"DisplayString",
[
"octetStringSubType",
[
[
0,
64
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"File to be uploaded onto the server. Default filename is 'config.xml'. Only XML files are supported for upgrade. The filename cannot contain the full path to the directory where the file will be placed. When all the objects are set correctly, the upload string is formed as such: <TFTP>://<ipAddress>[:<port>]/<fullpath>/<filename.ext>"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: LINKSYS-WLAN-ACCESS-POINT-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['DisplayString', 'TruthValue', 'RowStatus', 'MacAddress', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'LINKSYS-WLAN-ACCESS-POINT-REF-MIB': ['smb']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3955.1000.203.2.2.1 | apFileUploadAddressType | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.2.2 | apFileUploadAddress | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.2.3 | apFileUploadPort | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.2.4 | apFileUploadDirectory | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.2.6 | apFileUploadDataType | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.2.7 | apFileUploadFileFormat | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.2.8 | apFileUploadProtocol | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.2.9 | apFileUploadStart | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.2.10 | apFileUploadStatus | 0 | 0 |