User's Manual

Chapter 20:Firmware Management
TR0153 Rev. E1 151
There are two approaches for upgrading the firmware of a number of devices in a mesh
neighborhood:
• Upgrade the firmware on each device individually
• Upgrade the firmware for the entire mesh neighborhood from the mesh gateway
The latter method is the recommended approach.
The primary benefit of using the mesh neighborhood upgrade approach is that the
gateway will determine the order in which it should start the upgrades of devices in
the mesh based on their relative connectivity. If each device is upgraded manually,
the user must determine the connectivity between devices to ensure that they are
upgraded in an order such that connectivity to devices isn’t broken. For example,
consider the following scenario:
• Device 1 is a gateway
• Device 2 is a repeater connected to device 1
• Device 3 is a repeater connected to device 2
If the upgrade of device 2 is started before the upgrade of device 3, the connection
to device 3 from the gateway will be lost, preventing the user from connecting to that
device.
At least the gateway device must have access to the Internet, and specifically
the Tranzeo upgrade server, to complete an upgrade unless the upgrade
image has already been downloaded to the device’s non-volatile memory.
If power to the EnRoute500 is lost during the upgrade process, it is possible
that the device will become inoperable.
20.2.1 Upgrading the Firmware on all Devices in a Mesh Neighborhood
The web GUI page for upgrading all devices in a mesh neighborhood is only
available on devices configured as gateways.
It is possible to control the firmware upgrade of all devices in a mesh neighborhood from the
“Upgrade Mesh” tab on the “Upgrade” page. This page displays the following information:
• Firmware available on the remote upgrade server
• Firmware available in the non-volatile memory of the EnRoute500
• Devices in the mesh neighborhood