While a download is in progress this will
always be 'no-error'. After a download is complete
this indicates the success or failure of the download.
If it is anything other than 'no-error' then
'luDownloadStatusText' will contain a textual
description of the error. Error codes from 100
upwards are errors returned from a TFTP server.
Errors below this are locally generated.
Configuration files may return errors after download
as a result of reading a config file into the system.
conf-file-gen-err - General (unknown error)
conf-file-parse-error - Reading of config file resulted in
parsing errors.
conf-file-exec-error - Reading of config file resulted in
execution errors.
Parsed from file luDload.mib.txt
Company: None
Module: LUCENT-GENERIC-DLOAD-MIB
While a download is in progress this will
always be 'no-error'. After a download is complete
this indicates the success or failure of the download.
If it is anything other than 'no-error' then
'luDownloadStatusText' will contain a textual
description of the error. Error codes from 100
upwards are errors returned from a TFTP server.
Errors below this are locally generated.
Configuration files may return errors after download
as a result of reading a config file into the system.
conf-file-gen-err - General (unknown error)
conf-file-parse-error - Reading of config file resulted in
parsing errors.
conf-file-exec-error - Reading of config file resulted in
execution errors.
Parsed from file LUCENT-GENERIC-DLOAD-MIB.mib
Module: LUCENT-GENERIC-DLOAD-MIB
luDownloadFailureCode OBJECT-TYPE SYNTAX INTEGER { no-error (1), config-error (2), busy (3), timeout (4), cancelled (5), incompatible-file (6), file-too-big (7), protocol-error (8), flash-write-error (9), nvram-write-error (10), conf-file-gen-err (11), conf-file-parse-error (12), conf-file-exec-error (13), undefined-error (100), file-not-found (101), access-violation (102), out-of-memory (103), illegal-operation (104), unknown-transfer-id (105), file-already-exists (106), no-such-user (107) } MAX-ACCESS read-only STATUS current DESCRIPTION "While a download is in progress this will always be 'no-error'. After a download is complete this indicates the success or failure of the download. If it is anything other than 'no-error' then 'luDownloadStatusText' will contain a textual description of the error. Error codes from 100 upwards are errors returned from a TFTP server. Errors below this are locally generated. Configuration files may return errors after download as a result of reading a config file into the system. conf-file-gen-err - General (unknown error) conf-file-parse-error - Reading of config file resulted in parsing errors. conf-file-exec-error - Reading of config file resulted in execution errors." ::= { luDownloadEntry 8 }
Vendor: Loral WDl
Module: LUCENT-GENERIC-DLOAD-MIB
[Automatically extracted from oidview.com]
luDownloadFailureCode OBJECT-TYPE SYNTAX INTEGER { no-error (1), config-error (2), busy (3), timeout (4), cancelled (5), incompatible-file (6), file-too-big (7), protocol-error (8), flash-write-error (9), nvram-write-error (10), conf-file-gen-err (11), conf-file-parse-error (12), conf-file-exec-error (13), undefined-error (100), file-not-found (101), access-violation (102), out-of-memory (103), illegal-operation (104), unknown-transfer-id (105), file-already-exists (106), no-such-user (107) } MAX-ACCESS read-only STATUS current DESCRIPTION "While a download is in progress this will always be 'no-error'. After a download is complete this indicates the success or failure of the download. If it is anything other than 'no-error' then 'luDownloadStatusText' will contain a textual description of the error. Error codes from 100 upwards are errors returned from a TFTP server. Errors below this are locally generated. Configuration files may return errors after download as a result of reading a config file into the system. conf-file-gen-err - General (unknown error) conf-file-parse-error - Reading of config file resulted in parsing errors. conf-file-exec-error - Reading of config file resulted in execution errors." ::= { luDownloadEntry 8 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.677.4.1.1 | luDownloadIPAddress | 0 | 0 | The IP address of the server to use for the download when using TFTP-IP |
| 1.3.6.1.4.1.677.4.1.2 | luDownloadIPGateway | 0 | 0 | The IP gateway to be used to access the server. If this variable is zero then use the default gateway in luOpIPGateway. |
| 1.3.6.1.4.1.677.4.1.3 | luDownloadIPXAddress | 0 | 0 | The IPX address of the server to use for the download when using TFTP-IPX or RPL-IPX. The format of the address is |
| 1.3.6.1.4.1.677.4.1.4 | luDownloadNodeAddress | 0 | 0 | The Node address of the server to use for the download when using RPL-LLC |
| 1.3.6.1.4.1.677.4.1.5 | luDownloadFileName | 0 | 0 | The filename of the microcode to download. The maximum length of this string is device specific. If a string that is too long is … |
| 1.3.6.1.4.1.677.4.1.6 | luDownloadDestination | 0 | 0 | The destination for the download. This will contain the luDeviceIndex for the download destination. |
| 1.3.6.1.4.1.677.4.1.7 | luDownloadState | 0 | 0 | The current state of the download |
| 1.3.6.1.4.1.677.4.1.9 | luDownloadStatusText | 0 | 0 | A display string describing the status of the download in progress, or the reason for failure of the last download. If FailureCode… |
| 1.3.6.1.4.1.677.4.1.10 | luDownloadSize | 0 | 0 | While a download is in progress this indicates the number of bytes transferred so far. After the download is completed this rema… |
| 1.3.6.1.4.1.677.4.1.11 | luDownloadErrorLogName | 0 | 0 | The filename under which an error log has been created. In the case of file downloads that produce errors this file should conta… |
| 1.3.6.1.4.1.677.4.1.12 | luDownloadErrorLogLocation | 0 | 0 | The location of the error log. This will contain the luDeviceIndex for the error log |