Avaya 03-300430 User Manual

Page of 2574
STA-FWDL
Issue 1 June 2005
2125
 
13
Two consecutive terminals failed to download due to internal timeouts. It is 
likely that all terminals will fail as well so the schedule is stopped and any 
remaining terminals in the download list are aborted.
14
Could not build a list of terminals from the range specified in the change 
firmware station-download form. Check the administered stations 
for exact extension numbers.
15
The scheduled stop time was reached without completion of all scheduled 
terminals. The status firmware station-download command 
indicates all terminals not downloaded with a status of ABRT and a Reason 
Code of 3 (see 
on page 2126). If the Continue daily until 
completed field is y, this error will not occur because the continuation 
option causes the schedule to resume the next day at the scheduled start 
time (see 
Table 761: Schedule States of status firmware station-download command
State
Schedule
Done?
Description
Idle
No
No downloads Pending or Active and there are no unresolved 
errors/alarms for the last download
Pending
No
Download has been scheduled but not yet started. Check the 
start time to see when it is scheduled to start.
Active
No
Download is currently active. Actively downloading terminals 
should be listed with a status of ACTV. If the schedule has just 
started and no downloads are listed, the system may be 
waiting for a FAC requested or terminal requested download 
to complete before it begins.
Resume-pending
No
Download was stopped at the Stop Date/Time but not all of 
the terminals have been attempted. Downloading will resume 
at the scheduled Start Date/Time listed on the screen.
Aborted
Yes
Download was aborted for the entire range of terminals. This 
could happen if the firmware image was bad, damaged or 
lost.
 1 of 2
Table 760: Error Type 513 Aux Data descriptions  (continued)
Aux 
Data
Description
 2 of 2