OID reference
1.3.6.1.4.1.3955.1000.203.2.4.9
The file data type to transfer onto the AP. This object must be created when either the apFileTransferSrcFileType or apFileTransferDstFileType has the value networkFile.
Identification
{1 3 6 1 4 1 3955 1000 203 2 4 9}
| Value | Name |
|---|---|
| 1 | config |
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.4.9.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.
apFileTransferDataType OBJECT-TYPE
SYNTAX INTEGER {
config(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The file data type to transfer onto the AP. This object
must be created when either the apFileTransferSrcFileType or
apFileTransferDstFileType has the value networkFile."
DEFVAL { config }
::= { apFileTransfer 9 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The file data type to transfer onto the AP. This object must be created when either the apFileTransferSrcFileType or apFileTransferDstFileType has the value networkFile.
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: apFileTransferDataType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"apFileTransferDataType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"config",
"(",
"1",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The file data type to transfer onto the AP. This object must be created when either the apFileTransferSrcFileType or apFileTransferDstFileType has the value networkFile.\"",
"DEFVAL",
"{",
"config",
"}",
"::=",
"{",
"apFileTransfer",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"config",
1
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The file data type to transfer onto the AP. This object must be created when either the apFileTransferSrcFileType or apFileTransferDstFileType has the value networkFile."
],
null,
null,
null,
[
"DEFVAL",
"config"
]
]
}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.4.1 | apFileTransferProtocol | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.2 | apFileTransferSrcFileType | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.3 | apFileTransferDstFileType | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.4 | apFileTransferFilename | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.5 | apFileTransferAddressType | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.6 | apFileTransferAddress | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.7 | apFileTransferPort | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.8 | apFileTransferDirectory | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.10 | apFileTransferFileFormat | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.11 | apFileTransferStart | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.12 | apFileTransferStatus | 0 | 0 | |
| 1.3.6.1.4.1.3955.1000.203.2.4.13 | apFileTransferValidationStatus | 0 | 0 |