RUGGEDCOM ROX II
CLI User Guide
Chapter 4
Device Management
Setting Up an Upgrade Server
83
2. Navigate to
admin » software-upgrade » upgrade-settings
and configure the following parameter(s) as
required:
Parameter
Description
repository-url { repository-url }
Synopsis:
A string
The URL for the upgrade server or file system. Supported URIs are HTTP, HTTPS, FTP, USB
and SD.
To upgrade from a USB flash drive or microSD card (if applicable), the URL format
is "usb://device-name/path-to-repository" or "sd://device-name/path-to-repository".
To determine the device name, insert your device and in the web ui, go to "chassis",
"storage", "removable", OR, in the cli, type "show chassis". Note that only one single
partition is supported for either data medium.
For all other protocols, the format is "protocol://user:password@host:port/path-to-file". If
the server does not require authentication, omit "user:password". When using the default
port for the protocol, omit ":port".
target-version { target-version }
Synopsis:
A string
The target software version. Specify a specific software release in the form of 'rrX.Y.Z' or
enter 'current' to upgrade to the latest software release available on the upgrade server.
3. Add the server's SSH/RSA public key to RUGGEDCOM ROX II and add the server to the Known Hosts list. For
more information, refer to
Section 6.8.8.2, “Adding a Known Host”
.
4. Type
commit
and press
Enter
to save the changes, or type
revert
and press
Enter
to abort.
Section 4.12.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 server must have sufficient disk space for at least two full software releases. Each full software release is
approximately 75 MB, 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/
Summary of Contents for RUGGEDCOM ROX II
Page 2: ...RUGGEDCOM ROX II CLI User Guide ii ...
Page 4: ...RUGGEDCOM ROX II CLI User Guide iv ...
Page 39: ...RUGGEDCOM ROX II CLI User Guide Table of Contents xxxix 19 5 VLANs 752 ...
Page 40: ...Table of Contents RUGGEDCOM ROX II CLI User Guide xl ...
Page 46: ...Preface RUGGEDCOM ROX II CLI User Guide xlvi Customer Support ...
Page 170: ...Chapter 5 System Administration RUGGEDCOM ROX II CLI User Guide 124 Deleting a Scheduled Job ...
Page 256: ...Chapter 6 Security RUGGEDCOM ROX II CLI User Guide 210 Enabling Disabling a Firewall ...
Page 402: ...Chapter 11 Wireless RUGGEDCOM ROX II CLI User Guide 356 Managing Cellular Modem Profiles ...