While an upload is in progress this will
always be 'no-error'. After an upload is complete
this indicates the success or failure of the upload.
If it is anything other than 'no-error' then
'luUploadStatusText' 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 / before
upload, as a result of reading a config file into the system.
conf-file-gen-err - General (unknown error)
conf-file-exec-error - Generation of config file resulted in
execution errors.
Parsed from file luDload.mib.txt
Company: None
Module: LUCENT-GENERIC-DLOAD-MIB
While an upload is in progress this will
always be 'no-error'. After an upload is complete
this indicates the success or failure of the upload.
If it is anything other than 'no-error' then
'luUploadStatusText' 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 / before
upload, as a result of reading a config file into the system.
conf-file-gen-err - General (unknown error)
conf-file-exec-error - Generation of config file resulted in
execution errors.
Parsed from file LUCENT-GENERIC-DLOAD-MIB.mib
Module: LUCENT-GENERIC-DLOAD-MIB
luUploadFailureCode 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-read-error (10), conf-file-gen-err (11), conf-file-exec-error (12), 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 an upload is in progress this will always be 'no-error'. After an upload is complete this indicates the success or failure of the upload. If it is anything other than 'no-error' then 'luUploadStatusText' 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 / before upload, as a result of reading a config file into the system. conf-file-gen-err - General (unknown error) conf-file-exec-error - Generation of config file resulted in execution errors." ::= { luUploadEntry 7 }
Vendor: Loral WDl
Module: LUCENT-GENERIC-DLOAD-MIB
[Automatically extracted from oidview.com]
luUploadFailureCode 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-read-error (10), conf-file-gen-err (11), conf-file-exec-error (12), 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 an upload is in progress this will always be 'no-error'. After an upload is complete this indicates the success or failure of the upload. If it is anything other than 'no-error' then 'luUploadStatusText' 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 / before upload, as a result of reading a config file into the system. conf-file-gen-err - General (unknown error) conf-file-exec-error - Generation of config file resulted in execution errors." ::= { luUploadEntry 7 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.677.5.1.1 | luUploadIPAddress | 0 | 0 | The IP address of the server to use for the upload when using TFTP-IP |
| 1.3.6.1.4.1.677.5.1.2 | luUploadIPGateway | 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.5.1.3 | luUploadIPXAddress | 0 | 0 | The IPX address of the server to use for the upload when using TFTP-IPX. The format of the address is |
| 1.3.6.1.4.1.677.5.1.4 | luUploadFileName | 0 | 0 | The filename under which to store the uploaded microcode. The maximum length of this string is device specific. If a string that i… |
| 1.3.6.1.4.1.677.5.1.5 | luUploadSource | 0 | 0 | The source for the upload. This will contain the luDeviceIndex for the upload source. |
| 1.3.6.1.4.1.677.5.1.6 | luUploadState | 0 | 0 | The current state of the Upload |
| 1.3.6.1.4.1.677.5.1.8 | luUploadStatusText | 0 | 0 | A display string describing the status of the upload in progress, or the reason for failure of the last upload. If FailureCode = n… |
| 1.3.6.1.4.1.677.5.1.9 | luUploadSize | 0 | 0 | While an upload is in progress this indicates the number of bytes transferred so far. After the upload is completed this remains… |
| 1.3.6.1.4.1.677.5.1.10 | luUploadErrorLogName | 0 | 0 | The filename under which an error log has been created. In the case of file uploads that produce errors this file should contain… |
| 1.3.6.1.4.1.677.5.1.11 | luUploadErrorLogLocation | 0 | 0 | The location of the error log. This will contain the luDeviceIndex for the error log |