Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tftpTransferStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"noOp",
"(",
"1",
")",
",",
"connecting",
"(",
"2",
")",
",",
"transferringData",
"(",
"3",
")",
",",
"endedOk",
"(",
"4",
")",
",",
"error",
"(",
"5",
")",
",",
"busyByOther",
"(",
"6",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Status of SNMP-initiated TFTP transfer. Results: noOp(1) Default, no TFTP operation was in progress. connecting(2) Device is connecting to the server specified by tftpServerIP. transferringData(3) TFTP data transfer is in progress. endedOk(4) TFTP transfer ended with success. error(5) TFTP data transfer ended with an Error, (e.g. server timeout or remote filename not found). Check TFTP server log file for details. busyByOther(6) This value can never be read directly from the MIB tree. It is used only in tftpStatusChange to notify that device is bysy with other maintenance operation and the request for another operation was denied. If tftpLastOp is tftpSwDownload(3), tftpConfigDownload(4) or tftpConfigUpload(5), this variable shows the status of exactly that operation. Transfers initiated by other means (for example CLI command TFTP operation or normal software download), do not change this variable. This way one can get full status of SNMP-initiated up/download without interference.\"",
"::=",
"{",
"tftp",
"8",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"noOp",
1
],
[
"connecting",
2
],
[
"transferringData",
3
],
[
"endedOk",
4
],
[
"error",
5
],
[
"busyByOther",
6
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Status of SNMP-initiated TFTP transfer. Results: noOp(1) Default, no TFTP operation was in progress. connecting(2) Device is connecting to the server specified by tftpServerIP. transferringData(3) TFTP data transfer is in progress. endedOk(4) TFTP transfer ended with success. error(5) TFTP data transfer ended with an Error, (e.g. server timeout or remote filename not found). Check TFTP server log file for details. busyByOther(6) This value can never be read directly from the MIB tree. It is used only in tftpStatusChange to notify that device is bysy with other maintenance operation and the request for another operation was denied. If tftpLastOp is tftpSwDownload(3), tftpConfigDownload(4) or tftpConfigUpload(5), this variable shows the status of exactly that operation. Transfers initiated by other means (for example CLI command TFTP operation or normal software download), do not change this variable. This way one can get full status of SNMP-initiated up/download without interference."
],
null,
null,
null,
null
]
}