Filter
Top Products
Appendix A - Setting Up A Repository
Upgrading The Repository
RuggedRouter releases are obtained from the RuggedCom web site as ZIP files.
Download the ZIP file to your regular and/or test release directories and unzip them.
You may delete the original ZIP file if desired.
The ZIP file name will be in the form rrX.Y.zip. The major release number X is
changed when major new functionality (often hardware related) is offered. The minor
release number Y is increased when minor functionality is added or bug repairs are
made. The first RuggedRouter upgrade release is rr1.1.zip.
The zip file will extract to a directory that has the same name as the major release, e.g.
“rr1”. As subsequent release are made, they will also be extracted into this directory.
Setting Up The Routers
The name of the release directory, and the major and minor release names from the
zip file tells you how to set up the routers.
Suppose you have just unzipped rr1.2.zip into “ruggedroutertest” on a server available
to the network at server.xyz.net. The major release is rr1 and the minor release is 2.
You have chosen this directory because you want to test the release on a specific
machine before propagating it to the network.
Login to the test router and visit the Maintenance menu, Upgrade Software,
Change Repository Server sub-menu. Change the Repository server field to
“http://server.xyz.net/ruggedroutertest” and the Release Version field to “rr1”. You
can proceed to upgrade the router manually or wait for the next nightly upgrade to
take place.
After you are satisfied that the upgrade was successful you can proceed to unzip the
rr1.2.zip file into your “ruggedrouter” directory (or copy the rr1/dists/rr1.2 and
rr1/dists/current directories into or the “ruggedrouter” directory).
Ensure that the remainder of the routers to be upgraded have a Repository server
field to “http://server.xyz.net/ruggedrouter” and the Release Version field to “rr1”.
They can now be upgraded.
An Alternate Approach
You can eliminate the need for separate release and test directories by making your
routers upgrade to a specific major and minor releases.
In this approach you will always extract releases to the same directory, e.g.
“ruggedrouter”.
All routers will be configured with a Repository server field set to
“http://server.xyz.net/ruggedrouter” and the Release Version field initially set to
“rr1.1”. When you need to upgrade to rr1.2 you will visit the routers and update the
Release Version field.
This method is simpler, but has the disadvantage that you need to visit each of the
routers. This can become unwieldy when there are many routers to manage.
RuggedCom 295