Appendix C. Setting Up An Upgrade Server
ROX™ v2.2 User Guide
432
RuggedBackbone™ RX5000
The ZIP file name will be in the form rrX.Y.Z.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
new features are added or serious bugs fixed, and the patch release number ‘Z’ is increased when
minor bug repairs are made.
The zip file will extract to a directory that has the same name as the major release, e.g. “rr2”. As
subsequent releases are made, they will also be extracted into this directory.
C.4. Setting Up The Routers
Suppose you have just unzipped rr2.1.1.zip into “ruggedBackbone” (or "ruggedBackboneTest" if you
do not want your routers to point to it yet) on a server available to the network at server.xyz.net.
There are now two approaches available to you for the upgrade settings on the unit.
The first method described allows you to configure the unit to always upgrade to the last release that
was installed on the server. The advantage of this approach is that you do not have to update upgrade
configurations each time you obtain a new release. On the RuggedBackbone configure the repository-url
parameter to “http://server.xyz.net/ruggedBackbone/rr2” and the target-release parameter to “current”.
You can proceed to launch the upgrade on the ruggedBackbone (this can be done via CLI, web user
interface, and NETCONF - see the appropriate user guide for details).
The second method allows you to configure the target release version explicitly. Some administrators
may prefer this approach for sake of clarity, but this has the disadvantage of having to update all the units
with the release version each upgrade. On the RuggedBackbone configure the repository-url parameter
to “http://server.xyz.net/ruggedBackbone/rr2” and the target-release parameter to "rr2.1.1".
C.5. Using Microsoft Internet Information Services (IIS)
Manager 6.0 or Higher as a ROX Upgrade Repository
When using Microsoft Internet Information Services (IIS) Manager 6.0 or higher as your ROX upgrade
repository, you must add a new application/octet-stream MIME type named * to the IIS properties. The
new MIME type is required for IIS to consider ROX upgrade packets as an application/octet stream. If
the new MIME type is not added, ROX upgrades will fail.
To add the new MIME type, perform the following steps on your IIS server.
Procedure C.1. Adding the * MIME Type
1.
In the Windows Start menu, right-click on My Computer and select Manage. The Computer
Management dialog appears.
2.
Under Services and Applications, locate the Internet Information Services (IIS) Manager node.
Right-click on your ROX upgrade repository website and select Properties. The Properties dialog
appears.
3.
Select the HTTP Headers tab and click MIME Types. The MIME Types dialog appears.
4.
Click New. The MIME Type dialog appears.
5.
In the Extension field, type *.
In the MIME type field, type application/octet-stream.
6.
Click OK on the MIME Type, MIME Types, and Properties dialog boxes.
