User's Manual

AR24027 Operator’s Manual (rev A)
- 32 -
in order to speed up the network recovery after rebooting the master radio below (this step is not
necessary if the new firmware is known to be compatible with the old one but it does not hurt in
either case).
9. Depress the “F4” key to log-off the session with the current radio. “Econ” displays the list of all
radios from the initial discovery phase. Select the next radio and repeat steps 4 through 8.
10. Once all radios in the network have the new program, log onto the master radio (using econsole)
and issue the command:
>reboot
to cause the master radio to restart using the new firmware.
11. If the new firmware is compatible with the old one, the link will be reestablished in a short time
(with the master running the new version and the slave running the old version).
If the new firmware is incompatible with the old one, the link will not be reestablsihed. In this
case, after 60 seconds, the slave radio will reboot. It will then execute the new firmware and be
able to reestablish the link with the master.
12. Wait at least ten seconds from the moment you entered the reboot command, then press <CR>.
Econsole automatically attempts to reconnect to the master radio. Once a new session with that
radio is reopened issue the command:
> version
and check that the master radio is indeed executing the new version. Then issue the command:
>monitor-link
to verify that the link is reestablished.
13. Depress the “F4” key to log-off the session with the master radio. “Econ” displays the list of all
radios from the initial discovery phase. Select a different radio and issue the command:
>version
and check if that radio is running the new or old version. If the radio is already running the new
version repeat this step with the next radio. Otherwise perform the next step.
14. If the radio is running the old version issue the command:
>reboot
Wait at least ten seconds for the radio to perform its start up code and re-establish the link. Then
press <CR>. Econsole automatically attempts to reconnect to the same radio again. Once a new
session with that radio is reopened issue the command:
> version
and check that the radio is indeed executing the new version.
15. Repeat the previous two steps until all the radios are running the new firmware.
Note that the file downloads are executed with the links in full operation. The only downtime in the
network occurs when the radios are rebooting. The radio configuration is kept intact when a new
version is started. The downtime for the radio being restarted, is typically less than twenty seconds.
When upgrading to an incompatible version, the downtime will be less than one minute.