Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
1302 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
a. Error Type 513 — Indicates that the schedule has failed. A schedule failure can result from:
● Any of the previously mentioned log-only errors (257 – 259)
● An expiration of the schedule timer
● An execution of disable firmware download command
To resolve the error and clear the alarm, use the test firmware download command.
The Aux Data specifies the reason why the schedule failed. See Table 448
for more details.
21 Problem reading the requested file – Internal firmware error on target
board.
1. Retry the download, and escalate if it still fails.
22 The download file has a bad CRC – Internal firmware error on target
board.
1. Retry the download, and escalate if it still fails.
24 A download is already in progress – Internal firmware error on target
board.
1. Retry the download, and escalate if it still fails.
30 A start download sequence error – Internal firmware error on target
board.
4. Retry the download, and escalate if it still fails.
32 The file name is too long – Internal firmware error on target board.
1. Retry the download, and escalate if it still fails.
40 FLASH programming failed on firmware – Internal firmware error on
target board.
1. Retry the download, and escalate if it still fails.
All other
Aux Data
values
TFTP protocol error
1. Retry the download and escalate if it still fails.
Table 448: Error Type 513 Aux Data
Aux
Data
Description of Failure
1 Software resources not available; see Error Type 257 (a
).
1 of 2
Table 447: Aux Data for Error Type 259 (continued)
Aux Data Description of Failure
2 of 2