Demand test descriptions and error codes - Avaya Support

Table 129: Error Type 257 Aux Data descriptions 2 of 2
Aux Data Description
FW-STDL (Firmware Station Download)
14 Station firmware download to a terminal had too many retries, timeout
occurred.
b. Error Type 258 with Aux Data 5: one or more terminals in the download list were skipped
and not downloaded because the terminal was not in the appropriate state (in-service and
idle). Resolve the alarm with the test firmware station-download command. This
error can be caused by any of these problems:
● One or more target terminals were busied out by craft
● One or more target terminals were in use when the download attempt was made.
● One or more target terminals were out of service for an unknown reason.
Use the status firmware station-download command in conjunction with
Table 132: Reason Codes for status firmware station-download to determine the specific
cause of the failure to download.
c. Error Type 513: indicates a firmware download error that is not necessarily caused by the
target terminal. This error will cause the firmware download process to be stopped. Resolve
the alarm with the test firmware station-download command. The Aux Data values
associated with Error Type 513 are described in Table 130: Error Type 513 Aux Data
descriptions.
Table 130: Error Type 513 Aux Data descriptions 1 of 2
Aux Data Description
4 Two consecutive terminals failed to download with a failure indicating that
the terminals did not accept the firmware image. It is likely that any
remaining terminals will also fail, so the scheduled download is stopped
and any terminals in the download list that are not yet downloaded are
aborted.
8 The download image file is not present. The change firmware
station-download form requires that the image file be present before
the form can be brought up. This error indicates a problem with the image
file. As a result of this failure, the schedule cot continue, and any terminals
in the download list that are not yet downloaded are aborted.
11 There was a system error in the download process, possibly due to
interprocess calls. Escalate the problem.
2 of 2
1 of 2
Issue 5 May 2009 485