19216811.liveSoftware update
SwUpdate module
iMG/RG Software Reference Manual (System Configuration)
1-64
It then connects to the FTP/TFTP server and retrieves a file named MD5SUM from the directory defined by the
path parameter (and eventually by the MAC parameter). This file contains a list of all files available on the
server, with the corresponding MD5 value that the
SwUpdate
module must retrieve from the FTP server.
It compares the MD5SUM file downloaded from the server with the local MD5 file calculated on the current
flash file system.
For each file in the MD5SUM file that differ from the list in the local MD5 file or it not present, the
SwUpdate
retrieves it from the FT/TFTP server.
When all the files have been downloaded, they are saved permanently into the gateway file-system and the gate-
way is restarted. The next time it starts, the gateway will use the new files.
Non-existing times, such as ‘missing hours’ during daylight savings conversion, will never match, causing
SwUp-
date
scheduled during the ‘missing times’ not to be started.
1.4.3.2 Retry Period scheduling
If
SwUpdate
fails a download, it reschedules the next request using the retry-period timeout.
The retry-period timeout specifies the Maximum time within the
SwUpdate
will reschedule the next request.
The exact time when the
SwUpdate
will perform the next request is randomly selected between 15secs and
the retry-period timeout. This computation is performed every time
SwUpdate
fails and a new request must be
scheduled.
When the download finishes successfully,
SwUpdate
is rescheduled using the start timetable. If the current time
is in the time window between two consecutive start and stop time, the
SwUpdate
suspends any download.
The start time has precedence over the
Retry Period
schedule. If the start time happens while the
Retry Period
is running,
SwUpdate
starts immediately the download and only if it fails, it will reschedule the download.
1.4.3.3 Stop Time scheduling
It is possible stop
SwUpdate
at any minute/hour/day/week of the year.
Stop time is typically used when
SwUpdate
fails a download and as result a new request has been scheduled
prior to the next start time.
To prevent continuous re-transmissions, stop time forces the
SwUpdate
to stop any scheduled retry during
specific (configurable) time of day or day of week.
SwUpdate
will be active only in timeslots defined by two consecutive start and stop times.
The time period between a stop time and the consecutive start time is the inactive (idle) period where
SwUp-
date
does NOT contacts any server.
If the retry-period timer was running before the stop time, this timer is stopped when the local time match the
stop time.