Table of Contents
Advertisement
RUGGEDCOM ROX II
CLI User Guide
Section 3.11.2
Setting Up an Upgrade Server
An upgrade server containing a software repository can be used to upgrade or downgrade the RUGGEDCOM
ROX II software via the network.
The upgrade server must meet the following requirements:
• Each device that will be upgraded/downgraded must have access to a host that acts as a Web server or FTP
server. The host must also be able to download new software releases from www.siemens.com/ruggedcom.
• The server must have sufficient disk space for at least two full software releases. Each full software release is
approximately 75 Mbits, although most upgrades are typically much smaller.
• The server must have sufficient bandwidth. The bandwidth requirements will be based on the number of
devices, the size of the upgrade, and when the devices launch an upgrade. The bandwidth is also limited by
default for each device to 500 kbps. A modest (e.g. 486 class machine) web server should be able to serve
files up to the limit of the network interface bandwidth.
• The server must be able to accept at least as many HTTP, HTTPS or FTP connections as there are devices on
the network.
• The server must contain and publish a directory specifically for RUGGEDCOM ROX II software releases. The
name of this directory will be specified in the upgrade settings for each device.
• Communication between the server and the device must be along a secure channel, such as IPsec.
• For upgrades via HTTPS, the server's public key must be signed by a trusted Certificate Authority (CA). A list of
recognized CA's is available under /etc/ssl/certs/
NOTE
Each device should be configured to upgrade at different times to minimize impact on the network. A
large upgrade (or a low bandwidth limiting value on each device) may cause all the devices to upgrade
at the same time.
The following sections describe how to configure an upgrade server:
•
Section 3.11.2.1, "Configuring the Upgrade Server"
•
Section 3.11.2.2, "Adding Software Releases to the Upgrade Server"
Section 3.11.2.1
Configuring the Upgrade Server
For RUGGEDCOM ROX II to properly retrieve files from an upgrade server, the following must be configured on
the server:
• MIME Types
The following MIME types must be defined for the chosen upgrade server (e.g. Microsoft IIS Manager, Apache
HTTP Server, Lighttpd, etc.) for RUGGEDCOM ROX II to properly retrieve files from the server:
NOTE
2.x.y represents the RUGGEDCOM ROX II version, where x is the major release number and y is
the minor release number. For example, 2.9.1.
File Type
RUGGEDCOM ROX II Image Archive
Setting Up an Upgrade Server
File
imagerr2.x.y.tar.bz2
Device Management
Required MIME Type
application/x-bzip2
Chapter 3
73
Advertisement
Table of Contents
Troubleshooting
